Assignment
Who wears which transponder, race by race. The tab shows the transponders passed from one race to another (yellow: normal; red: conflict), and lets you change them one at a time or all at once for several races.
- The commands and the minimum gap between two races.
- The legend and the session summary.
- A race: its name, its time, its state, then one tile per athlete, in the colours of their start position.
- Yellow ▲: the transponder is reused long enough afterwards (normal).
- Red ✖: a real conflict.
Assignment
Where: Timing, Assignment tab. It is always there when the session's technology is “decoder” or “hybrid” and the assignment mode (Configuration › Mode › Assignment) is not “Auto-assignment”. Otherwise, it appears as soon as the session assigns at least one transponder: JSON file, Excel, session created with Create an Excel session… (History → Athletes), EVENT .cfevent, automatic assignment on crossing.
One row per race, in start order, with its time (“scheduled 10:30” when the file gives it, “start 10:31” once it has started) and its state. In each row, one tile per athlete, in start order: their name (otherwise their bib), their position, then their transponders no. 1 and no. 2, each with its ID (the printed code, otherwise the number) and its usual code in a dark badge (the short code painted or stuck on the transponder, entered in History → Transponders). The tile takes the colours of the start position when Colour athletes by start position is checked (Settings), otherwise those of the athlete. What the tab shows is the actual assignment: the one being timed for a loaded race, the one that will be loaded for a race in the list.
Raced races also shows the races already raced (and counts them for duplicates).
Yellow, red: reused transponders
| State | When |
|---|---|
| ▲ Yellow | The transponder was already used in a race that ends at least Minimum gap between two races (20 min by default) before this one starts. This is normal: athletes bring their transponder back to the start line for others. Also yellow, with a warning: when the time of one of the two races is unknown (check the gap yourself). |
| ✖ Red | A real conflict: the same transponder twice in the same race (always), in two races run together (same group, races loaded together), whose times overlap, or less than the minimum gap apart. Both occurrences are red. |
The first occurrence of a reused transponder has no colour. The tooltip of each transponder says why it is yellow or red, with whom and in which race it is shared. The end of a race without an end time is estimated cautiously (about 8 m/s).
Where the transponders come from: the assignment mode
The mode is chosen in Configuration › Mode › Assignment; one at a time:
| Mode | When the session is read | Assignment tab |
|---|---|---|
| Auto-assignment | Nothing: each transponder will go, on its first crossing, to the athlete in its start position. The transponders written in a .cfevent or an .evt are kept. | As soon as a transponder is assigned. |
| By the transponder's usual code | The kits, by usual code split at “;”: 3_BLANC, 3_ROUGE (pairs), 2_TEAM_1 (pursuits), 1_MASSTART_4 (mass starts); one transponder can carry several: 3_ROUGE;1_MASSTART_4. | Always (decoder, hybrid). |
| Transponders from the athlete record | Transponders no. 1 and no. 2 from each athlete's record, in all their races; none if the record has none. | Always (decoder, hybrid). |
An Excel session file keeps its own behaviour in all three modes: its first sheet is authoritative.
- The ⚠ alert: the tile has a gold border, the race header counts the athletes without a transponder, and so does the summary. Give them a transponder with a click (below), or complete their record and read the session again.
In “By the transponder's usual code” mode, the alert says that no usual code matches their race or position. In automatic mode there is no alert: the transponder will come on the first crossing.
Changing an athlete's transponder
Clicking a transponder in a tile (or the “+” of no. 2) opens the list of transponders known to the database. Type part of the ID or of the usual code: the list filters (the exact usual code first); in orange, those already used elsewhere in the session. Choose Transponder no. 1 or Transponder no. 2 (replace or add), then Choose; Remove this transponder empties the slot. A transponder already worn by another athlete in the same race is refused.
Reassigning several races
- Choose the races
Click a row, then Ctrl+click or Shift+click to add more.
- Reassign…
Give the usual codes in order: a range (
1-40,40-1,001-040,P1-P12) or a pasted list (one code per line, or separated by commas). Choose what the code replaces: transponders no. 1 and no. 2 (a code carried by two transponders, one per foot, gives both), no. 1 only or no. 2 only.The codes go to the athletes in the order of the chosen races, then in start order. The preview (before, after, remarks) follows each keystroke; unknown, extra or missing codes are reported.
- Apply
Everything changes at once. Undo the reassignment or Ctrl+Z undoes the last change (the last 50 are kept).
One line per start position
In Codes go, choose One line per start position: each line you type goes to one start position. Line 1 gives its codes to the athletes in position 1 of the chosen races, in race order; line 2 to those in position 2, and so on. In sequence (races, then start order) keeps the former rule: a single sequence of codes, race after race.
Example, three pairs chosen (P01, P02, P03) and two lines:
14_ROUGE-16_ROUGE 14_JAUNE-16_JAUNE
| Race | Position 1 (line 1) | Position 2 (line 2) |
|---|---|---|
| P01 | 14_ROUGE | 14_JAUNE |
| P02 | 15_ROUGE | 15_JAUNE |
| P03 | 16_ROUGE | 16_JAUNE |
A range A-B whose bounds have a number and the same suffix is expanded: 14_ROUGE-20_ROUGE gives 14_ROUGE, 15_ROUGE… 20_ROUGE; leading zeros are kept (08_JAUNE-10_JAUNE: 08_JAUNE, 09_JAUNE, 10_JAUNE). A line can also be a list separated by commas or spaces. Empty lines do not count.
If a line has too many or too few codes for the number of races, the preview says so below the list: “Line 2 (position 2): 1 code(s) missing, for …” or “… extra code(s), not used: …”. A position with no line, or no code, stays unchanged (“No code for position 3: unchanged”).
Saved reassignments
Next to the entry box, the Saved reassignments list keeps your usual entries under a name (for example “Red and yellow pairs”):
- Save as… keeps the entry and the choice in Codes go (in sequence, or one line per start position) under the name you give; a name that already exists is replaced after confirmation;
- choosing a name in the list reloads its entry and its mode, and the preview is redone at once;
- Rename… and Delete act on the chosen name; the current entry stays.
They are kept in the FINISH settings on this station: they carry over from one session to the next, but do not follow the session file. The choice of what the code replaces is not part of them.
Printing
Print… opens the preview: A4 or Letter paper, landscape, one race per page, athletes' colours. Each reused or conflicting transponder carries its symbol (▲, ✖) and a reference to a note that explains it, at the end of the list: the list stays readable in black and white. “Microsoft Print to PDF” makes a PDF of it.