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:
ASSIGNED: Passing has been successfully assigned to a participant. (internal status)
NO_RACE: Passing could not be assigned to any race.
WRONG_RACE: Passing was assigned but to the incorrect race.
DEVICE_CLOSED: Passing was recorded while the device was not active.
RACE_CLOSED: Passing was recorded after the race had ended.
CHECKPOINT_CLOSED: Passing was recorded while the checkpoint was not active.
TIME_VALID: The timestamp of the passing is within valid limits. (internal status)
TIME_INVALID: The passing's timestamp is invalid for the current race.
VALID: Passing is valid and used for classification.
EOTR (End Of The Road): Indicates the end of valid iterations for a passing.
BOUNCED_BY_CHECKPOINT: Passing was ignored due to being captured too soon after a previous valid one (checkpoint-specific bounce).
BOUNCED_BY_DEVICE: Passing was ignored due to being captured too soon after a previous valid one (device-specific bounce).
VALIDATED_BY_USER: Passing has been validated manually by the user.
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.
Last updated