Skip to main content

Select Event

Syntax​

Select Event        event_name
conditional_command value

Parameters​

  • event_name: The name of the event to compare against.
  • conditional_command: The comparison operator (LT, LE, EQ, GE, GT, NE).
  • value: A time value (e.g., 10:00:00) or the name of another event.

Description​

Compares an entrant's time in one event against a fixed time or against their time in a second event. Only entrants who satisfy the comparison are included in the listing.

Absentees are always excluded

Entrants who do not have a time in event_name are excluded regardless of the operator. RunScore must find the entrant in the event before it can compare times. If the entrant is absent, the comparison is never evaluated and the entrant is dropped.

This means Select Event cannot test for presence or absence in an event. If you need to filter by whether an entrant has a time in a specific event, use the workaround below.

Remarks​

Only one Select Event command can appear in a listing file. For more complex filtering, use Event To Database to move event data into database fields and then filter with Select.

Examples​

Compare against a fixed time​

Find runners who started at or after 10:00:00:

Select Event        Start
GE                  10:00:00

Compare two events​

Find runners whose split time is greater than their finish time (a data-quality check):

Select Event        SPLIT1
GE                  FINISH

Filtering by presence or absence​

Select Event compares times — it cannot test whether an entrant simply has or lacks a time in an event. Use the purpose-built commands below instead.

Entrants recorded by one mat but not another​

Use Not after an Event command. This lists entrants who finished the first event but did not finish the second — without modifying the database.

To list runners recorded by the SECONDARY mat but missed by PRIMARY:

Event               SECONDARY
Not                 PRIMARY
Sort

Entrants who did not finish an event​

Use Did Not Finish to list registered entrants with no result in the specified event.

To list all registered entrants who are missing from the QBSPLIT event:

Did Not Finish
Select              no.
<>
Event               QBSPLIT

Fallback: persist the time to a database field​

If you need the event time stored in a field for downstream use, you can use Event to Database to copy it, then filter with Select.

Field must be blank before first use

Event to Database skips the write when the entrant has no time in the source event — the target field is left unchanged, not blanked. The blank/non-blank test only gives correct results if the field has never been written to before. Re-running the listing after corrections or additional finishers can leave stale values and produce silently wrong output.

To list entrants who have a time in QBSPLIT, writing the time into a previously unused field:

Event to Database
Event               QBSPLIT
Database field      SPLITTIME

Then filter on that field:

Select              SPLITTIME
NE