Software update 2.12.30 Staged Release for S3/S5/S9

[Dimitrios Kanellopoulos]

@Łukasz-Szmigiel inclination

0 is flat up to 100 which is 90degrees if not mistaken

However the way to interpret it is this for me.

Grade: If you climb 100m in 1km it’s 10% grade

VS: If you are climbing with a vertical speed of 10meters per minute you will gain 100 meters up in 10 minutes. In a 10% grade you will also have covered one km.

[Łukasz Szmigiel]

@isazi that’s what I’ve also found but wasn’t sure if it’s the same in Suunto.

@Dimitrios-Kanellopoulos, thanks, this makes sense.

Also, how often is this data smoothed in case of S5 which doesn’t use baro for elevation?

[Egika]

@Dimitrios-Kanellopoulos isazi is corect .
100% equals 45°
(in your example 1km vertical over 1km horizontal)

[Dimitrios Kanellopoulos]

@Egika oups

[kabzior]

@Dimitrios-Kanellopoulos said in Software update 2.12.30 Staged Release for S3/S5/S9:

VS: If you are climbing with a vertical speed of 10meters per minute you will gain 100 meters up in 10 minutes. In a 10% grade you will also have covered one km.

BTW - either there is a bug in the application (it should be m/h, not m/min) or it’s time to go to the Himalayas and break some world records;)

[Dimitrios Kanellopoulos]

@kabzior got a link for me ?

[isazi]

Yesterday I finally tried the loop S+ function on the track. Pretty good results, the laps triggered in the space for 1-2 meters of where I started my track session. Will use it again

[Łukasz Szmigiel]

@isazi yeah, can confirm the precision is amazing. Even with tree cover, it works surprisingly accurate.

[kabzior]

@Dimitrios-Kanellopoulos said in Software update 2.12.30 Staged Release for S3/S5/S9:

got a link for me ?

There you go:
https://quantified-self.io/user/jiPftbRzlpbGL3ZQJ0UJl1qEO653/event/fec63a9466895210db3308d7f0f9747c6a596f4841259514a6bee710b3f68336

Of course, the error is in SA and not in the activity itself, the wrong units are given in app.

PS - In one of the threads earlier you asked me to let me know if there was still a problem with the navigation after updating the software. See the attached section of the route - it’s straight and to the left, but with going a bit down to the hut and back in the same way to continue. After leaving the hut, the navigation for about 10 minutes guided me back to the hut, even though I was walking in the opposite direction. As I said - there is a problem if the route is on the same road in opposite directions.

[isazi]

@Łukasz-Szmigiel at first I was using the speed based sprints believing that GPS based loop would be less accurate, but I was wrong
Now I will keep using the loop in the track, or for loops in the park, and using the sprints for something like fun fartlek sessions.

[Dimitrios Kanellopoulos]

@kabzior I meant a suunto app link (since I now work as a dev I could create and fix this my self )

[kabzior]

@Dimitrios-Kanellopoulos said in Software update 2.12.30 Staged Release for S3/S5/S9:

I meant a suunto app link

oh, i did not know that one can do that…

here it is:
https://app.suunto.com/move/kabzior/5f788bd7dfbf8b068b1105c9/

[Dimitrios Kanellopoulos]

@kabzior on android its correct.

[kabzior]

@Dimitrios-Kanellopoulos so I guess this is just IOS issue, no big deal, it is not data problem, just change of the label

[Dimitrios Kanellopoulos]

@kabzior I created a bug

[Frixos Demetriades]

Feedback on Sprint - Running pace.

I am not sure whether it is the right place to post it or open a new topic. Please move it accordingly if needed.

I have tested it yesterday, although results were quite disappointing.

My running session was as follow:
6 min warm up
then,
4 min rest
then,
Every 3 minutes Run 400m for 10 rounds (total 30min)

I have started Sprints exactly at min 10, so I was supposed to have 10 sprint counts in total, however that was not the case. Sometimes sprints were interrupted while I was running so this resulted in more sprint counts. I was also expecting the sprint to kick in faster (it took around 8-10sec) and 8-10 sec to stop.
Please note that the distance was measured from stryd (paired as foot pod).

I have attached some photos, which shows clearly what I have mentioned. Data highlighted in yellow is the warm up and in light blue are the 400m running.

Also as you can see from my photos, data in the table is so confusing. A suggestion would be to have a similar format with intervals’ table which shows work and recovery. Probably add warm up description as well.

Don’t know if I was too optimistic or I was missing something. Maybe sprint feature is for shorter faster intervals?

Excuse my English, hopefully my points are well understood. Any advice appreciated

[isazi]

@Frixos-Demetriades I have pretty good results with sprint, I can share some screenshots later if you want.

[Frixos Demetriades]

@isazi would be great yes. I have tried it only once, and I am sceptical to use it again. Maybe you can convince me

[isazi]

@Frixos-Demetriades to be honest, I would not use it in your case, you have a perfectly structured interval and you could just play with the on watch intervals, but I’ll show you my results in another topic in like 15-20 minutes.

[Dimitrios Kanellopoulos]

Sprint is not intented for this case. It’s more to the Fartlek philoshopy (random sprints).

However depending on the pace increase it should be 3-5s not 8s for the sprint to start end at least from my experience. It shows the threshold pace that is needed to be used.

I personally use this for FartLek mainly.

Since Sprints creates normal laps, there is no concept of recovery. Its just a sprint lap.