RUFUS Help
RUFUS Race Manager
RUFUS Race Manager
  • Introduction to RUFUS Race Manager
  • GETTING STARTED
    • Introduction to Race Timing and Race Timing Software
    • Excel 101: Handling Participant Data
    • Networks 101: Understanding the Basics for Race Timing
    • System Requirements for RUFUS Race Manager
  • installation and setup
    • Installing RUFUS Race Manager
    • Initial Configuration
    • User Interface Overview
  • event management
    • Creating a New Event
    • Managing Events
    • Event Settings
    • Event Control View
  • Participant Management
    • Participants Menu
    • Manually Adding Participants
    • Import Participants from List
    • Editing Participant Details
    • Participant Statuses
    • Participant Passings
    • Organizing Participants
  • Checkpoints
    • Understanding Checkpoints
    • Checkpoints Menu
    • Creating Checkpoints
    • Checkpoint Dashboard
    • Checkpoint-Race View
  • Races
    • Races Menu
    • Creating Races
    • Race Dashboard
  • SEGMENTS
    • Understanding Segments
    • Segments Menu
    • Creating Segments
    • Time Visualization
    • Race-Segment View
  • GROUPS AND AGE GROUPS
    • Groups Menu
    • Groups
    • Age groups
  • Timing Devices Integration
    • Introduction to Timing Devices
    • Devices Menu
    • Connecting Local Devices
    • Connecting Cloud Devices
    • Analyzing Backup Files
    • Event-Devices View
    • Rewind Passings
  • Collecting and Managing Timing Data
    • Understanding the Data Collection Process
    • Timing on Race Day
    • Adding Manual Passings
    • Monitoring Live Timing Data
    • Editing Timing Data
    • Passing Statuses
    • Reprocess Passings
  • Classification and Results Processing
    • Understanding Classifications
    • Results Menu
    • Viewing Race Results
    • Generating Reports
  • PUBLISHING IN THE RUFUS EVENT APP
    • Publishing the Event
    • Publishing Participant Information
    • Publishing Race Results
  • Offline Mode and Data Synchronization
    • Working Offline with RRM
    • Data Synchronization
  • Troubleshooting and Support
    • Common Issues and Solutions
    • Frequently Asked Questions (FAQs)
  • Updates and New Features
    • Upcoming Features
    • Keeping RRM Updated
    • Changelog
  • Best Practices and Tips
    • Optimizing Race Timing Workflow
    • Data Management Best Practices
Powered by GitBook
On this page
  • Activating/Deactivating Passing Analysis
  • When to Use Passing Analysis Activation
  • Status of Passings When Checkpoint is Deactivated
  1. Checkpoints

Checkpoint Dashboard

PreviousCreating CheckpointsNextCheckpoint-Race View

Last updated 3 months ago

The Checkpoint Dashboard in RUFUS Race Manager (RRM) provides a way to manage the activity status of a checkpoint. This feature is crucial for ensuring that each checkpoint is processing participant passings correctly during the event. In this article, we'll cover the current functionality of the Checkpoint Dashboard. More features in the form of widgets are yet to come to the Checkpoint Dashboard, which will display relevant information about the checkpoint, such as timing efficiency, checkpoint statistics, time correction, last passings, and more.

Activating/Deactivating Passing Analysis

The main feature available in the Checkpoint Dashboard at this time is the ability to activate or deactivate the passing analysis for a checkpoint. This toggle allows race organizers to control whether a checkpoint is actively processing participant passings.

When to Use Passing Analysis Activation

  • Activate Passing Analysis: Ensure that the checkpoint is activated for processing participant data before the race begins. This ensures that all participant passings are recorded and analyzed accurately.

  • Deactivate Passing Analysis: If the checkpoint is no longer in use (for example, all participants have passed through it), you can deactivate the checkpoint to prevent any further unwanted readings.

Status of Passings When Checkpoint is Deactivated

Any passings recorded while the checkpoint is deactivated will be marked with the status CHECKPOINT_CLOSED. This status indicates that the passing occurred while the checkpoint was inactive and should not be included in the final race analysis.

Process Passings Toggle