Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 50 million developers.Sign up
Guess marks during an event During an event, while the riders haven't finished all zones and rounds, order the riders by their expected performance and not by how many zones they have already completed: * When riders haven't tried a particular zone yet, assume they will be credited the average number of marks in that zone (in their class). * When riders have tried a particular zone already, assume they will achieve the same average result in the remaining attempts. Riders that have failed are still ordered by how far they have come.
Adapt marks computation to mobile scoring So far, rider scores were mostly entered round by round, and zones skipped in a round could immediately be marked as skipped. When computing the results of an event, results were only counted up to the first zone that hasn't been entered yet. With mobile scoring, the results from different zones can arrive in a very different order, so it makes more sense to count all the results. Riders are now ranked by the number of completed rounds, the number of completed zones, and only then by their marks, etc. The results table indicates which rounds are still incomplete.
Ignore scoring data when computing a patch When computing a diff between two /api/event/:tag/dump dumps, ignore the scoring data and computed fields for now. We'll eventually sync the scoring data as well, which will allow the other side to recompute those fields.