Real world data
-
@_marcus_ are you using DC rainmaker ? If yes his software cannot handle missing values (ie no distance update but we’ll elevation update) and ads 0 instead. Old way of dealing with data ie when a bike sensor did not broadcast power it was assumed to be 0. But dcr maker tool assumes all data is power.
-
@dimitrios-kanellopoulos thank you for clarification. Yes, it is DC Rainmakers Analyzer.
-
@_marcus_ Even assuming F6X is correct in that case, and it’s a big if, the ascent difference between S9B and F6X is 14m, or about 3%. It seems most of it is due to a single portion of the route near the top where S9B pegged you lower for whatever reason.
Honestly, I’d take that over 30% I just showed for F6X in Runalyze above
-
@mff73 slightly offtopic but I can never find the battery burn rate in QS activities, does it require enabling something extra? I was wondering if it was device limited because I remember the Spartan Trainer is a bit dubious for battery counting from memory.
-
@the_77
Do you have Android phone?
If yes, after watch activity sync with SA, there is a specific file stored somewhere in your phone and this file need to be imported manually in QS (Dimitrios developped the import specially).
It will create a new acitivity entry in QS (duplicate with the one automatically synced from SA). Only this file contains battery info.More details here
https://forum.suunto.com/post/33052
Or here
https://forum.suunto.com/post/86681 -
@nickk I said that for trail running elevation for all watches is quite good. I wanted to underline my statement with the screenshots
There was just that huge difference in ski mountaineering. But we will see how S9P will be in the cold and bad weather…
-
@_marcus_ said in Real world data:
@nickk I said that for trail running elevation for all watches is quite good. I wanted to underline my statement with the screenshots
There was just that huge difference in ski mountaineering. But we will see how S9P will be in the cold and bad weather…
I do a lot of Ski Mo and do not see this issue comparing either my S9 Baro or Peak against my friends Garmin watches. We are always within reasonable error of each other.
-
S9P arrived yesterday, unfortunately too late for my morning and noon “utility” runs. So this morning it was, used the belt out of habit (no VO2max from this run btw), so cannot comment on OHR but the track (GPS only) was better than what the S9B had ever produced - and I tend to run this same route several times a week. It is an urban environment, so the track is not perfect but the Peak could even deal with my 180° turn (perfect on my way back, better than S9B but with some issues in the way out - but there is a wall on the lhs just before). Curiously, the default run mode with power (have a Stryd) is quite different in terms of fields and screens from the S9B - not an issue as can be customised but just interesting. Overall very happy but still many things to explore
! -
@mff73 I do have one indeed - I’ll have a play tomorrow.
-
5k “walk run “ s9p in gps only
https://www.suunto.com/move/andrfaria640/60cc26410a970d0c596558feGarmin 245 (doesn’t have baro ) + decathlon hr strap
https://connect.garmin.com/modern/activity/6977857873Small 16k team bike ride:
S9p
https://www.suunto.com/move/andrfaria640/60cb342bf1f0e24ada24b377Edge 530 (decathlon hr strap)
https://connect.garmin.com/modern/activity/6973800924 -
@andré-faria Hi André, thanks for sharing you data
… did I get I right, the gps data were not that nice, or? what kind of setting did you use at GPS settings? Many thanks, Martin
-
@andré-faria That looks good, thanks for sharing.
-
@andré-faria said in Real world data:
5k “walk run “ s9p in gps only
https://www.suunto.com/move/andrfaria640/60cc26410a970d0c596558feGarmin 245 (doesn’t have baro ) + decathlon hr strap
https://connect.garmin.com/modern/activity/6977857873Small 16k team bike ride:
S9p
https://www.suunto.com/move/andrfaria640/60cb342bf1f0e24ada24b377Edge 530 (decathlon hr strap)
https://connect.garmin.com/modern/activity/6973800924Same trace (±) on different times with different watches (some altitude may vary if I climbed some stairs on the way or notm but it should vary that much, although not everytime the case)
Ambit 3 peak sapphire
https://www.suunto.com/move/andrfaria640/5fc9dd2f586ad13e50eca662
Garmin FR45
https://connect.garmin.com/modern/activity/6315306290
Fenix 6s sapphire
-
@gosem said in Real world data:
@andré-faria Hi André, thanks for sharing you data
… did I get I right, the gps data were not that nice, or? what kind of setting did you use at GPS settings? Many thanks, Martin What activity is that?
I was seeking those parts and can’t find them.
I found the gps quite good, specially because this zones are tricky for gps.
Setting GPS+QZSS -
First mountain tour today with the S9P and the altitude measurement and the GPS make a very good impression.
-
I did my first ride with the S9P yesterday. Most of the data seems to be good, though the S9B OHR is way too high compared with my Wahoo Bolt + Polar OH1. It reads at least 10-15% high during a threshold effort:
S9B: https://www.suunto.com/nb-no/move/lakerveldt/60cb8f3fe9893c2c684ef50a
Bolt + OH1: https://www.strava.com/activities/5486185880
This was pre FW update to 2.16.26. I continue testing troughout the weekend where I have a swim, long run and long ride planned.
I love the form factor of the S9P compared with my SSU though!
Previously used: Cyclosport HAC4, Polar S710, Ambit 2S, Ambit 3S, SSU, S5P, S9P Ti. Currently using: Race Ti.
-
Did a hike today to check out new trails and do a bit of recovery. Had a route set up and used snap-to-route feature. Here’s a comparison to F6X that was just tracking in the background, connected to HRM-TRI:
Some of the points:
- I think despite snapping, S9P is right here, I quickly went down the wrong path then came back. No way it was in the roundabout fashion of F6X.
- Here we see snap-to-route artifact cutting me straight even though trail was running around a bit. You can see plenty of those straight sections even though I was getting on and off the route to get the picture. Yes, snap was meant to do that, but looks funny on the trail
- Another case of wrong turn. S9P is probably closer to reality.
- Not sure what happened there other than snap-to-route artifact.
- Some UFO maneuvers by snap-to-route. Busted! US Navy, you found me!
All in all, given how close the network of intersecting trails was I think snap-to-route performed fairly well despite plenty of obstruction from rocks and trees. It did cut some of my wondering. Final distance is 2.57 in S9P, 2.60 in F6X.
-
The altitude on the same hike:
Even though profiles look fairly close, you can see S9P tracking me a good deal higher for most of the hike. Interestingly enough, the S9P ascent then is just 259 ft while F6X is 361 ft. When corrected in TP, F6X elevation gain is 233 ft. Given difference in GPS tracks, I’d say S9P wins again, without any corrections.
The heart rate didn’t fare as well though. S9P tracked really well first 10-12 minutes of the hike, then mostly lost it. The average were still fairly close but:
This is very unlike yesterday’s threshold run where S9P was spot on against strap, down to a beat:
Then I shouldn’t hold hiking performance against it. Fenix wouldn’t be perfect without a strap either. And I know COROS is considerably worse.
I continue to be impressed.
-
@nickk keep in mind one thing when hiking. The blood flow is restricted resulting in typically lower HR from any device. A belt reference is needed. Lifting the hand , letting some blood flow fixes that.
Unfortunately no OHR will ever fix that due to the nature of the human body (I hold my breath to be mistaken)
-
@nickk regarding the altitude.
The initial altitude of the s9P was 10 meters pretty much wrong. So at this case we check the vertical error (that is typically 5-20m). If the error is higher than the difference it you apply we keep it uncalibrated but slowly letting it adjust (so a kalman filter). If the conditions provide we retrospectively correct.
In your case as you can see we slowly corrected the altitude instead letting it jump to some not correct value that would have cought the users eye, and also would have provided subsequent wrong ascents and descents.
I hope it makes a little sense
