J
Jeff59
Guest
Agree with the TDS assessment, a great tool for the intended application. Those X counts are a bit tough to handle.
As the creator of TDS I've been following this thread with interest. When I saw a couple comments about the X count being incorrect I figured I could help out. As mentioned in a couple earlier posts TDS is intended to gather data that would be difficult and/or time consuming to do manually and present the data in a usable format. The simulated scoring is intended to give the user an idea of how the would have scored in competition and to suggest sight adjustments to maximize their score.
The calculations for scoring an 'X' are different for the 25 and 50 meter targets. Currently TDS displays the 25 meter target score in the Virtual Group dialog. The 50 meter score is only displayed when the data is printed. It's really a matter of screen space, there's not enough room for both scores in the dialog. I can switch to the 50 meter score in a future version of TDS if that would be preferable.
Here's the code that calculates whether or not the shot is an 'X'. The variable "dSize" is the calculated distance from the center of the bullet hole to the center of the bull. This code only checks for the 'X', the next few lines check for a "10" without the 'X'.
25 meter calculation:
if( dSize < 0.033 ) // .112" - .079" (dot size), obliterated dot
{
nScore = 10;
bBull = TRUE;
}
...
50 meter calculation:
if( dSize < 0.127 ) // .112" + .0.15" (dot size), touching dot
{
nScore = 10;
bBull = TRUE;
}
...
The scoring calculations for the WRABF, and other targets, may not be perfect. That's why I specify that it's "for informational purposes only and may not reflect the official target score".
If you have any questions about TDS or the other OnTarget programs send an email to: ontargetsoftware@msn.com
- Jeff