RemoteRacing™ uses EnviroNorm® to normalize remote and onsite racing environments, RaceX to simulate onsite race outcomes, and a unique remote race flow to make the remote race experience as comparable to onsite racing as possible.
Your remote results are normalized based on your remote environment and terrain (elevation, temperature, humidity, wind, wind direction, air pressure, course elevation change, and so forth) then localized to the environment and terrain of the associated onsite race to produce the finish time you would have gotten had you actually competed onsite.
Here’s how it all comes together:
Swim localization accounts for internal and external impacts due to differences between your remote swimming pool and the onsite swim venue such as elevation, salt or fresh water, water current, open water or pool, wetsuit or no wetsuit, pool format (short-course yards, short-course meters, or long-course meters).
Swim-to-Bike Transition (T1)
Inconsistent pool accessibility and proximity to adequate bike and run routes for many participants requiring the swim to be performed immediately before the bike unfair and impractical. Due to this fact, the time between your swim and bike activities is unregulated.
Your T1 time in the final results is calculated to be comparable to what it would have been if you’d have competed in the Simulated Race based on the range of actual onsite T1 times and your run verified run threshold. Eg. If the onsite T1 times ranged from 4:00 to 6:00 and your pre-verified run threshold is at the fiftieth percentile, then your T1 time would be 5:00.
Bike localization accounts for internal and external impacts due to differences between remote and onsite environments and terrains such as temperature, humidity, elevation, elevation change, wind speed, wind direction, wind exposure, yaw angle, and road surface.
RemoteRacing computes each participant’s aerodynamic drag (CdA) used in onsite simulations based on their individual height and weight, but a standard bike equipment setup and riding position are used for all participants. This standardized approach creates a level playing field as it relates to bike aerodynamics with everyone essentially “riding” the same bike for simulation purposes. It also allows all participants to perform their remote bike segment in their most powerful position.
Bike-to-Run Transition (T2)
Due to fairness and practicality, Remote Races use a fixed 10-minute T2 time for all participants during the race then calculates a results T2 time that would be comparable to the onsite race. Similar to the T1 time calculation, your T2 time is calculated based on the range of actual onsite T2 times, your run threshold, and any time between your bike and run beyond the fixed time allotted. Eg. If the onsite T2 times ranged from 4:00 to 6:00 and your pre-verified run threshold is at the fiftieth percentile and you spent 12:00 between your bike and run, then your T2 time would be 7:00 (5:00 plus the 2:00 beyond the allotted T2 time).
Run localization accounts for internal and external impacts due to differences between remote and onsite environments and terrains such as temperature, humidity, elevation, wind, and elevation change (hills).