Virtual Racer (legacy)

NO MORE MAINTAINED: use https://apps.garmin.com/en-US/apps/833564b1-d1e9-4688-85ab-1b733ef4f704 instead. Virtual Pacer/Racer data field. The field display itself the following information: - the current pace - through a progress bar, the remaining distance - if behind and if the speed is higher as the virtual partner an estimated time to catch him is computed. - if ahead and the speed is lower as the partner, an estimated time to be catch by the partner is computed. The pacer itself has following configuration parameters: - the distance and the race average pace (mandatory) - a warmup time/distance: during this time the pacer is deactivated. After this time, the pace is adapted to reach the requested average pace at the end of the race. - a optional startup or finish pace: this permits to request a specific pace at the arrival or after the warmup. But this does not change the average pace: * If the finish space is unset, the pace is calculated so that the finished space is reached as slow as possible. In other words, it minimize the necessary speed to reach the given overall race pace. * If the start pace is unset, the average pace is used. Color convention: - Gray: warmup phase - Black: end of the race - Green: Ahead - Blue: same time (with a configurable tolerance) - Orange: behind but the actual speed permits to win the race - Red: behind # Example: warm up time set to 2:00, distance to 5k, pace set to 5:00 and finish pace set to 4:50. 1) During the first 2 minutes, the virtual partner stays at the same speed as you. 2) At 2 minutes , the pace was 6:00. The virtual partner then continue with this pace and in increase the speed progressively. 3) when it reach 5k, its instant pace is now 4:50 and the overall pace for the 5k was 5:00 # Example: constant pace to 05:00 for a 5k: 1) set the warm up distance to 0, 2) the distance to 5.0 # Example: 45 min run with a target pace to 5:00 with a finish at 4:30 and a slow warm up at 6:00 1) set the warmup to 6:00 2) set the race time/duration to 45:00 3) set the target pace to 5:00 4) set the start pace to 6:00 5) set the final pace at 4:30 # Example: 5k with a target pace to 5:00 and the first 10 minutes run without a pace. After 10 minutes, an optimal pace will be computed starting from the current speed to do the 5k with a pace of 5:00. 1) set the warmup time to 10:00 2) set the distance to 5.0 3) set the target pace to 5:00 4) Set "Begin Race after Warmup" to false # Example: 25k bike race with a target speed of 30.5 km/h 1) set the warmup time to 0 2) set the distance to 25.0 3) set the target pace to 30.5 4) clear the final and start pace

0.1.0: First version 0.2:0: Notifications 0.4.0: Handling lap button 0.5.0: French translation 0.6.0: Target distance is now in miles/km 0.7.0: tolerance is now in meter. 0.8.0: Possibility to choose between the pace and the speed on the display. Possibility to enter a speed in the configuration instead of a pace. 0.9.0: Fit recording 1.0.0: Specific configuration for running and biking 1.0.2: Estimated time to reach the virtual partner 1.0.4: Issues with printing the current pace fixed after the race completion. 1.1.0: Better layout to display the information on Fenix and Vivoactive HR. Bug fixed with the estimated time and the winner of the race. 1.1.5: Bigger fonts 1.2.0: Small changes in the layout 1.2.1: Possibility to start the race after a warmup. Better summary. 1.3.0: Warm up distance 1.4.0: different vibrations and tones for all events (on time, behind, ahead, ... notifications) 1.5.0: recording the speed during the session 1.6.0: Possibility to specify a race time instead of a distance. Issue with imperial metrics fixed. 1.7.0: after a warm up/free running, the partner speed is the average speed if not defined in the settings and no more the instant speed. 1.8.0: displaying in the first seconds the configuration. Fixes in the prediction that the speed is high enough to win the race.