Running Dynamics question

No, running dynamics - despite the name - do not exclude periods of walking. Some metrics, like cadence, will exclude periods of standing still (i.e. 0s are not included in the cadence average, if I'm not mistaken).

So if you walk during your activity (while the timer is running), this will be reflected with a lower average cadence and stride length (for example).

The run/walk detection feature only affects the total times displayed for running, walking and standing still (as well as the corresponding graph). Furthermore, the moving time feature is completely separate from run/walk detection, which means that moving time may not be exactly equal to run time + walk time (due to a slightly different threshold for what's considered "movement" compared to what's considered "walking").

Some possible solutions:

1) Since you did separate periods of walking and running by taking laps, I guess you could try to determine the "running averages" and "walking averages" yourself, by taking averages of lap averages, weighted by either distance or time. Ofc this isn't a perfect solution, for various reasons.

2) You could also export activity FIT files and view them in fitfileviewer.com, so you could get the raw data for each data point (with a resolution of up to 1 point per second), so you could average the individual points yourself, and avoid some of the problems that might be associated with the previous solution.

3) For a more automated solution, you could use runalyze.com, a free site which syncs with Garmin Connect. It allows you to classify laps as work or rest intervals. If you tag all your run laps as work intervals and all your walk laps as rest intervals, then it will show the averages for the work intervals, including running dynamic metrics. The only problem I've seen with this approach is that runalyze does calculate averages in a slightly different way than Connect (so that even the plain activity average cadence and stride length are slightly different than what Connect displays). I've noticed that Strava also calculates average cadence slightly differently than Connect.