Started when using the new site. Coros has Effort Pace as a dev field and the new site is not interpreting that field correctly.
Before and After screenshots and Coros file in Attachment
Can you have a look please?
Thx
Actually, this closely matches the issue with the TymeWear fields. Not a dev, so not sure if it is exactly the same problem...
Coros dev field not behaving correctly
Coros dev field not behaving correctly
- Attachments
-
i122861792.fit- (162.85 KiB) Downloaded 25 times
-
-
Re: Coros dev field not behaving correctly
Is there any chance you can upload test files please? I do not use Effort Pace myself so I'll need test files. Thanks,
Re: Coros dev field not behaving correctly
There's a FIT file with the Effort Pace field attached. Do you need anything else?fulmar2 wrote: Fri Feb 06, 2026 1:50 pm Is there any chance you can upload test files please? I do not use Effort Pace myself so I'll need test files. Thanks,
It's basically a stream that looks like GAP (in m/s) but Coros has an algorithm that behaves a bit like Power. Screenshot from the file viewer attached.
- Attachments
-
Re: Coros dev field not behaving correctly
OK, I think I see what the issue is. Sometimes the "Effort Pace" goes to zero in the GOTOES output file. This is because I didn't "carry over" the developer data fields in the way I used to. I've been working on an "intelligent" carry over algorithm, which I plan to introduce soon. I'll put it as a checkbox at the bottom so the user can decide to use the new "engine" or the old one. I think that this will address all of the recent concerns about carry over in one fell swoop. This option should be available as beta in about 1 week. After we confirm that everyone is happy (feedback requested)... I hope to make that be the one and only output path.