Understanding Checkpoints
Checkpoints are a fundamental element of race timing in RUFUS Race Manager (RRM). They represent specific locations on the racecourse where participants’ times are recorded, enabling accurate tracking of progress, splits, laps, and results.
Checkpoints work within a race’s plan — the ordered list of checkpoints a participant must pass. Each checkpoint has a lap ID, a type (start, intermediate, or finish), and may have additional properties such as whether it closes a lap.
What Are Checkpoints
A checkpoint is a designated location on the racecourse where participants’ passings are logged. Timing devices (e.g., RFID readers, manual entries, floating passings) capture these passings as participants cross.
Start checkpoint → Marks the official beginning of a race (lap 0). If missing, RRM may create a synthetic start at race time + 1 ms to guarantee continuity.
Intermediate checkpoints → Record splits and help validate course completion. Each increments the lap ID according to the race plan.
Finish checkpoint → Marks the end of the race (lap 9999). After a valid finish, all subsequent passings for the same participant on that device are marked EOTR (End of the Road).
Race Plan vs Device Plan
Race Plan → The full ordered sequence of checkpoints for a participant’s race. This defines the expected course from start to finish.
Device Plan → A filtered subset of checkpoints that a specific device records (e.g., a 10k mat only has the 10k checkpoint).
When a passing is recorded:
The race plan determines what checkpoint comes next.
The device plan determines whether the passing matches the device’s assigned scope.
Floating passings are special because they are not tied to a device plan. Instead, they use the full race plan as scope, letting the system infer the correct next checkpoint.
Importance of Checkpoints
Checkpoints provide several critical functions:
Start and finish tracking → Calculate total race times.
Intermediate splits → Track pacing and performance at multiple stages.
Validation of completion → Ensure participants follow the full course.
Lap and segment creation → Define race structure, including repeated laps and sector splits.
Flexibility of Checkpoints
Checkpoints in RRM are highly configurable:
Shared checkpoints → A single checkpoint may serve as both start and finish (common in loop or out-and-back races).
Separate checkpoints → Distinct start and finish points, with intermediates in between.
Multi-lap checkpoints → Configured to repeat across multiple laps (e.g., triathlon bike loops or circuit races).
Lap-closer checkpoints → Define when a lap is complete, ensuring laps are validated correctly.
Tips for Setting Up Checkpoints
Plan placement carefully → Place checkpoints at the start, finish, and key points along the course.
Use consistent naming → Descriptive names like Start, Finish, or 10k Split help during setup and race control.
Test in advance → Run devices and check test passings to confirm configuration before race day.
Summary
Checkpoints form the backbone of race timing in RRM. They define the race plan, structure lap progression, and ensure fair and accurate results. Whether shared, separate, or repeated across laps, checkpoints give race organizers flexibility to adapt to any race format.
By understanding how checkpoints interact with devices, participants, and passings, timers can confidently manage both simple and complex race scenarios.
Last updated