Suunto 9 baro very low elevation gain vs other brands

Egika

@Dimitrios-Kanellopoulos and that post should be made a sticky one

Oktan

OK. then last sentence from my side:

I’m a programmer too.
If I had in my program a constant (that its value can be argued) which fits 90% of the users, but the other 10% nagging the same issue over and over and consuming 20% of my time for explanation & proof - I would consider to let them change it (just a bit) for their own fine tuning ( and hapiness ).

Dimitrios Kanellopoulos

@Oktan the best would be (although not easy) to allow you to change that. Suunto cannot change it for all because then the other percentage will complain then for example.

I think that is the best solution for all. User power.

Oktan

I meant that 3 will be the default threshhold in the setting so the 90% will obviously wont change it, hence will not complain.
Anyways, thank you for your time, patience and all that you do for us.

Dimitrios Kanellopoulos

@Oktan yeah I got it pal.

fazel

@Dimitrios-Kanellopoulos Sorry - I thought my data was unconcerning and should have been clear. For me - this was within an acceptable range of deviation. I was relieved to be honest. You didn’t have to do all of this. I apologize for frustrating you.

Dimitrios Kanellopoulos

@fazel no no. It’s ok. I just wanted to explain that many times we can miss some fault etc.

To be honest if I could I would make you a tester as you did take the time Todo that great run and compare.

Actually at your data the s9 I think did a boo boo at the end as I said which I reported.

fazel

@Dimitrios-Kanellopoulos thank you - are you referring to the GPS track at the end?

I would love to be a tester. If that ever becomes a possibility please let me know.

Dimitrios Kanellopoulos

@fazel no at the elevation difference if you take a look.

fazel

@Dimitrios-Kanellopoulos oh wow. I see it now.

freeheeler

I went backcountry skiing with my friend who has well deserved and honourable inherited my A3PS. Of course the watches were not on the same arm, hence a comparison with the slightest scientific touch isn’t possible. However I would like to mention here that we went in the exactly same ascent track and his A3PS recorded around 100m less total ascent plus had issues with the track on the first few meters.

My takeaway is that S9B is not inaccurate at all.
Plus: it’s crazy good to enjoy sports without having issues like these in mind life is easier when we don’t worry

Oktan

@TELE-HO Can it be that his jacket blocked the barometer hole for a small period of time, and yours didnt?

freeheeler

@Oktan
no, not on A3PS and also not possible when I check the graph

stromdiddily

Interesting one for me today…S9 more than doubled the ascent/descent on my route. Green graph is a lot more jagged than the typical results.

Pouring down rain today but it was constant the whole time.

fazel

@stromdiddily so light green is today, dark green is a track from the same route ran in the past? I see this sort of delay with FusedAlti, @Brad_Olwin has as well.

stromdiddily

@fazel green is today, yellow-ish is from three months ago on the same 7 mile route. The start looks ok tbh but the green is reporting over 1k feet of climbing and the yellow is correctly showing 500ish feet.

Edit - QS feature request, ability to assign colors to merged tracks

freeheeler

@stromdiddily
the spike-ish graph looks like hydraulics did magic on the sensor… it’s a wild guess, but possible

fazel

@TELE-HO hydraulics = water?

freeheeler

@fazel
my assumption… pouring rain and the baro holes right next to the wrist… it seals great and the movement could create pressure that causes a down spike. once relieved it shows an up spike.
for our luck the recording is not set to every second as it was possible with Ambits, hence it’s somehow equalling out a bit… or let’s say it would be worse

Fenr1r

@TELE-HO Sleeve pump effect?