How to add both distance and estimated time on workouts?

Hi,

I’m trying to see estimated load for next week. What I need:

  • Being able add total planned distance for the week
  • Being able to see total load for the week

What I tried:

Using this format I only get the time, but I also want to see distance. I know 32 km is going to take me around 4 hours (Average HR: 145). So I want a load estimate for that distance, time and average heart rate.

But If I add the distance, time changes:

I guess I’m not using the proper format. Any ideas?

Thanks

How do you expect this to work?
You are giving three parameters were one automatically influences one of the other. this could only work if you know quite precisely what the outcome will be.
A higher HR will automatically result in a shorter time for the given distance or a higher distance for the given time…
But if you do know that these 3 metrics should be about correct, you may have a typo:

In the screenshots, you entered 154 as as HR. Maybe that’s what putting the estimation off?

What is your 89% LTP? I mean, if you have configured your pace zones similar to your real HR zones, you should get a very close estimation in distance, time and avg heart rate.

This is how I set up my LTP:

I do understand what you mean. The problem is that I mostly do trail runs. So when I enter 32 km at LTP in the workout, it does not take into account elevation gain, or how hard some parts of the run are. I guess.

I know that run is going to take me around 4 hours, at an average of HR 145 (estimation from previous efforts). That’s what I want Intervals to use for load calculation (HR and time). That one is ok on the first screenshot. But I’d love to also see accumulated distance for the week calculations.

I just need to add km as you see here (red squares):

I guess it’s not possible right now, since it won’t make sense for most of Intervals users.

Thanks. I removed the “154” commented line from the workout. Same result.

According to my HR and pace settings, running for 32 km at that average HR gives me a 2 hours 47 minutes mark. I know that would work for a road run, but not for that specific trail run (elevation gain: +1600 meters)

So I don’t see the problem :slightly_smiling_face:. If you know the time and load from previous training, why just don’t input them in your workout?

The calculated values are editable, and the week totals will take account of them.

Thanks. I see your point, but… I want Intervals to tell me the estimate load. I know the load from a previous activity, but at a different average HR.

I tried this:

  1. I set up a 4 hours workout at an average of 145 bpm.
  2. I got a value of 261 for load

Then I edited the planned workout this way:

Red: added distance
Blue: manually added load (based of previous calculation)

This is the closest I can get to see actual planned distance and load for the week, which is my goal:

Intervals_icu

However, estimated time is wrong. But I can live with that :slight_smile: Also, once I first save the edited workout, manual added load gets saved correctly. But if I open the workout and save it again, 261 gois away and the load is recalculated.

Thanks!

You can edit duration as well.

Can’t get it to work:

Any ideas? Thanks

I can get it in a workout of mine. This is my initial values:

Changing load and duration manually:

Result as expected:

1 Like

Have you tried adding the planned duration, load and distance in the summary info. Click the summary information to open the time in zone details.

Then add your weekly target for duration, load and distance. When you create your planned workouts, you can play around with the known factors, i.e. duration and distance to meet your goal.

The main problem is that distance and duration are basically the same field for us to input.

And the calculation down below does indeed not include elevation.

Thanks! I swear that’s how I was doing it. I tried again, from scratch (copying your details), and now it works:

However, if I clic the “edit” button, values change back to original calculations. Also, time in zone (Z2 keeps original time value). Anyway, it’s a good workaround. Gracias!

1 Like

Thanks. But I need values for single activities, not weekly aggregated.