Graph problem: Speed vs Time is wrong in trails with more than 2 trailpoints
GoogleCodeExporter opened this issue · comments
What steps will reproduce the problem?
1. Use new version 1.2.821
2. Load a track and select a trail with at least 3 trail points
3. Select speed/Time graph
What is the expected output? What do you see instead?
The speed (but also hr and power) vs time graph is clearly broken, are only
displayed the values (and the lines connecting them) in correspondence to the
trail points, while the speed vs distance graph is ok.
Attached a graph showing the problem (speed vs time) and the corresponding
speed vs distance
This issue is only for the new version of the plugin, previous version is ok.
Original issue reported on code.google.com by fabryl...@gmail.com on 9 Apr 2013 at 8:54
Attachments:
Thanks for the report, but I cannot reproduce the problem.
The speed over time is for some reason only defined in the trail points for the
graph in the example.
The HR over time looks OK to me, do you have another example?
Can you please provide the activity and your Trails configuration?
The configuration is in System.Preferences.xml, the
"86c3b0eb-1c41-4817-b97a-e054bf4ac41c" section if you do not want to include
the complete settings.
What trail is selected?
Original comment by gerhard....@gmail.com on 9 Apr 2013 at 9:36
Hi,
I didn't find the "86c3b0eb-1c41-4817-b97a-e054bf4ac41c", but I believe I have
found the correct chunk of the preference file and I have attached it.
Also attached the .fit file of one of the problematic tracks.
The name of the trail is Maddalena
Original comment by fabryl...@gmail.com on 9 Apr 2013 at 9:53
Attachments:
Problem reproduced. It is related to some core structures in ST. All track info
is supposed to be saved in order. In some situations the plugin inserts points
in the tracks, to avoid border effects when chopping up an activity. For
instance speed is strange if there is no point where the trail starts. The core
ST structures are not always handling this correctly. See what can be done
without slowing down (too much?).
I got the problem on an old activity too, cannot see the trigger right now, so
no workaround.
Original comment by gerhard....@gmail.com on 10 Apr 2013 at 10:37
- Changed state: Started
Hi, I understand, but how come the problem is only present in the last release
and not in the previous one?
Thank you.
Original comment by fabryl...@gmail.com on 10 Apr 2013 at 10:54
There has been many internal changes in this release. The last number is the
revision number for the commit. As that increased from 721 to 821, there has
been quite a lot of changes. (There are some change in working too, it is not
like 1/8 of the plugin is written since last release.)
As the problem is slightly "random" (see below), it may be that an unrelated
change just happens to trigger the problem.
However, the problem acts a little randomly. I could suddenly recreate it on
one of my activities, then I could not longer recreate it.
The solution is to always resort the time tracks before smoothing the data, for
presentation.
Original comment by gerhard....@gmail.com on 12 Apr 2013 at 10:54
- Changed state: Fixed