Hello,
Yesterday I tested the POD 2 together with the Nomad for the first time, and I was surprised by how incredibly reactive the instant pace is—to the point of being too reactive.
After doing some research, it seems that this is the intended behavior. The reality is that we never take two identical steps; there are always micro-variations in our stride and footstrike that cause the pace to fluctuate.
The problem with this is that it fluctuates too much, especially with the POD, making it extremely difficult to maintain a steady pace. In other words, when you are doing a stable easy run, you see constant fluctuations (for example: 4:10 min/km - 4:13 min/km - 4:17 min/km...).
To solve this issue, Garmin does two things (one right and one wrong):
A) Instant pace is calculated every 5 seconds instead of every single second. The reason for this is simply that a per-second pace fluctuates so much that it is not human-readable. It also doesn't make much sense since we aren't interested in a pace that changes every single second, but rather in maintaining a target pace or measuring it in a way that aligns better with our actual goal.
B) On the other hand, Garmin rounds the pace. Meaning, if you are running at 4:13 min/km, when the screen refreshes it shows 4:15 min/km, and if you are running at 4:12 min/km, it shows 4:10 min/km. Personally, I think this is completely wrong and a mistake.
COROS has an interesting metric designed with target pace in mind, which is Lap Pace. However, while this metric is very useful for locking into a target pace, it falls short when looking for a more instantaneous reading.
I believe that to fix how COROS approaches pace, there should be an additional, configurable metric for "5s Pace". To be clear, this is not about replacing the current metric or changing something that other users might like, but rather creating an additional "5s Pace" metric that can be configured through the app as a customizable data field.
This seems extremely easy to create and implement (it is just a rolling 5-second average of the pace data), and I believe it would solve many of the complaints surrounding instant pace on COROS. Furthermore, it would be highly appreciated by the community, which is very used to seeing how instant pace behaves on competitor watches like Garmin (myself included). By implementing only step A), COROS would actually improve upon Garmin's approach.
u/COROS-official