Re: Chronographing questions
Mouse,
Definitely not trying to imply I know more about this than others here, but I've spent a lot of time thinking about this issue and trying to learn more about how my beta chrony functions, so I'll take a crack at responding to the first two parts of your question.
a) One way to try to check the MV readings from a shooting chronograph is to compare your <span style="font-style: italic">actual</span> drops at some distance to the drop <span style="font-style: italic">predicted</span> by a ballistics program such as JBM. At 600 yd, JBM gives the drop for an SMK 175 gr BTHP as 105.2" or 4.9 mil at 600 yd (using the Litz BC, 70 degrees, 2.4" sight height, air press = 29.92, MV = 2540 fps). At a MV of 2590 fps, the drop is predicted to be 100.4"/4.6 mil under the same conditions. If someone is confident enough in the precision of their shooting, they can get a feel for whether their chronograph is reading hi/lo by how their actual drop compares to the drop predicted for the MV given by their chronograph.
b) The SD and ES given by any chronograph are calculated directly from the numerical data collected by simple mathematical algorithms. These numbers should be absolutely correct for the <span style="font-style: italic">actual</span> values collected in any given string (data set). However, like any other data set, if the collected data are lacking in accuracy or precision, then any values derived from them by an algorithm will also be in error. Take the following two 10-shot MV strings for example:
<span style="text-decoration: underline">String 1</span>
2591
2597
2583
2601
2588
2576
2593
2596
2591
2584
<span style="text-decoration: underline">String 2</span>
2541
2547
2533
2551
2538
2526
2543
2546
2541
2534
The values in String 1 differ from those in String 2 only in that they are each 50 fps higher. The mean, standard deviation, and extreme spread for these two strings are as follows:
String 1: mean = 2590, SD = 7.5, ES = 25
String 2: mean = 2540, SD = 7.5, ES = 25
What this demonstrates is that as long as the chronograph always gave a reading <span style="font-style: italic">exactly</span> 50 fps high, it would only affect the mean MV value determined from the string, but not the SD or ES.
However, it seems pretty unlikely that a chronograph under actual use would read every velocity high (or low) by exactly the same amount every time. So in reality it is more likely that MV, SD, and ES would all be affected by a chronograph that gave inconsistently high (or low) readings, even if it tended to be one or the other.
By analogy to comparing actual drops to those predicted from a ballistics program, one way to get an idea of how well the chronograph is performing in terms of hi/lo readings is to record individual shots at some distance to the MV recorded for that shot. If they are <span style="font-style: italic">real</span>, large changes in measured MV would be expected to give noticeable vertical stringing if the range is great enough. The vertical stringing should correspond to the extremes (hi/lo) in MV. As with comparing actual and predicted drops, the range needs to great enough to outweigh the normal group spread for a given shooter, and of course, the precision of the driver needs to be sufficient for such a test to give any useful information (LOL).
Even though I enjoy thinking and learning about issues like this one, I have to tell you that in reality, I don't worry about it too much at the range any more, primarily because I realized the major limitation in my shooting was me, not the accuracy of my chrony. Just to check it, I have done what I described in a) above for several different .308 factory loads that I chrono'd. The drops calculated by JBM for the MV values given by the chrony were very good for every one at 600 yd. I don't know whether that means my chrony is well-calibrated, but the data it generates seems to work, so now I just go with it. It's also possible that the chrony is behaving so well only because I accidentally shot the support wires out on one side a couple months ago and perhaps it fears further retribution if it acts up (LOL).
FWIW, the info that came with the beta chrony states that it has an accuracy of 99.5% or better. That translates to +/- ~13 fps for an avg MV of 2500. If you believe the statement in the product manual, of course. How the company actually calibrates the instrument, I have no idea. That was one reason I tried to compare actual to predicted drops, just to get an idea of whether it was in the ballpark. Since doing that however, I decided I have so many more important things to worry about (like basic shooting fundamentals) that I quit worrying about whether my chrony was accurate so much anymore and just use the values it gives and then determine actual drops with that particular load. If someone's chronograph was consistently high or low, it wouldn't be a big deal to back-calculate approximately how much it was off, then re-run the MVs through JBM, or just know that you have to increase (or decrease) the JBM predicted drop by that correction factor, which can save a lot of time and ammo over the long run.