Forums
New posts
Search forums
What's new
Articles
Latest reviews
Author list
Classifieds
Log in
Register
What's new
Search
Search
Search titles and first posts only
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Rifles, Reloading, Optics, Equipment
Rifles, Bullets, Barrels & Ballistics
Ballistics caculator help
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="BallisticsGuy" data-source="post: 1681670" data-attributes="member: 96226"><p>That's what I would call goal seeking. Doing that is a defacto admission that either the math was wrong or the inputs were wrong. Since the math doesn't change, the inputs need to but which one and by how much? Most ballistics apps have some capacity for adding some level of refinement to the data, usually something like banded BC's and stepped velocities and such. Many apps (not mine because I advocate accurate data gathering and analysis) have "truing" features which adjust velocity or BC to make N result match the prediction of the model. In the case of velocity it's not truing squat, it's fabricating bogus input data to match observed results without regard to the origin of the departure between the mathematical model and the observed results. This is making up for BDU's (brain dead users) who don't want to troubleshoot or are incapable of troubleshooting. As far as BC truing, that is in my opinion the only legitimate use of truing type functionality. That's only because minor changes in BC aren't necessarily unheard of going from one lot of projectiles to another and because drag, especially at long range, is affected by quite a few continuously varying factors in the real world. </p><p></p><p>Dealing with an ultra-complicated reality in a way that Joe Sixpack with no understanding of the physics involved can enter some trivially easy to gather information into an app and get an answer to their question is not going to be without consequences to the perfection of the prediction of the model.</p></blockquote><p></p>
[QUOTE="BallisticsGuy, post: 1681670, member: 96226"] That's what I would call goal seeking. Doing that is a defacto admission that either the math was wrong or the inputs were wrong. Since the math doesn't change, the inputs need to but which one and by how much? Most ballistics apps have some capacity for adding some level of refinement to the data, usually something like banded BC's and stepped velocities and such. Many apps (not mine because I advocate accurate data gathering and analysis) have "truing" features which adjust velocity or BC to make N result match the prediction of the model. In the case of velocity it's not truing squat, it's fabricating bogus input data to match observed results without regard to the origin of the departure between the mathematical model and the observed results. This is making up for BDU's (brain dead users) who don't want to troubleshoot or are incapable of troubleshooting. As far as BC truing, that is in my opinion the only legitimate use of truing type functionality. That's only because minor changes in BC aren't necessarily unheard of going from one lot of projectiles to another and because drag, especially at long range, is affected by quite a few continuously varying factors in the real world. Dealing with an ultra-complicated reality in a way that Joe Sixpack with no understanding of the physics involved can enter some trivially easy to gather information into an app and get an answer to their question is not going to be without consequences to the perfection of the prediction of the model. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Rifles, Reloading, Optics, Equipment
Rifles, Bullets, Barrels & Ballistics
Ballistics caculator help
Top