Data field: Yet Another Interval field - YAIF

Further Mockup

Here you can see a first Mockup of the interval screen. The green color of the labels indicates that YAIF has detected an interval lap. Note that the vertical lines between the pace fields are missing in that Mockup. Furthermore my intention was to show the pace fields in large readable characters. As you can see the font size is too large to show all three paces that large. I probably will decrease the size of the right pace field to have enough space to show the three paces. This means, just one pace is that large, the other two are a bit smaller. ToD and Calories burned as well as Elapsed Time and Elapsed Distance are hidden during the fast part of the interval lap.

What do you think?

nice

very useful. Thanks for you work

Hi,

I finished yesterday a very early working interval field. Here is the status:

• The layout is far away from being final and has changed a bit to my early mockups posted here.
  
• Regarding paces the datafield will only show the high-intensity pace and the 10 second pace. The high-intensity pace is shown in very, very large letters.
  
• After a high-intensity period (namely in the rest period) the high-intensity pace vanishes and the datafield shows instead performance indicators of the last two high-intensity periods
  
• Also the high-intensity's average heart rate and average cadence vanishes and instead performance indicators of even more high-intensity periods are shown.
  
• In the rest period there is also shown time of date, calories burned, elapsed total time and elapsed total distance.
  
• From coding point of view, the separation in high-intensity and rest period works pretty well. The high-intensity period has another color scheme (Yellow) than the rest period (Blue) to visualize the runner in which period the watch think it is
  
• Apart from this I am pretty sure that there are loads of bugs in there. I will test them out in the next days to get a bug free datafield
  
• If someone wants to test that datafield in this early stage to provide feedback to the layout, to bugs or to feature enhancements, leave me a note - I will provide you a test version.
  
• A test version is not installed via the official garmin app shop but a file is copied directly to your watch to a certain directory. That's it - very simple.
  
• Since the test version is so simple to install, you can not configure the datafield at all to your needs like color schemes etc. The most important value which would need to be set upfront is the separation pace which splits the high-intensity periods and the rest periods. Therefore I would provide versions dedicated to the beta testers with this value coded hard right into the code. If you want to become a beta tester leave me a message what's your typical high-intensity pace is.
  

test

I would like to test the interval data field

Hi nitemolestes,

cool that you are my first beta tester. Don't expect too much regarding the layout. I have to fiddle around some things to put the information right on it's place. Nevertheless, I am confident, that the algorithms behind works and you should hopefully get good results. Furthermore currently I show only just the last high-intensity period instead of 4 during the rest period.

The datafield I created for you is good for the Forerunner 235, it splits rest periods and high-intensity periods at 5:00 min/km. This means, everything faster at a lap is recognized as high-intensity period, everything slower is recognized as a rest period. If this is fine to your intervals, you are good to go: just copy the YAIF.prg file to the Apps directory of your watch (you have to connect your watch to the PC while the PC is already running) and you are good to go. I am excited about your feedback since I haven't tried it on my watch yet, just in the simulator and you can imagine how complicated test is in the simulator. It's really tricky. I will do interval training with that datafield at saturday, so maybe you are the first YAIF user ever :-)

If you have copied the file to your watch, just start your interval training and you are sorted. YAIF will detect a warm up (if you do one) automatically.

OK, last but not least let me say: have fun with that datafield.

PS: next saturday (17.) I will have a 10 km competition. I will not reach my best result since it is currently very hot in germany, but I hope to get below 43 min. Cross your fingers that temperatures will fall below 20 degrees.

Edit: I forgot to say that the total elapsed km shows only 10.23 km. It is a fixed string and doesn't change currently it's value.

Here are two screenshots of a rest period and of a high intesity period. As you can see in the blue rest period that the total elapsed distance is fixed to 10.23 km. The time in the blue field next to the total elapsed distance is the total elapsed time which is only shown in the rest period. The area where the period pace appears in the high-intensity period is during the rest period for the interval information. The first number shows the interval number (here it's the 2nd interval). The second value is the average heart rate and the third value is the average pace during the high-intensity period. BTW: PT means Period Time.

A new version is available now and attached to this post. Changes: I fixed the calculation of the average pace of the high-intensity period at the end of a period. Furthermore I have improved the layout a lot: now the recent 4 high-intensity periods are shown quiet perfect.

Note: the total elapsed km is still fixed to 10.23 km.

You can see 4 intervals, the middle left field is the latest field and shows the most detailed data:
The interval number,
H ... the average heart rate of this high-intensity interval period
C ... average Cadence of this high-intensity interval period
P ... average Pace of this high-intensity interval period
D ... average distance of this high-intensity interval period
T ... Time of this high-intensity interval period

The middle field misses the distance and the cadence values, whereas the upper left und bottom left fields misses also the Time of the high-intesity period due to missing space on the watch. But I think the most important values are shown.

must I remove the previous version before to install?

what the people have in mind when do an interval workout is the number of lap to know how many laps to go, the distance or time (with a vibrating signal when finish) per lap, the pace and the rest periods (better in time values).
So I think the biggest fields to read are pace, distance in lap and cadence or heart rate. The customizable fields would be distance per lap, number of lap, and rest interval (in meters or time if you stop) All that with vibrating or beeps advices to begin and finish a new lap.
It is also interesting to use pace from footpod if it is possible to determine the pace in real time.
they are only my ideas

Just copy the de-zipped file (a .prg file) over the other file and you are sorted. It's very easy. I think we are short before releasing an official version: I will fix the total elapsed time, will do some real life testing tomorrow, will include your feedback, will make some things configurable and we are good to go.

... is the number of lap to know how many laps to go

I can't find out what you have set in the garmin interval settings. Therefore I don't know how many intervals you intend to do.

BTW: some thoughts to the wording:

• Lap: a lap is something I can get from the watch since it is accessible via Garmin's API. A lap is fired during an interval workout, if a new interval begins, if a rest period begins and in between if a certain distance after the last lap event is reached (typically after 1 km if you have not changed the setting on your watch)
  
• interval: an interval is typically split in a high-intensity period and a rest period. Typically a runner does at least two intervals
  
• high-intensity period: the period of an interval with a fast pace
  
• rest period: the period of an interval with a rest pace
  

, the distance or time (with a vibrating signal when finish) per lap

Here, the same is valid as I wrote above. I don't know which distance you want to go. But you can setup a training in the garmin settings which exactly do this.

, the pace and the rest periods (better in time values).

This is delivered by my datafield.

So I think the biggest fields to read are pace, distance in lap and cadence or heart rate.

agree. This is delivered by my datafield.

The customizable fields would be distance per lap, number of lap, and rest interval (in meters or time if you stop) All that with vibrating or beeps advices to begin and finish a new lap.

You can setup this in the garmin settings. Menu -> settings -> Training -> Interval

It is also interesting to use pace from footpod if it is possible to determine the pace in real time.
they are only my ideas

This is unfortunately not possible.