I second that! This is one of the main things why I can’t recommend Intervals to my fellow triathletes. One has to know the paces and compute each interval’s duration
Tx. Target by pace is on the todo list. There are a lot of running related things missing from Intervals.icu. I have a dodgy knee and can’t run at all which is the root cause of this issue.
Not yet. The code would require quite a bit of cleanup first Intervals.icu is also somewhat complicated to run. You need Postgresql, Apache Cassandra, Google cloud storage a/c, Backblaze storage a/c. This bit of work requires client side and server side changes.
I think I’ve got the ‘lap button’ workaround figured out. I just made lap times a little long, and will press the lap button when I finish each mile (roughly 1 mile loops in this example, that I run in about 10-11 minutes so I programmed 12 minutes), and drink/recovery (typically 10-15 seconds so I programmed 20 seconds). Will test it later today! Otherwise, will appreciate any suggestions until then.