Average moving pace on interval runs

This forum is actually for Connect IQ (third-party) app developers, not the Connect app or website.

I will assume you're asking about the app, although the general idea also applies to the site:

1) Open your activity in the app

2) View your laps

3) Make sure all your intervals are categorized properly (if they aren't, edit your intervals with 3 dots > Edit Activity > Show More Data > Intervals)

4) Turn your phone to landscape orientation so that you can see all the columns

5) Select step type > Run. The Total row at the bottom of the page will now show totals (or averages where applicable) for only the selected step type

6) Scroll right to the Average Moving Pace Average Pace column, and down to the bottom of the page, where you'll find the average moving pace just for the Run intervals

EDIT: On second thought, if your intervals are categorized properly and you've filtered them to remove the Rest periods, I think it makes more sense to look at Average Pace rather than Average Moving Pace, which gives you the data you're (implicitly) looking for: the pace for your intervals,.

The reason for this is:

- Garmin's moving pace algorithm may make it seem like you ran your intervals faster than you actually did, especially if the distance for each interval is very short

- If you're already excluding rest intervals from the calculation, then average pace already gives you what you want, by definition

EDIT2: Sorry, I assumed that this question is about viewing data after the fact. If you need to see your average interval/moving pace during a run, it isn't possible unless you use a Connect IQ app or you pause your watch during rest intervals.

What I do in my custom data fields, is maintain moving and elapsed time and speed. The native Garmin metrics can't do that. If you have Auto Pause turned ON, then you only get MOVING average speed. If it is turned off then you only get ELAPSED average speed. So I track both inside my data fields - both are important.

In your case, your REST intervals could be stopped or like many, those are much slower "recovery" run sections between the hard/fast intervals. So you could set a pace threshold that detects which state you are in (hard or easy, fast or slow) and accumulates your time in each, the number of each, and avg speed and HR in each. There are lots of cool things you can do to give you exactly what you'd like to see if you roll your own. Another interesting metric might be your HR recovery - the BPM drop from the end of your hard interval, so begin your next interval when your HR has dropped X bpm (ex: -20bpm) or when it has reached Y bpm (ex: reached 132bpm).