Garmin Xero - update

gregmark24 said:
The Garmin is calculating SD way too low, ie optimistic. 9.3 vs 12.0. I believe the actual displayed velocities are accurate, and don't know if my friend's early-made Garmin is calculating SD wrong from three velocities, or if all Garmin's are. I'm hoping other folks with both Garmin chrons and Excel (or other apps to calculate sample SD's) can verify the results agree or not
Click to expand...
In my short time using the Garmin I've had 2 firmware updates. The first when I set it up and the second last Saturday. Don't actually know if the update affects the calculations you mentioned.

The numbers you stated, (9.3 & 12), are these SD from a Garmin and LR? If so, who is to say which is actually correct? The comparison between the two isn't valid. The only way to accurately measure accuracy is to measure each against an industry standard chronograph. Only this measurement will provide a usable comparison. If you don't, all your getting is data output that has no basis in accuracy. That can only come from testing to a standard, not against a comparison of chrono to chrono out there. If folks continue to test one make against the other, the only result you get will be a disparity between the two chronos and BOTH may be wrong. Or maybe one will be right. It's a coin toss.
 
Last edited:
gregmark24 said:
Ok. Here you go. For a point of reference, look at Load #2. Take the three velocities 2632.1, 2609.9 and 2628.9. Excel STDEV says 12.0, and Excel STDEVP comes up with 9.8. Garmin has 9.3. I'd say that Garmin calculates SD wrong. This is from the session with my buddy, and he got one of the early Garmin units. Perhaps it has been fixed by now. I'd be interested if any of you have three shot strings that give you the correct SD; or not. When I entered in the values from my LabRadar, my Excel SD results were EXACTLY the same results as the LabRadar.

View attachment 521732
Click to expand...
I'm not sure where the difference between 9.8 and 9.3 is coming from. The only thing I can think of is the garmin treats decimals behind the scenes differently. I pulled a recent 5rd string and got essentially the same stdev (red is the excel calculated value)
1702699856453.png


Edit: I am also seriously impressed at GRT's ability to predict your velocities, it is never that accurate for me.
 
Aloeus said:
I'm not sure where the difference between 9.8 and 9.3 is coming from. The only thing I can think of is the garmin treats decimals behind the scenes differently. I pulled a recent 5rd string and got essentially the same stdev (red is the excel calculated value)
View attachment 521782

Edit: I am also seriously impressed at GRT's ability to predict your velocities, it is never that accurate for me.
Click to expand...
Is it possible that Garmin drops anything after the period (.x)? I've not tried to calculate this, I'm only taking a jab at it...
 
Thanks for the review....you've convinced me that it's worth picking one up.

I used my old CED M2 a few weeks ago, and didn't even mess with connecting it to my laptop to transfer the data...just manually wrote down the velocities and did the calculations myself.
 
Ok. We're there! My buddy mis-typed his Garmin-read SD on the 2nd string of three shots. He typed 9.3, and it should have been 9.8. Standard Deviation for his sample (small size) should have been 12.0, but the SD for a population (large sample size) is 9.8. Garmin calculated for the wrong type of standard deviation. From Aloeus' message above, Garmin is [still] doing it wrong. 3 shots, 5 shots is a SMALL sample size and SD should be calculated with a denominator of sample size -1, or (N-1). "Population" is a LARGE sample size with more confidence of results and is calculated with a denominator of just sample size (N). I believe Garmin is making SD look better than it is. Significantly.
1702705097799.png
 
Last edited:
gregmark24 said:
Ok. We're there! My buddy mis-typed his Garmin-read SD on the 2nd string of three shots. He typed 9.3, and it should have been 9.8. Standard Deviation for his sample (small size) should have been 12.0, but the SD for a population (large sample size) is 9.8. Garmin calculated for the wrong type of standard deviation. From Aloeus' message above, Garmin is [still] doing it wrong. 3 shots, 5 shots is a SMALL sample size and SD should be calculated with a denominator of sample size -1, or (N-1). "Population" is a LARGE sample size with more confidence of results and is calculated with a denominator of just sample size (N). I believe Garmin is making SD look better than it is. Significantly.
View attachment 521796
Click to expand...
I'm not going to attribute it to malice or deception- I'm not sure Garmin has anything to gain by making SDs smaller, but I do agree it really should be sample stdev. Hopefully this is something they can patch into it (or at least the option to change it).
 
Below is a large sample size of 86 shots. STDEV and STDEV.P are very close with a large sample size with Excel rounded to one decimal place like the Garmin results. Originally posted with Excel having 2 decimal places which didn't really make sense since the results were being compared with the 1 decimal place Garmin.

Garmin AVERAGE
1078.8​
1078.8​
Excel Average
Garmin STD DEV
9.8​
9.9​
Excel STDEV
Garmin SPREAD
50.9​
9.8​
Excel STDEV.P
Session NoteVolq Clean Rifle Norma Tac-2286 Shots
 
Last edited:
It is possible that Garmin truncates the extra digits to the right of that 0.1 place instead of rounding. Regarding your large sample vs population Excel differences, sample (STDEV) will always produce a larger result than population (STDEVP) because the denominator will be N-1 for sample and N for population, producing huge differences for small samples and minimal differences for large populations. I think the cutoff between sample and population is a size of around 30
 
gregmark24 said:
It is possible that Garmin truncates the extra digits to the right of that 0.1 place instead of rounding. Regarding your large sample vs population Excel differences, sample (STDEV) will always produce a larger result than population (STDEVP) because the denominator will be N-1 for sample and N for population, producing huge differences for small samples and minimal differences for large populations. I think the cutoff between sample and population is a size of around 30
Click to expand...
So if I have a case of Tac-22 (5,000 rounds). That would be the population? And if I were shooting all 5,000 rounds you would use STDEV.P. In this case, I selected two boxes to shoot so that was a sample of the 5,000 even though its a fairly large sample from a shooting stand point so the correct use would be STDEV. Another way of looking at it with much smaller numbers would be that if I reloaded 200 rounds and randomly selected 10 to test, you would use STDEV. If the following weekend I went to a competition and shot the remaining 190 rounds and added in the data from the 10 test rounds, the proper formula would be STDEV.P since it was the entire batch or population?
 
orkan said:
When I last talked to the Garmin rep... she said they had over 24,000 back-orders for these units.

Pretty soon, guys will be able to pick these things up for $400 everywhere. lol

When these back orders hit, all the mom-and-pop shops that got conned into their 10-unit opening order, will be cutting each others throat to sell them for $5 over cost. 🤣



-----------
Follow on Instagram
Subscribe on YouTube
Amazon Affiliate

Click to expand...
Just glad I got mine been holding off buying a Labradar, just glad I waited for the new technology.
 

Similar threads

Coyote Shadow Tracker
Garmin Xero Case
2 3
Replies
33
Views
8K
dustbag
D
quigley257
Garmin Xero C1 Storage
2
Replies
18
Views
2K
Alpha Echo
Alpha Echo
H
Garmin Xero C1 Pro Chrono
2 3
Replies
30
Views
4K
Justice1327
Justice1327
K
Soft Case for Garmin Xero Chronograph
Replies
4
Views
464
quigley257
quigley257
Darryle
All you Xero owners looky loo
Replies
12
Views
1K
338 dude
338 dude

Recent Posts

Top