Problème cumul dénivelé positif sur une course

[Mi_chael]

Quelle montre as tu?

[PatBess]

@Mi_chael S9 Baro

[Mi_chael]

Tu l’as porte au poignet droit ou gauche?
Avais tu une veste? Était elle en dessous ou au dessus.

[PatBess]

@Mi_chael Poignet gauche et non, pas de veste au dessus, mais ma manchette descendue contre des fois… Ce serait l’explication ?

[Mi_chael]

J’ai déjà rencontré des erreurs de dénivelé lorsque les trous du capteur barométrique sont obstrués par intermittences. Pluie, sueur, vêtement…

Est-ce que ton altitude de départ ainsi que ton altitude Max correspondent à la réalité?

[PatBess]

@Mi_chael Ça je n’ai pas vérifié. Je vais regarder.

[freeheeler]

@Mi_chael
did you notice that with s9b, too?
I only observed this with suunto core.
isn’t fusedalti filtering or correcting it?

[PatBess]

@TELE-HO How can I know about fusedalti ?

[Mi_chael]

Fusedalti corrige l’altitude dans les 10min environ après le début d’un Moves.
Néanmoins il te faut une bonne couverture gps.
Il me semble que ça te créer un décrochage sur la courbe de vitesse verticale lors de l’ajustement.

[freeheeler]

@Mi_chael
I’m so glad we have Google translate
it would be helpful to see the alti graph… if this run is mostly flat the difference between the watch and the “correct” total ascent could be because of the famouse 3meters “issue”

[A Former User]

@TELE-HO said in Problème cumul dénivelé positif sur une course:

if this run is mostly flat the difference between the watch and the “correct” total ascent could be because of the famouse 3meters “issue”

How can it be mostly flat if the gain is more than 5 km in in 100 km? That means the average grade is about 10% (assuming a similar amount of elevation loss).

And yes, even if all the climbs and descents are larger than 3 meters, Suunto 9 still counts less ascent than actual. I posted about this issue in details in the past.

[freeheeler]

@silentvoyager
sorry, I did not want to say most of the trail is flat… I imagined if a long enough distance is small ups and downs, not entire trail.
you’re right, we’ve had this topic couple of times.
I understand that finding the answers is not easy even with a good search function

[PatBess]

@silentvoyager You’re right, it wasn’t flat !!
So it’s a problem with the watch ? A difference of 1000 meters is a big problem on that race !!

[freeheeler]

@PatBess
did you compare your alti graph with the original already?
I just looked it up and saw that your screenshots are similar to the original graph (don’t get me wrong, for sure it’s not flat) but it might be something in the detail…
the original graph shows tonns of small spikes

[freeheeler]

spikes example…
I’m interested in that because I went on the same trail last week with 2 different total ascent results

[PatBess]

@TELE-HO Yes there was a lot of small spikes ! I don’t know how to have more details with the file my S9Baro recorded…
Maybe the software of the watch is sort of “flattening” the smaller pikes, which could explain the elevation difference ?

[freeheeler]

@PatBess
that’s what I also like to know…
first pic is with total ascent of 240m.
second pic is with total ascent of 286m. exactly the same trail but the 2nd day with some “noise” in the recording. I assume day 1 was right and day 2 with the noises, something went wrong. it your case it must be vice versa…

[77alex77]

Hello,

I ran the Marathon des Causses, Festival des templiers, Millau on Saturday : 37 km and 1780m ascent. My S9 baro recorded 36.5 km and 1658m ascent, an error about of 100m. I syncronized AGPS the morning before the race. One day before I recalibrated the compass and requested an automatique adjustment for altitude.

(Félicitations PatBess pour ta course)

[PatBess]

« Flattening » 3280 feet is quite a big issue for me !
I’m very disappointed !