Relays and forking keys

Say which course each leg of a relay runs. If the course is forked, a forking key is worked out for every team: which variation the team runs on each leg.

1. 1Under Relays in the course panel (advanced, with forking on): press New relay and type the class name as in the timing system.
2. 2Choose the course for each leg. The legs can have different courses, and the same course can come back.
3. 3Set Number of teams and First bib number. Take a few more teams than you expect: the keys belong to the bib, and teams that do not enter are skipped.
4. 4Press Export IOF XML. The keys come along, and ControlFreak Event or MeOS takes them by the teams' bibs.

• The keys are given branch by branch: teams with numbers next to each other run different branches at every fork. Put the course on as many legs as its forks have branches and all teams run the same controls in total. If that is not possible, it says so under the relay.
• Below the keys it says how many maps of each variation each leg needs, and Show the keys shows each team's variation per leg.
• Print maps per team makes a PDF with one page per team and leg, marked with bib, leg and variation ("12-2 AD"). Choose Team by team for an envelope per team, or Leg by leg for a pile per changeover. Each course is printed with its own print area and paper.
• Once the maps per team are printed, the relay remembers the keys they were printed with. If a course or fork changes so that a team gets another key, it says in red which bib numbers are affected: print the maps again, or change it back.
• A leg can have several runners side by side: choose the number next to the course. Tick Parallel runners run different variations for them to take different branches, so that they cannot follow each other; otherwise all run the leg's variation. The key writes parallel variations with a plus, e.g. AD+BE, and the print gives each runner a page of their own ("12-2.1").