Checkpoint Dashboard
The Checkpoint Dashboard in RUFUS Race Manager (RRM) provides direct control over whether a checkpoint is actively processing participant passings. This ensures that checkpoints can be enabled or disabled at the right moments during an event, giving organizers precise control over timing operations.
Activating or Deactivating Passing Analysis
The main control available in the Checkpoint Dashboard is the Process Passings toggle:
Activate Passing Analysis → The checkpoint begins processing participant passings. All valid passings are assigned and included in timing calculations.
Deactivate Passing Analysis → The checkpoint stops processing new passings. This is useful once all participants have cleared the checkpoint or when the checkpoint is no longer needed.
Status of Passings When Inactive
If a checkpoint is deactivated:
Passings recorded at that location are still captured and stored.
These passings are marked with the status CHECKPOINT_CLOSED.
This ensures a clear audit trail while preventing the passings from affecting official race timing and rankings.
When to Use This Control
Before the race starts → Keep checkpoints deactivated until just before the event begins to avoid noise from setup or early chip detections.
After all participants have passed → Deactivate a checkpoint once it has served its purpose to prevent unnecessary data (e.g., staff or spectators walking over mats).
Shared physical locations → If start and finish share the same mat but are set as separate checkpoints in RRM, you can close Start while keeping Finish active.
Best Practices
Always verify that Start checkpoints are activated at race start.
Close checkpoints that are no longer needed to keep data clean.
Use separate logical checkpoints for Start and Finish, even if they are physically in the same place, so you can control them independently.
Check the Event Control View for passings with the status CHECKPOINT_CLOSED when reviewing inactive periods.
Last updated