• Replies 150 replies
  • Subscribers 24 subscribers
  • Views 32530 views
  • Users 0 members are here
Options
Related

Data Field: Peter's (Hi Vis) Pacer

peterdedecker
over 7 years ago
Description
Peter's (Hi Vis) Pacer helps you to ride/run the perfect race.
This is a spinoff project from Peter's (Race) Pacer, while it has many similarities it took me a while to create as it's a completely seperate code base.
It's different in the following ways:
  • high visibility less data is shown on the screen, which means that it is easier to read - eg for people with bad eye sight.
  • it can be used in non-single field mode, this means you can put it on the same page with other datafields of your choice!
  • It's also optimized to run on Edge devices, this means you can just as well use this field to pace your bike races just as your running races....
Adjusting the race distance
In a race when you are next to the race marker press the LAP button, the distance will now be corrected to the nearest lap position - eg 5.08 will correct to 5, 8.8 will correct to 9. After pressing the lap button the distance will be adjusted and all averages will be recalculated against this new distance figure.
When you miss a lap marker do not worry: do not press LAP and go for the next lap marker.
When you press the LAP marker by mistake you can undo the (last) correction by pressing the LAP button again - within a 30 second window

Donations
The data field is fully functional as is, yet donations are encouraged on the watch by an encouragement text.

Download
Download link: https://apps.garmin.com/en-US/apps/5...4-e3afdd10eddf
  • over 7 years ago
    Ah, of course.

    I didn't notice the difference between the 'Target Type' field between the two apps, as the Pacer has a single 'Target Pace' selection where 'Hi-Vis' provides the Pace/Speed/Finish choice. I mistakenly thought the format of the value used in the 'Target Pace' field of 'Hi-Vis' was used to differentiate the type: one colon == Pace, decimal == Speed, two colons == Finish Time. I've updated to 'Target Pace' for Hi-Vis; it gets its shake-out use tomorrow AM.

    Thanks for the timely support.

    Ken

    PS: Both worked flawlessly, enabling me to PR!
  • over 7 years ago
    Peter,

    Fantastic app. I use both your regular race pacer and now the hi-vis pacer. I wanted to know if I am inputting the right settings for the condition that I run at. For the military, I have to run on a 400 meter track for 2 miles. The time I want to finish it is 14:00. I want the big field to be the ETA on when I am expected to finish the 2 miles. Would the settings below be the right ones to have?

    Lap size in meters = 400
    Target distance = Custom
    Custom distance = 3200
    Target type = Target finish time
    Target pace = 0:14:00

    Also, how accurate is the ETA time (using the lap button on the watch to provide manual lap counts)?
  • over 7 years ago
    PS: Both worked flawlessly, enabling me to PR!

    Way to go Ken! Congrats on your new PR! :)

    Peter,

    Fantastic app. I use both your regular race pacer and now the hi-vis pacer.

    Thanks Johnny :)

    I wanted to know if I am inputting the right settings for the condition that I run at. For the military, I have to run on a 400 meter track for 2 miles.

    Interesting to see this adaptation of the Cooper Test by the military! With an expected speed of 13.7k/h (8.5mile/h) you already have to be a pretty decent runner as well to make the limit.
    Do you have to do this test each year?

    The time I want to finish it is 14:00. I want the big field to be the ETA on when I am expected to finish the 2 miles. Would the settings below be the right ones to have?

    Lap size in meters = 400
    Target distance = Custom
    Custom distance = 3200
    Target type = Target finish time
    Target pace = 0:14:00

    It depends.
    Are you allowed to stop after 8 laps of 400 meter? Then the settings are ok. (you don't need the 0 in front of the 0:14:00, 14:00 will work as well)
    If you have to run 2 miles exactly, then you will have to set the custom distance to 3219 as 1 mile is 1609.34 meter.

    I would advice to turn the auto-lap setting in your watch off for this test.

    Also, how accurate is the ETA time (using the lap button on the watch to provide manual lap counts)?

    The ETA is based on your average speed. If you can keep up with the average speed the ETA shown by the app is going to be spot on. :)

    Good luck with your test Johnny!
    (If you may disclose the result, you can let me know how it went.)
  • over 7 years ago
    Hi Peter,

    great app! Thank you. Made my PR in Dresden.
    Wasn't that fast in Frankfurt - so my question/request
    I can read very clearly the "ahead" times (on green) but this "almost white" on "quite red" on my Fenix 3 is really hard to get. So I'd like to ask - do you think it will make sense to invert the layout? Red digits on white ground? Can't test ist - but I think it would be easier.
    The second (and last) item on my F3 is - how to handle this km-adustment? Could not figure it out (w/o my glasses).

    Anyway. Switched to F5 today :D (see PR @ Dresden;) Maybe everything is better there....but the red on white thing ...

    thank you, best-readable letters since lucarun
  • over 7 years ago
    A problem is that I have zero wiggle room to add functionality on ciq1 devices such as the fenix3 (in the current 2.3 sdk I'm at 15.7k out of 16k and in the new 2.4 beta sdk I'm at 15.9k out of 16k), so while I like the idea of providing alternative color themes it won't make it onto the fenix3 (I have no memory for it), it could be something that I add to connect iq 2 devices though.

    I'm not so sure about the red on white, I think this might look like no coloring (as red on white is not so different from the default black on white), maybe something like white on orange could be more readable?

    how to handle this km-adustment

    if you're next to the 2k marker and your watch says something drastically different like 2.1k then just press the lap button, it will correct the (displayed) distance of 2.1k to 2k
  • over 7 years ago

    Hi, I wanted to ask if during a marathon to update the kms to the visuals it was necessary to remove the autolup from the fr235 settings or not. Thanks for the reply
  • over 7 years ago
    you do not have to disable autolap, just make sure that your lapsize is equal to that of your autolapsize (typically 1000 if you use metric, 1609 when you use miles)
  • over 7 years ago
    Thanks for that new version for eyes that are getting older ;-)
    I suppose both version can be run at the same time but FIT writing would have to be deactivated on one of them ?
  • over 7 years ago
    you can have both data fields simultaneously active, including fit recording if you wish and use the combo in interesting ways, I've elaborated on this here
  • over 7 years ago
    Ah yes, thanks for refreshing my memory !