Race Finish Time Predictor

This datafield provides an estimated time to finish (ETF) and an estimated time remaining (ETF) to run for a given distance and trailing pace. It does this by using a user configurable 'rolling look back' window of the last XX minutes of data and then from that data calculates the finish and remaining times. It can additionally be configured to provide warnings in the form of changing the colors of the background and or the colors of the text and additionally provide a estimate of how many hours/minutes you current are over/ once you exceed your thresholds. Disclaimer: This datafield was written to fill a need for myself and my running partner for our ultra marathons. It's designed to help keep us on pace and target for our desired goals and warn us about being too far ahead of or behind our overall target finish time for a given race. I've made reasonable effort to make it work for a variety of CIQ3.x watch displays but there's no guarantee it'll work for a given supported watch in an optimal fashion. All the supported watches run correctly in the simulator using various exported race files (.fit files), but I have only tested it real world on Fenix 5X and 6X watches. Note that because this is aimed at running long distances and stupid long distances it only displays ETF/ETR times in hours and minutes. Seconds aren't a major factor for pacing for ultra marathons (typically). Features: Large fonts to make it easier to read after 20+ hours of running. Warning can be enabled that can change the background colors to make it easy to see at a glance if you're too hot or cold. If the background is white (default configuration) then you're on pace, red and you're running too fast, blue - too slow. Look back window - Can be configured between 5 and 60 minutes. Use a short look back window for a short race or a race that you have a steady pace on and a long one for a long race or if you're a run walker to get the best results. Recording interval - The recording interval determines how often during the look back window a data point on elapsed time and distance is recorded. For a short fast race choose a shorter interval so you get faster updates. For a longer race a longer one because it's not as critical. IMPORTANT NOTE: If you set the recording window to 30+ minutes the recording interval will be reset internally to no oftener than 10 seconds. This is to keep the memory usage within reason. Arrays are expensive. Race Distances: You can either choose one of the preset race distances, a number of common and or famous ones are included. If you want to run a distance other than those then select the Use custom race distance, if it's in Kilometers or not and then put the distance in the appropriate field. Decimals are allowed for custom distances so if you want to race a 89.32 kilometer race in 10 hours and 12 minutes go right ahead. If you want warnings during the race (color changes) then check that box. If you do check the Warnings box then you have to provide an accurate finish time as well as a desired threshold to get warnings on. If you know your pace is going to vary by a wide degree, then choose a higher threshold in % or minutes to avoid the stress of looking down and seeing too fast, too slow colors. Input your target finish time in Hours and Minutes, this is critical for the warnings to make any sense and be valid. If you're pacing for 50 miles and accidently leave the default 24 hours set up then you're probably always going to way ahead of pace. Unless you do take 24 hours to run 50 miles in which case we don't judge, whatever gets you across the finish line. Out of the box the datafield, if warnings are selected, will use a white background with black text for on pace, red background with white text for too fast, blue background with white text for too slow. You can mix or match these as desired.

1.0.0 Initial non private release - Fixed the display output so it looks okay on all supported watches. Reduce memory usage by 2K be removing all debug code. Uploaded to public venue. Not 100% sure max array sizes will work on all watches due to memory limits real world but they all run in the simulator.