I have many instances where my Virtual Partner in my TCX is going back in time. I'd like to insert images (and attach files) to demonstrat this problem, but can't. Here's a simple route that exhibits the issue.
https://www.plotaroute.com/map/2034642
Virtual Partner settings --
Flat Speed 22.00 km/hr
Uphill: 1m up = 14.15m flat
Downhill: 1m down = -13.42m flat
Steep downhill: 1m down = -4.75m flat
Thanks for reporting this Paul. At what point in the route do you see this happening?
To insert an image, just copy/paste, like this screenshot ....
Starte a new thread ... How do I Insert an Image or even a File
@plotaroute admin It happens at the following points in the route. I'm thinking the model can create a negative time interval on some downhill sections. I'll think about it more later.
[IMAGE REMOVED DUE TO SIZE]
I think you're right Paul - the time adjustments for downhill sections are probably creating this anomaly. I think this would be very tricky to resolve. Reducing your Downhill adjustment from -13.42 would probably help.
I retract my notion that "the model can create a negative time interval on some downhill sections." If my math is right, with a flat speed of 22 km/hr, a downhill grade would have to exceed 21.6% to model a negative time with my steep downhill setting of "Every 1m down equivalent to -4.75m". I altered the setting to the fastest allowed of -10.00m which requires a downhill grade to exceed 45.45% to model a negative time interval. This had no impact on the number, 22, of negative time intervals.
All this said, perhaps it is time to create a more realistic model for cycling. A "simplified" Chung (Virtual Elevation) Method would be darling. I'm willing to consult on the algorithm.
Thanks for that analysis and your offer of help Paul. We've got a vast number of things already on our feature requests list and while we'd love to promise to do them all, realistcally this isn't something we'd be able to find time to look for the foreseeable future I'm afraid.
OK, set aside the virtual elevation method. There's still the matter of something wrong causing the model to back in time and I suspect the code, not my configuration.
Sure Paul, we'll certainly add it to the list to look into. It's quite an obscure one though, so I have a feeling it will be hard to track down and fix.