Wildly incorrect spiky altitude data

[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

[Dimitrios Kanellopoulos]

@lexterm77 is this like this on your suunto app ?

[lexterm77]

@dimitrios-kanellopoulos

Yes, the watch recorded it that way, on the outside of my sleeve.

[Dimitrios Kanellopoulos]

@lexterm77 yeah then I only can say it can happen. What activity was this btw?

[lexterm77]

@dimitrios-kanellopoulos

Running on gravel trough forest, double track. Some downed trees skipped over.