![]() |
Pool SwimmingDownloads: 1,406 •
|
|
Tisztul_A_Visztula wrote:GC is shit. I always promote ST3 and some of its plugins on forums.garmin.com, because some of the complaints there have nothing to do with the hardwares or the unit firmware, just simply related to GC. I am not surprised at all that now I faced another example.
Burnt Toast wrote:Tisztul_A_Visztula wrote:GC is shit. I always promote ST3 and some of its plugins on forums.garmin.com, because some of the complaints there have nothing to do with the hardwares or the unit firmware, just simply related to GC. I am not surprised at all that now I faced another example.
On that note, it amazes me that a lot of people take what GC spits out as "gospel" and is the ultimate answer. If GC says so, it must be true.
k3sk wrote:...If you doubt about GC, then you must doubt about 910XT in this case, too. And if we doubt about 910XT itself, we cannot believe ST3 results anymore because they are imported from 910XT
In no manner I mean that 910XT is without bugs. What I am trying to find out here is what values I can rely on.
texmurphy wrote:Garmin Connect will always report the value from their devices for lap times from the lap summary values. GC does not recompute these values whereas ST will.
old_man_biking wrote:It's a general mechanism in human minds.
Whatever you see first, and probably presented by a "reliable authority", is taken as the one and only undoubted truth...
k3sk wrote:Hi OMB,
I did read your post carefully and understood it. I appreciate it, but it didn't reply to my questions.
I will try to summarize all my findings:
1. Pool Swimming plugin shows length intervals almost correctly, except the fact that the values are not rounded properly (decimal digits are only trimmed) and this has confused me (e.g. value 70.099 is shown as 70.0 instead 70.1):
e.g. if we take the 1st lap instead of the 2nd one we get the following:
length 1: 00:01:11.0
length 2: 00:01:05.3
Total shown in PS is 00:02:16.4 and this is not following common rules of mathematicsThat's why I think you have chosen the second lap for your explanation
2. However, confusing is the lap time. I have inspected the FIT file using FitSDK and it has revealed, that the lap time present in the FIT file is not a sum of length intervals. Now the question is, why? Is it a firmware bug? What value is authoritative for 100m swimming (2 lengths)?
3. When I use SportTracks without OMB plugins I get different results in Split view than with OMB plugins.
4. When I use SportTracks with OMB plugins, I get non matching results between PS view and Split view (as it was shown in "PoolSwimmming versus splits.png" screenshot). Furthermore, the Split view has the 1st column (Time) values always ending with .86. Isn't it suspicious? I don't believe I swam all laps exactly with .00 times. This behavior is visible only when I use OMB plugins.
5. I have noticed also another strange thing in PS view - in the upper view I cannot see more than 53 lengths even if I use zoom out tool. I cannot even move the view to the left to see lengths beyond length 53:
What I am looking for is an application which can precisely store my results and allow me to analyze them. The application which I can rely on. I consider a Pool Swimming plugin a nice piece of software but some inconsistencies prevent me to fully rely on it.
Kind regards,
Peter
old_man_biking wrote:Re 1: PS plugin rounds to 1/10 sec. So if lenght 1 is in fact 1:11.04 and lenght 2 is 1:05.34, the sum is 2:16:38 which is rounded to 2:16.4. That's maths.
And you're right: I've choosen lap 2, because you need less maths to understand it and I didn't want to write the explanation in the previous line. No I had to![]()
old_man_biking wrote:Re 5: If you encounter such problems, please post and attach the affected .FIT file.
Users browsing this forum: No registered users and 2 guests