Wildly incorrect spiky altitude data

[Mff73]

@sesam
issue somewhere in Suunto backend from beginning of the week, and normally solved now
https://forum.suunto.com/topic/5854/altitude-bug-in-one-fit-file-export/7
you should re export the fit file, and import it again, and it should be OK.
it is for my case.

[sesam]

@mff73 Nope, this is something different. SA also has the altitude displayed incorrectly as well as the post-workout info screen on the watch.

[Mff73]

@sesam
so maybe worth sharing this SA activity link for Suunto support to analyze raw data in cloud. It may be side effect of the same issue (which symptom are similar, except you have SA showing it).

Or if you have Android phone, you can find raw data file yourself and import it in QS to analyze it.

[sesam]

@mff73 Okay I will try that. I’m concerned because the data was displayed post-run on the watch, so it has nothing to do with Suunto’s cloud or app. It’s either watch software or watch hardware.

[isazi]

@sesam or the way you did wear the watch in this particular occasion.

[Mff73]

@sesam
Ok, we missed this info that watch also recorded 600m ascent (which was not the case, at least for me and the cloud issue).
but, but, but, … who knows with bugs
see what you can find and/or share the activity link if no privacy concerns.

[sesam]

@isazi I was thinking about this… I was wearing the watch the same way as always, over the sleeve of my jacket, using a 3rd party HR band. The only difference was that it was snowing like crazy, my clothing and the watch was covered in snow after a short while.

[isazi]

@sesam bingo! It happened to me under the snow a week or so ago, and something similar to @stromdiddily and @freeheeler I believe not long ago.

[stromdiddily]

@isazi I wonder if there were changes somewhere. I don’t remember this popping up as much last year…

[isazi]

@stromdiddily the release notes of version 2.13.18 says:

Fix some pressure sensor issues

But I actually do not know if it is related or not.

[freeheeler]

@stromdiddily
weather changes… we haven’t had that much snow in ages!!

It’s a bit of a drawback that we only have one sensor for measuring. Two sensors or at least channels from different sides would really really help here.

I know that Suunto uses Creo to design watches… maybe I should apply as a designer and give them a hand with the future baro watches

[stromdiddily]

@freeheeler well, it’s been raining pretty steady where I’m at since…forever lol

I really liked the location of the sensor on the A3P. I am not a fan of the side sensors for this very reason.

[cosme.costa]

@freeheeler said in Wildly incorrect spiky altitude data:

I know that Suunto uses Creo to design watches… maybe I should apply as a designer and give them a hand with the future baro watches

Don’t go so fast, if there is an opening I’ll apply first…Creo is my friend too.

[freeheeler]

@cosmecosta
maybe they need 2 great design engineers

[stromdiddily]

And then it totally redeems itself. Off by 5 feet at the top of the summit on today’s run.

[lexterm77]

@stromdiddily

I think it is better to just feed all data into tensor flow and give it as much as possible correct keys to learn how to deal with these conditions. I had better experience with S9 when biking than with A3P. Under certain conditions with S9B I have 600m ascent instead of 6m but with A3P I had predictable errors due to wind.

[freeheeler]

@lexterm77
did you have A3P set to 1s or 10s recording?

[lexterm77]

@freeheeler

Always 1s, but regardless if should filter out wild swings in altitude with steady wrist on a bike.

[Dimitrios Kanellopoulos]

hi there was a fit file issue export. This is fixed now. Can you validate ?

[lexterm77]

@dimitrios-kanellopoulos

SA -> .fit -> TP Upload

Real ascent is 10m stairs at half and then same route back. Route is flat. Recorded with S9B.

Edit:
Pic add