My first pace guided workout run today with a 955, and it shows current pace not average pace like the 945 alway has. Not being able to run according to dispalyed average pace makes the whole workout function useless - it's impossible to try to match when it oscillates up and down 15 seconds each way. This is a critical feature. - how can this be set to AVERAGE pace?
can you customize the fields of the run activity, or add a new data screen with the average pace?
Also, the instantaneous pace should not be oscillating 15 seconds each way if you are running at approximately constant pace...that's another issue I think garmin is having.
Displaying the average pace to circumvent this (the fact that the watch is not doing a good job at displaying the instant pace, or you not running at constant-ish pace) is not the solution. But regardless, preferences are preferences and you should be able to customize what you see on the watch during the activity, unless I misunderstood your question
The instantaneous pace is not instantaneous anyway btw and there is some filtering (too much for my own taste but it cannot be customized)
Do you use all+multiband for gps settings?
In my experience page is quite stable that way and at most deviates 5s (which is standard interval it seems anyway).
The target pace data screen in workouts with a target pace IS weird though. Can't really put my finger on it but often gives me warnings while avg and current pace seen fine (when checked on another data screen)
Thanks for your input into this. Yes I can, and am, using a separate data screen to keep me on the desired pace for longer runs - no problems with that as the appropriate field can be explicitly selected. There appears to be no user control of the workout screen other than setting the intensity type and range, then we get what we get.
I did a fair bit of testing today and will do more. I know for sure we currently get the current value, not the average value, for single steps. I suspect if multiple laps are used then lap pace is enabled, which is average pace. Will confirm this with longer laps tomorrow. If this is the answer then I suppose a long run could be broken into parts to trigger the lap = true condition and then we get average pace/power. I'm hoping so anyway. If this is NOT the answer then controlled speed sessions with the 955 aren't really achievable and I need to go back to the 945.
I get warnings all the time, displayed pace up and down 15 seconds at a time from the average pace which frequently means a swing of 30 seconds while running at a constant pace. I've already tried a 20 second window, not enough, currently using a 2 minute window to stop getting these useless alerts.
I haven't tried bumping up the satellite settings - I usually run along the coast with few buildings so I don't see why this should be necessary. Current pace using Garmin has always been only approximate in my experience, never stable enough for controlled sessions.
The main problem is it's not showing average pace - there's no issue with that data if only it could be used on the workout screen.
Thanks for your input into this. Yes I can, and am, using a separate data screen to keep me on the desired pace for longer runs - no problems with that as the appropriate field can be explicitly selected. There appears to be no user control of the workout screen other than setting the intensity type and range, then we get what we get.
I did a fair bit of testing today and will do more. I know for sure we currently get the current value, not the average value, for single steps. I suspect if multiple laps are used then lap pace is enabled, which is average pace. Will confirm this with longer laps tomorrow. If this is the answer then I suppose a long run could be broken into parts to trigger the lap = true condition and then we get average pace/power. I'm hoping so anyway. If this is NOT the answer then controlled speed sessions with the 955 aren't really achievable and I need to go back to the 945.
Testing is completed - this watch does not use average pace for workouts, ever. There was no case where I could get that to happen. Huge swings in the reported pace and actually matching the required pace is a rare accidental event - at one point I was told it was too fast when it was exactly in the middle of the zone. Also, the pace is only shown to the nearest 5 seconds - unacceptable.
For long runs you could use this watch by not using the workout screen at all - for speed work this is impossible. Until this is fixed this watch is not suitable for running. Wish I'd known that I was upgrading to a toy - would have saved my money for a few pairs of shoes.
Ok, this is my last word on this. The final test has been done, this time I got solid average pace after about 400m (normal satellite locking), timing to the second and extremely easy to reach and hold the required pace. No multiband gps or other tweaking required. Perfect.
How did I do this? By using the 945.
Over to you Garmin. Please fix this and then I can start using the 955 for the intended purpose.
honestly if garmin was showing average pace they would lose me forever. I can see that on 400m intervals the average pace could be useful enough. But anything longer it becomes useless. I want to run a 4min/km on 1km intervals, I don't want to at an average of 4. I want to go at 4 and I want to know at anytime at what pace I am running
Your issue is that your instantaneous pace is not stable. Using the average pace is just a workaround. If the instantaneous pace was more stable (assuming you are running at a stable pace), then you would not need to use the average pace
I have used almost all models of garmin watches and the most recent ones are doing a worse job at this. I never used the average pace (and never want to use it because I can look at the averages at the end of a workout for statistics, but while I am running, I want to know my pace now so that I can speed up or slow down. What I was doing in the overall previous 3 minutes it's irrelevant to me)
The older watches had a more stable instantaneous pace information (which you also don't want too stable otherwise you won't see any subtle change in pace). I am already very annoyed that the last few years garmin has been rounding the instantaneous pace to 5 seconds (yes yes...the gps has tolerances and it is not that precise...sure...I am an engineer unfortunately I know all of this...but...the other competitors don't round to 5seconds, and the previous watches from garmin didn't either)
the fact to you are seeing 15 seconds jumps in the instantaneous pace is wrong. The beginning of a lap will be crazy but it should stabilize.
But again, these are just preferences. I can see why the watches are not getting better. Garmin is bombarded by conflicting feedback. I don't think they should "fix this", I think they should give you the option to select what you want. Anything average to me is useless, but for you it is the opposite
My view on workouts is that they facilitate controlled runs - if repeats and intervals aren't at the correct pace intensity then you're either not going to make it through the session or you won't achieve the objective.
The problem with this watch (as it is right now) is that if workout pace intensity is specified, it doesn't actually provide the necessary information on the workout screen precisely and accurately enough to allow you to achieve that intensity with any consistency. Not much use looking at stats afterwards.
I don't accept that because you don't want average pace then no-one should have it, or that we don't need it in the first place. There are important benefits in using average pace during training, and the concept has been around for a long, long time - it's not a workaround to cater for GPS errors.
It's not as if the average pace isn't known by the watch, it knows it the whole time and Garmin make it readily available, just not on the workout screen where we need it. For 5k runs and upwards I can make do with using another data screen, but its a backward step making us do that.
For race training or performance improvement in general, what you're doing at all times during a run is highly relevant. If you prefer to be more flexible you could just go on a run and speed up or slow down as it suited you without needing to be in a workout, or be in a workout but without an intensity if you only need time control.
How would a stable connection prevent seeing subtle changes in pace - seems to me the opposite is true. Even on a long run, small changes in effort don't take long to affect the average.
