Hello drivers,
In assessing the results of the 12 Hours of Kyoto GP, we had a large amount of data to consider, and several courses of action to choose from. We are happy to report that the series admins (myself, Appie, Three_Jump) have reached a unanimous choice among these courses, and we can now present you with race results and a clear policy for how we will deal with future incidents of this nature, should they occur.
The course we have chosen is to treat the interruption in the race as a "red flag" condition. The result of this policy is as follows:
A rules amendment will be made shortly in order to fully delineate handling of race stoppages.
*Results after processing penalty related to Scipy's cheat: http://www.lfsforum.net/showthread.php?t=50271
Part 1 Replay
Part 2 Replay
In assessing the results of the 12 Hours of Kyoto GP, we had a large amount of data to consider, and several courses of action to choose from. We are happy to report that the series admins (myself, Appie, Three_Jump) have reached a unanimous choice among these courses, and we can now present you with race results and a clear policy for how we will deal with future incidents of this nature, should they occur.
The course we have chosen is to treat the interruption in the race as a "red flag" condition. The result of this policy is as follows:
- A red flag lap is determined for the entire field, based on prevailing server conditions (i.e., the last complete lap prior to the point at which the server begins to seriously malfunction). In this case, it was lap 88 for the overall leaders at the time, Mercury Racing GT1.
- All teams completing this lap behind the leader are credited with the lap count they hold at the time they cross the line. This count is determined using the tracker and the server-side replay.
- Gaps in minutes and seconds are erased as they would be in a corresponding real life red flag situation.
- The field is reset using the data gathered from the red flag lap results.
- The race continues, and the race time remaining is based on the planned race-end time, not on the time of the server crash.
- At the end of the second part of the race, the lap totals for parts 1 and 2 are combined, and teams with the same amount of total laps are ranked based on their on-track position at the end of part 2.
- It is a more logical solution to a race stoppage and a better simulation of real life endurance racing (in this case, the IMSA/ACO rule set), which is our ultimate aim.
- Using lap-based gaps is less likely to cause major damage to the standing of a team who has just made a pitstop, or spun, at the selected "red flag" lap than would minute/second gaps. In short, it takes a less precise but more broadly accurate snapshot of the standings at a given point in the race.
- It provides a much better potential for us to offer clear and timely in-race standings via the tracker during the second part of an interrupted race. Obviously this was not the case during the 12 Hours of Kyoto, but that was due to unrelated factors and we are making it our business to have a plan in place for future occurrences.
- As an extension of #3, disregarding second/minute gaps from the first part means that the race in the second half produces a clear winner--one that will not have to be produced via statistical analysis post-race. We feel that this will be far more satisfying for all involved.
A rules amendment will be made shortly in order to fully delineate handling of race stoppages.
*Results after processing penalty related to Scipy's cheat: http://www.lfsforum.net/showthread.php?t=50271
Part 1 Replay
Part 2 Replay