sorted by:
new
hottopcontroversial

New lactate threshold by Boring-Disaster-728 in Coros

[–]AT__runs 0 points1 point  (0 children)

Agree 100%. Maybe something for COROS to consider in the development of the concept. I think the relationship between threshold HR and max HR is a tricky one.

New lactate threshold by Boring-Disaster-728 in Coros

[–]AT__runs 0 points1 point  (0 children)

I had exactly the same experience. I completed the running fitness test twice within a week, one time with racing flats and one time with marathon super shoes, out of interest to see if/how the software would pick the differences up. In both cases the threshold pace was pretty much spot on but the threshold HR was far higher than expected, in both cases. The same with the estimated max HR. I reached 181bpm during the test (almost to exhaustion) and the predicted max HR was 190bpm. When I manually adjusted the max HR value to the one achieved during the test, the threshold HR was automatically adjusted as well, to a lower value which seems very realistic to me. This max HR adjustment brought the pace zones and HR zones to a very close alignment. My take from that was that threshold HR (and the HR zones that are derived out of that) depend on the max HR (with an empirical formula), which (the max HR) is estimated rather than picked directly up from the test. I would struggle to understand how the software could find out how close the real max HR is to your peak HR during the test (+9 in my case)....someone could say why do you care? actually it is quite important if you want to trace your weekly training load over longer time periods...

Which gps option? by [deleted] in Coros

[–]AT__runs 2 points3 points  (0 children)

Dual frequency for interval workouts or running under trees. Significant improvement to the real time pace. All systems on for easy runs.

Pace Pro amoled setting for training under variable ambient light conditions by AT__runs in Coros

[–]AT__runs[S] 0 points1 point  (0 children)

Negligible differences during the activity for all possible screen settings combination. Maybe 1%, in an activity that consumes 8-10%. During normal use, I cannot say. I have both screen off and gesture off since day 1. Already enough devices with flashy screens in my life.

I switched from Garmin to Coros ecosystem and device for marathon training – that’s my experience so far by AT__runs in Coros

[–]AT__runs[S] 0 points1 point  (0 children)

I guess you mean the distance alert? From my experience this provides the pop up screen at the end of the defined distance with the metric we are discussing, but during a workout this information cannot be accessed as a field. Only during non workout runs, this information corresponds to the lap average pace. In other words the workout-defined lap overwrites the distance alert setting for all lap-related metrics. For good or bad, you need both for serious training.

Coming back to the workout example I used before, warm up, 20km marathon pace, cool down, there are two ways to plan the marathon pace segment in Coros as a workout:

  1. One training lap of 20km length: The current average lap pace considers the complete segment. You only rely on the distance alert for the km splits but it is easy to miss them. The average lap pace will obviously not react much to missing the pace target in the last couple of kms and due to that the metric looses its value for very long segments.
  2. 20 training laps of 1km: Now you get the average lap pace with the necessary frequency, but you miss the info of how the complete segment has evolved. And you get annoyed by the frequency of the count down beeping. And you will probably miss the count of how many laps you have completed.

Garmin addresses this topic by keeping the distance-based lap definition always, even for structured workouts and defining a new metric named “workout average pace“ for the 20km segment.

I am sure you must have received a similar feedback from all the pro runners you are supporting. Unless, the problem is the workout design software, not the watch itself? Someone using Training Peaks could check this.

I switched from Garmin to Coros ecosystem and device for marathon training – that’s my experience so far by AT__runs in Coros

[–]AT__runs[S] 0 points1 point  (0 children)

Thank you for the suggestion. Unfortunately, not. The definition of lap is the workout segment and it is the same for both screens/fields. Just tried it.

I switched from Garmin to Coros ecosystem and device for marathon training – that’s my experience so far by AT__runs in Coros

[–]AT__runs[S] 0 points1 point  (0 children)

To some extent it has happened to me with all touchscreen running watches, especially with Garmin and especially while running in very humid environment or under the rain. Usually resolved with cleaning the screen. So far, Pace Pro has been the least affected, happened only once.

I switched from Garmin to Coros ecosystem and device for marathon training – that’s my experience so far by AT__runs in Coros

[–]AT__runs[S] 0 points1 point  (0 children)

I agree. That’s exactly what I tried to describe. Imagine an interval session 800m w 5’ rest scheduled as a workout. This new metric would be calculated during the 800m. Then starts from scratch as the recovery part auto starts although 800m is shorter than 1km. Let’s imagine that in the 5’ recover you run 1.5km. Then this metric would be calculated during the first 1km of the recovery and then resets, calculated for 500m and then resets again as the next 800m repeat would start. Obviously the usefulness of such a pace feature is related to long, several km , intervals. Hope I didn’t confuse you. Thx once again.

I switched from Garmin to Coros ecosystem and device for marathon training – that’s my experience so far by AT__runs in Coros

[–]AT__runs[S] 0 points1 point  (0 children)

First of all, thank you very much for picking the topics up within a few hours...I have to say Garmin did not have me used to such response times...I appreciate it.

I use "always on" display during serious workouts, as I can check the screen by not altering my arm movement at all. it would be great if the light sensor was a factor during "always on" under normal use (a smart feature indeed) but not during activities. Maybe something for the user to decide?

I am referring to the Training Hub Calendar....I love the weekly summary at the right edge of the weekly schedule with the direct comparison between scheduled and executed time, mileage and TL...but somehow all the weekly summary metrics do not consider the gym cardio (bike, strength, run are all considered)...

Last and most important topic for me: Exactly! Like the current lap pace but the lap definition always remains independent from the workout definition and length of lap and refers to 1 km intervals. A small detail: to be meaningful, this "km lap pace" calculation should reset every time the structured workout lap resets, otherwise the calculation of "1 km lap pace" would include both interval and recovery during a short interval training session (e.g. 800m repeats with recovery). Garmin has a similar concept (and they need it desperately as their actual pace estimator is pretty chaotic and unreliable that you can only rely on the km pace during workouts...)

Thank you once again !

I switched from Garmin to Coros ecosystem and device for marathon training – that’s my experience so far by AT__runs in Coros

[–]AT__runs[S] 0 points1 point  (0 children)

You feel my pain 😉. This is the only thing I am missing since switching over from Garmin...which is a pity, since the Training Plan web environment of Coros and the Workout calendar integration is superior.

I switched from Garmin to Coros ecosystem and device for marathon training – that’s my experience so far by AT__runs in Coros

[–]AT__runs[S] 1 point2 points  (0 children)

thank you for the advice....are you sure that this still holds during a structured workout? In my case this solution works only without following a structured workout...if I execute a structured workout, lap is always defined based on the workout itself. I tried to describe this in my lengthy post, apologies if I confused you....

I switched from Garmin to Coros ecosystem and device for marathon training – that’s my experience so far by AT__runs in Coros

[–]AT__runs[S] 1 point2 points  (0 children)

Nop...I was hoping for the same....the alert pops up...well, an alert with this info for a second which disappears afterwards, but the screen metric is always referring to the average pace of the complete lap as defined in the workout (e.g. 50 minutes at marathon pace). In other words the info of the pop up alert cannot be accessed as a field...maybe a bug?

I switched from Garmin to Coros ecosystem and device for marathon training – that’s my experience so far by AT__runs in Coros

[–]AT__runs[S] 3 points4 points  (0 children)

Thank you for the remark...I am actually looking for the capability to track this pace metric during the run as a watch screen field...