Number of downhill runs in alpine skiing
-
@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.
-
@MdzOtt said in Number of downhill runs in alpine skiing:
…“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.
Have you tried looking at the GPX or FIT file, do you note any count of runs written into it?
-
@Umer-Javed I haven’t tried. But I will and report back.
-
@Umer-Javed Interestingly, if I export from Sport-Tracker using GPX, Strava reports the same (correct) number of runs as Sport Tracker. The same happens if I “Export GPX workout” from SA (which seems logical, as it seems that this is the same file). However, if I “Download FIT file” from SA and upload it to Strava, the double number of runs shows up.
I think that Suunto is passing the FIT file to Strava (and the problem is within the FIT file).
Unfortunately, I have no tool to look inside the FIT file to see what information is there. -
@MdzOtt said in Number of downhill runs in alpine skiing:
Unfortunately, I have no tool to look inside the FIT file to see what information is there.
If you’re interested in diving deeper, you may try the https://runalyze.com/tool/fit-viewer you could upload the .fit and see if you can find a field for runs and what the count is from the file from SA.
-
@Umer-Javed thanks!!
-
I revice this topic because I have the same issue between Suunto and Strava.
My Suunto App displays 18 runs, while the Strava app displays 37 runs. After analyzing the FIT file from Suunto App I discovered the issue. At the end of the file there is a statistics for the entire activity including number of laps = 37. This is the source used by Strava to count the runs. If this field is missing, than Strava calculates the number of runs by itself.
Suunto developers, please set the correct number of laps/runs into the FIT file so that Strava can read the correct value. Thank you!
== = TYPE=0 NAME=session NUMBER=18 --- timestamp=1077629177=2024-02-23T13:26:17Z --- start_time=1077612424=2024-02-23T08:47:04Z --- event=8=session --- event_type=1=stop --- sport=13=alpine_skiing --- sub_sport=9=downhill --- first_lap_index=0=0 ***--- num_laps=37=37*** --- min_heart_rate=45=45 bpm --- avg_heart_rate=106=106 bpm --- max_heart_rate=166=166 bpm --- avg_speed=2191=7.888 km/h --- max_speed=14540=52.344 km/h --- total_calories=1364=1364 kcal --- total_timer_time=16752340=16752.340 s --- total_elapsed_time=16752332=16752.332 s --- total_distance=3670800=36708.00 m --- total_ascent=3684=3684 m --- total_descent=3688=3688 m --- max_altitude=12954=2090.8 m --- min_altitude=9740=1448.0 m --- training_stress_score=1903=190.3 tss --- total_cycles=2926=2926 cycles --- avg_temperature=17=17 deg.C --- max_temperature=25=25 deg.C --- avg_cadence=58=58 rpm --- max_cadence=254=254 rpm --- total_training_effect=23=2.3 --- time_in_hr_zone=14688130=14688.130 s,1182.209 s,645.201 s,173.892 s,61.085 s --- pool_length_unit=0=metric --- pool_length=2500=25.00 m --- 0_2_recovery_time=106140=106140 --- 0_4_peak_epoc=133=13.3 ==
