Number of downhill runs in alpine skiing
-
@mdzott as far as I know, I am using s9 baro, when you start to descent the watch start the interval, and the interval is finished when you start to ascent.
If you have small descents and ascents the watch will record that as ski runs.
Alpine skiing sport mode syncing problem with iOS is another problem, still unsolved unfortunately. -
@nseslija
I did a small test recently and could not see a reasonable pattern… I did one decent without any bigger climbs that S9B with its 3m threshold would recognize and it showed 3 runs.
The theory that a longer pause might not be right either as I did a lot of quite similar pauses to get the fire out of my legshttps://www.suunto.com/move/skiingone/603a4763d03bd02037ba863d
-
@freeheeler
do you see that in QS, there seems only to be 2 laps (descents) vs 3 in the SA ?
-
@mff73
and the sum is not the total duration -
@freeheeler I only see one descent there… I must say that I didn’t experience such a behavior with the watch… Did you feel vibration when the watch started a new interval during your descent?
I can feel the vibration almost every time, and it is when I start to descent, and when the ascent starts on the chairlift. -
@nseslija
I rarely feel it. It’s only when I pay attention when I enter or leave the chairlift station. I never notice the unwanted descent count vibration -
@mdzott here is the link to the activity: https://www.suunto.com/move/marekdziedzic/6037d336cdd3874e077c7966
-
@mdzott In the activity i just posted, the total descent is ~3800 m, whereas, when you count the runs, it should be around ~2500 m.
-
@mdzott
I see 2’868m descent… it’s about alright.
but 62 runs… hmmm… -
@freeheeler when i looked at the SA, there were multiple runs of 2 m, 3 m etc. It seems that it counted every single step i took waiting in line to the chair.
-
@mdzott
possible, not good and not logic with the threshold… but only the dev teams knows
-
@freeheeler when you look at the move on the web site, it shows only 0.5 km laps. On the SA it shows “downhills” - I assume runs. The first few are fine, then it starts showing 0 m length, 5 m descent for 5-6 “runs” and then a longer one. Somehow the logic has failed the watch.
-
@mdzott
did you use the famouse lock button? -
@freeheeler I did. I have to under the jacket. What am i missing here?
-
@mdzott
nothing… I have the impression the ski mode simply does not work properly -
@freeheeler The development team could use the code that is available for Ambit 3 (and 2), as “Downhill Counter, Max speed, Distance”. It works like a charm. And the code is almost trivially simple.
-
@mdzott
for us developers it is more entertaining to re-invent the wheel
-
@freeheeler Then why is Stackoverflow so popular?
-
I am resuscitating this old topic - the new season, some of the same problems.
I started skiing again and the number of runs is still a problem. It has improved dramatically (SA adds a couple of runs, and they are quite legitimate (e.g., a short run to the chairlift).
The latest issue is how the activity is passed from Suunto to Strava. I thought it might be a Strava issue, but their response is that “if the platform with which the activity was recorded passes a number of runs, Strava will take it at its face value. If there is no such number, Strava will calculate it internally”. So it seems that Suunto is counting the runs in a strange way.
For example, the last time, SA reported 21 runs (https://www.sports-tracker.com/workout/marekdziedzic/63a0950e27a4974d2657ebe4), but Strava shows 43 runs. It seems that Suunto is passing some other number (some other variable) as the number of runs.
As we discussed before, this is not a huge issue, but possibly, this could be fixed. And as mentioned before, the Ambit 3 (and 2) reported these numbers correctly.
Btw. the total descent is much closer now, so I am not complaining.
S9 Baro
SA on Android
Ambit 3 Peak
Ambit 2 Sapphire -
@MdzOtt seems odd that SA would be able to know the correct run count but then Suunto would be storing a bogus number in the “supported” run count field - seems like this number includes the auto laps and how those segment the activity up artifically. I wish that Strava either allowed user to “correct” lap count like you can with elevation and override with their calculated run count with an algorithm based value.
