Totalt ascent/descent doesn't seem to match elevation graph

Aleksander H

@fenr1r Thanks. I’ve given it a good rinse now without resorting to a toothbrush. I’ll see how it fares today.

Aleksander H

Today’s run fared better. Some unexpected drops in elevation but not as bad as they’ve been earlier. Maybe I’ve not been cleaning it well enough.

That said. I’m still confused how I managed to get 0 m ascent on activities where the elevation graph clearly shows me going up .

Mff73

@aleksander-h said in Totalt ascent/descent doesn't seem to match elevation graph:

Today’s run fared better. Some unexpected drops in elevation but not as bad as they’ve been earlier. Maybe I’ve not been cleaning it well enough.

That said. I’m still confused how I managed to get 0 m ascent on activities where the elevation graph clearly shows me going up .

as asked @isazi in the other post, do you also have 0m in the watch ?
but i guess at this stage that we (just users) can’t go further into analysis with any Suunto insight
fit files, QS import, etc…, are just what Suunto clould let export from your activities, not any raw informations (if they are some).
if i had a S7 i would have searched in my android phone or in the watch itself if there are some of these raw data file after a workout, but i have not …yet ?

Aleksander H

@mff73 the watch doesn’t show ascent info at all in the diary for the activity with 0 ascent. Only elevation graph and descent information. I’m guessing its not showing data with no data to show.

Unfortunately I can only check this for one of the two activities I have with this problem. I got a new phone 1 February and therefore needed to reset the watch. The first activity with this issue was before the reset, so that one is gone from my watches diary.

Dimitrios Kanellopoulos

@aleksander-h I suspect this is due to slow ascent

Dimitrios Kanellopoulos

@aleksander-h ill report this anyways

Aleksander H

@dimitrios-kanellopoulos
Going from 240 to roughly 350 in about 35 minutes is slow? I guess I must be in worse shape than I thought .

Dimitrios Kanellopoulos

@aleksander-h there is a fix already done for that.

Aleksander H

Incidentally, that graph is from a different activity that gave 0m. To avoid confusion, I’ll just post direct links to both here:

https://quantified-self.io/user/DUrrVK0qMVZO5TtAP0r6Ox2HVLD2/event/48100bfe1ddfeee6242d124cc67d4cbbff0fc13357bac4207d10f0b9d3bfb895

https://quantified-self.io/user/DUrrVK0qMVZO5TtAP0r6Ox2HVLD2/event/583f92a0b4ceb9d5406432cd03971f10e2ae5252eca6503191648ae1ef9ba1a0

And below is the activity which was posted by @mikulass in another thread:
https://www.suunto.com/sk-sk/move/mikulasstrelecky/6047bd0e148abc47025d3e17

Aleksander H

@dimitrios-kanellopoulos oh really? In the app? Backend?

Dimitrios Kanellopoulos

@aleksander-h needs watch update but yes its fixed and spotted beforehand.

Aleksander H

@dimitrios-kanellopoulos awesome. I guess there’s nothing to do but wait for it then :). Thanks for the help, and thanks for building such an awesome free tool (quantified-self).