Analyzing Backup Files

In RUFUS Race Manager, you can treat backup files as if they were additional timing devices. Backup files, often generated by timing hardware at the source, contain passings—essential data entries that record participants’ id and timestamp. By importing and analyzing a backup file, you ensure that all recorded passings are processed through the same logic pipeline as real-time device data. Passings sourced from backup files are identified with type "BACKUP FILE" within the software.

When to Use This Use this feature to incorporate passings recorded outside your primary timing devices—such as from a manual backup system or a secondary timing setup—and integrate them seamlessly into your event’s results.

Step 1: Select Files

Import backup files step 1

1. Open the Devices menu

2. Select “Backup file” Click the Backup file button. This opens the import modal window, allowing you to add and configure your backup files as a data source.

3. Choose the Backup File Format From the “Select file format” dropdown, choose the format type that matches your files. The supported formats are:

   • CSV file

   • TXT file

   • CloudBox backup file

   • One4All 5 backup file

   • RUFUS Cloud device file

   • RUFUS Timing App file

   Note:

   • For CSV or TXT files, you will need to manually map your columns in step 2.

   • For all other supported formats, the software already knows how to interpret the file structure, so step 2 (column mapping) is skipped. You’ll go directly to step 3 to review and confirm the data.

4. Select Your File/s

   Click the upload area to select your backup file/s. A preview of your data will be displayed in the next step.

Step 2: Match Columns (for CSV/TXT Files)

Import backup files step 2

If you selected CSV or TXT:

Column Headers and Field Mapping

If your file includes column headers, enable the corresponding toggle to ensure the software correctly interprets them.

Next, match each column in your file to the appropriate data field. The available mapping options are:

• (ignore): Skip this column.

• Chip: Maps to the participant’s chip number.

• BIB: Maps to the participant’s bib number.

• [Date]: Maps to the date portion of the passing’s timestamp.

• [Time]: Maps to the time portion of the passing’s timestamp.

• [Date][Time]: Use if the timestamp is in a single column all together (e.g., YYYY-MM-DDHH:mm:ss).

• [Date];[Time]: Use if the timestamp uses a “;” as a separator (e.g., YYYY-MM-DD;HH:mm:ss).

• [Date]T[Time]: Use if the timestamp uses a “T” as a separator (e.g., YYYY-MM-DDTHH:mm:ss).

• [Date] [Time]: Use if the date and time are separated by a space (e.g., YYYY-MM-DD HH:mm:ss).

By correctly mapping columns, you ensure the software can recognize participants id and accurately record their times.

Selecting Date and Time Formats

Once you’ve matched the timestamp columns, select the proper date and time formats from the available lists:

Date Formats:

• dd/MM/yyyy, dd-MM-yyyy, dd.MM.yyyy, ddMMyyyy

• MM/dd/yyyy, MM-dd-yyyy, MM.dd.yyyy, MMddyyyy

• yyyy/dd/MM, yyyy-dd-MM, yyyy.dd.MM, yyyyddMM

• yyyy/MM/dd, yyyy-MM-dd, yyyy.MM.dd, yyyyMMdd

Time Formats:

• HH:mm:ss

• HH mm ss

• HHmmss

• HH:mm:ss.SSS

• HH mm ss SSS

• HHmmssSSS

Select the formats that match your file’s timestamp pattern. Getting this right ensures that each passing’s recorded time is parsed correctly.

Skipping Step 2 for Known File Formats

If you selected any format other than CSV or TXT, the software already recognizes that file’s data structure. In these cases, you do not need to manually map columns or select date/time formats. You will skip directly to step 3 to review and confirm the importation data. This streamlined process saves time and reduces configuration complexity.

Step 3: Review & Process

Import backup files step 3

After configuring your columns (CSV/TXT) or if you’ve skipped that step (other formats), you’ll move to Review & process. Here, you can:

• Confirm the number of passings detected.

• Preview a few entries to ensure data is correct.

If everything looks right, click Process to finalize the import. Your backup file’s passings are now integrated into your event data.

After Importing the Backup File

Once processed, backup file passings behave just like any other timing device passings. You can:

• View and Filter Passings: Identify them by their "BACKUP FILE" type.

• Generate Reports and Leaderboards: Include these passings in your event’s overall results and analyses.

• Adjust and Validate: Apply the same validations or corrections as you would for real-time device data.

Tips & Best Practices

• Verify Date/Time Formats: Always double-check the selected formats for timestamps. Incorrect formats can lead to parsing errors or inaccurate times.

• Map Fields Carefully: Ensure that columns containing BIB, Chip, and Date/Time data are matched correctly. Missing or incorrect mappings may lead to unassigned or invalid passings.

• Leverage Known Formats: When possible, use supported file types other than CSV/TXT for a simplified import process.