Software update 2.12.30 Staged Release for S3/S5/S9

[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.

[Frixos Demetriades]

@Dimitrios-Kanellopoulos as you can see from my photo, first sprint was kicked on 10’09.7, and I have started sprinting exactly at 10’00, which is almost 10 seconds. Probably my pace was not fast enough
Where can I find threshold pace? didn’t notice such thing

[Frixos Demetriades]

@isazi since my rest period was not constant, I couldn’t use the existing interval program.
I was starting each running set at 0’00, 3’00, 6’00 … etc therefore my rest was depending on time to complete the 400m. ok I could have just estimate it, but I wanted to try sprints

[Dimitrios Kanellopoulos]

@Frixos-Demetriades you can see it at the loop screen. It tries to find it at start.

Also those 10m at start define that. If you want the warmup to end (defining the pace) you press that lap button.

During the warmup, you see the trigger level being updated. This trigger level is set to 25% faster running pace or 25% higher cycling power.

[Frixos Demetriades]

@Dimitrios-Kanellopoulos Ok now I got it, thanks!

[Dimitrios Kanellopoulos]

@Frixos-Demetriades i ll double check my claim of 3-5s when I can to make sure I am not thinking 9s = 3s (mind tricks). But at least this is what I thought.

[jw cou]

@Frixos-Demetriades that’s how it looked for me during the last session. Taking a closer look at the numbers (increase of the pace vs beginning of the “automatic” manual lap), there’s about 5 sec gap (start and stop), which reduces a bit the avg speed of a sprint. Still useful in my opinion, especially to compare sessions all done with that feature.

[Frixos Demetriades]

@jw-cou My main problem was that some of my sprints have stopped while I was running as you can see from my photos (I think 3/10), even though distance was measured from stryd. That was not expected.

[Dimitrios Kanellopoulos]

@Frixos-Demetriades that should not be like so…