i have some Rowing Activity Intervals.icu
I did a 5km , is computed by Concept2 and Garmin , but when uploaded said 4.99km ( i dont know if this is the reason, and how to solve) I change to 5km trying to fix , but dont .
Any ideas?
I’ve noticed this happening to me on some occasions a well.
I suspect it’s due to some rounding “error” somewhere.
You mention both a Concept 2 and a Garmin recording, do they both suffer from the same issue?
I don’t do a lot of pieces or racing on the erg so in practice I just connect the PM5 monitor to my Garmin watch through ANT+ and use the watch to set intervals and distances. The PM5 is just running along for reference as it is easier to read.
Obviously this works better for intervals by time instead of distance.
Hey thanks for share yout thoughts.
NO, in the garmin and Concept2 - no problem! i tried uploaded with Garmin and COncept2 file , but both got the same error when uploaded to intervals.icu
i tried not use Garmin Watch to set distance etc… , because Garmin dont read distance only RPM , i use recorded with him “just in case” (plan B)
I have seen one other report of this and in that case the actual fit file from the Concept2 was showing 4.99km and not 5km. You could check the file on fitfileviewer.com.
I am a little reluctant to add a small fudge factor for this, but maybe that is what the other services are doing.
Hi,
I am also seeing this on activities coming from Concept2; initial distance is often entered as objectif (500m, 1km, 2km, 5km, 6km, 10km) and those activities are usually leading to FIT file showing a shorter total distance (499.99m, 999.99m, 1999.99m, 4999.99m, 5999.99m, 9999,99m). All are missing those 10cm that would allow intervals.icu to report best effort appropriately.
As for Garmin, I guess they are just displaying rounded data and they don’t report best effort like Intervals.icu.
1 Like
Yesterday I did an indoor row where I preset the intervals as 5000m in my Forerunner and connected it through ANT+FEC with the PM5 monitor.
One of the intervals is indeed showing up as 4.99 km, the others are fine.
I’d say this has nothing to do with Intervals.icu.
2 Likes
Yep , i use Fitfileviewer to see this I tried correct in many ways but only got me frustrated. I change the activity to 5km , but this dont reflect on my “race effort” Season , Pace profile - Any way to change that?
Can you please mail me (david@intervals.icu) that fit file. Tx.
I have just added a 10cm fudge factor to the last distance value for virtual row fit files. It sorts out this problem. You need to do Actions → Reprocess file to get the fix.
1 Like
I’ve asked this prev in Garmin Forums for FIT files and the encoding and things ike that. I basically got the answer of something like “it happens” so they basically just fudge it…
1 Like
Thanks DAvid , Thanks app4g for the info.!
I imagine i cant “solve the problem” myself next time . Any suggestions?
Garmin uses the intervals as recorded into the FIT files.
Intervals.icu uses the raw data to calculate the distances and sometimes the distances won’t match up due to the way the indexes in the FIT file aligns to the distances. (also GPS distances are always gonna be like .xxxx and never a full integer)
As Garmin uses the intervals “as recorded” by the firmware instead of calculating it, this happens.
My Suggestion is to ignore it, but of course I understand that you want it to be included as it’s your “5K” best kind of thing.
Just Like strava, when using GPS, they recalculate the distances instead of numbers from Garmin so we end up with 99.9km or 159.9km instead of full 1000/160km metric/imperial century… most of us just ended up as cycling just an additional 100m “just in case”
Is this a possibility for your use case?
1 Like