Run Snapshot
Raman completed a 43K half marathon long run at an average pace of 6:31-7:43 min:sec/km, with the fastest kilometer at 4:40 min:sec/km and the slowest at 13:32 min:sec/km. The run took place with no available weather data, and Raman’s heart rate and cadence varied throughout the run. The average cadence was around 160 spm, indicating a relatively efficient form.
Pace & Effort Breakdown
The gap between the average and maximum pace reveals a pacing strategy that involves varying effort levels throughout the run. Although heart rate data is not available, the pace data suggests that Raman was working at a moderate to high intensity. The cadence data indicates that Raman maintained a relatively efficient form, with an average cadence of 160 spm.
The temperature and dew point data are not available, so it’s difficult to assess the impact of weather conditions on Raman’s performance. However, the pace data suggests that Raman was able to maintain a consistent effort level throughout the run, with some variation in pace due to terrain and fatigue.
Route Narrative
The run can be broken down into several segments, with varying pace and elevation changes. The fastest kilometer was at 4:40 min:sec/km, which occurred on a relatively flat segment. The slowest kilometer was at 13:32 min:sec/km, which occurred on a segment with a significant elevation gain.
Raman’s pace responded to elevation changes, with slower pace on uphill segments and faster pace on downhill segments. The cadence data also varied throughout the run, with higher cadence on flat segments and lower cadence on uphill segments.
Run Analysis
Workload Intelligence
Unfortunately, the ACWR value is not available, so it's difficult to assess the training load and risk of injury. However, the pace and distance data suggest that Raman was working at a moderate to high intensity, with a significant accumulation of fatigue towards the end of the run.
The acute load and chronic load are not available, but the pace and distance data suggest that Raman has been increasing his training volume and intensity over the past few weeks.
Physiological Impact
Based on the pace and duration of the run, it's likely that Raman was targeting his aerobic and lactate threshold energy systems. The run would have driven adaptations such as increased mitochondrial density, capillarization, and lactate clearance.
Recovery & Next Session
Given the intensity and duration of the run, Raman should allow for a recovery period of at least 48 hours before his next hard workout. The next workout should be a easy recovery run of around 10K at a pace of 6:00-7:00 min:sec/km.
Training Trajectory
Raman's training trajectory over the past 28 days suggests that he has been increasing his training volume and intensity. To continue progressing safely, Raman should aim to maintain a consistent training load and avoid excessive increases in volume or intensity.
A concrete coaching directive for Raman would be to aim for a weekly training volume of 60-80K and a pace target of 5:30-6:30 min:sec/km for his next hard workout.
Takeaway
Raman should focus on consistent training and recovery to achieve his goals.
View the original activity on Strava
Gear Used: Asics Novoblast 5 (Shoes)
Transparency: The links above are affiliate links — if you purchase through them, I earn a small commission at no extra cost to you. It helps support my training and this data analysis hobby project.