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
  1. Collecting and Managing Timing Data

Passing Statuses

In RUFUS Race Manager (RRM), passings can have different statuses that indicate their current state in the system. These statuses help classify the data for validation, race assignments, and consistency. Below is a summary of all possible passing statuses in RRM:

  1. ASSIGNED: Passing has been successfully assigned to a participant. (internal status)

  2. NO_RACE: Passing could not be assigned to any race.

  3. WRONG_RACE: Passing was assigned but to the incorrect race.

  4. DEVICE_CLOSED: Passing was recorded while the device was not active.

  5. RACE_CLOSED: Passing was recorded after the race had ended.

  6. CHECKPOINT_CLOSED: Passing was recorded while the checkpoint was not active.

  7. TIME_VALID: The timestamp of the passing is within valid limits. (internal status)

  8. TIME_INVALID: The passing's timestamp is invalid for the current race.

  9. VALID: Passing is valid and used for classification.

  10. EOTR (End Of The Road): Indicates the end of valid iterations for a passing.

  11. BOUNCED_BY_CHECKPOINT: Passing was ignored due to being captured too soon after a previous valid one (checkpoint-specific bounce).

  12. BOUNCED_BY_DEVICE: Passing was ignored due to being captured too soon after a previous valid one (device-specific bounce).

  13. VALIDATED_BY_USER: Passing has been validated manually by the user.

  14. INVALIDATED_BY_USER: Passing has been invalidated manually by the user.

These statuses are essential for ensuring that race timing and classifications are accurate and reliable. They help maintain the integrity of the timing data by clearly indicating the condition of each passing throughout the race process.

PreviousEditing Timing DataNextReprocess Passings

Last updated 7 months ago