> For the complete documentation index, see [llms.txt](https://docs.wiclax.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wiclax.com/en/all-competition-types/lap-race-circuit.md). # Lap race, circuit A lap-based event counts the number of times a runner crosses the finish line. This setting becomes necessary when competitors are expected to cross the finish line a large number of times, and in cases when the exact number of crossings is initially unknown, such as in a 24-hour race. ## Creation and settings In the [event creation wizard](/en/use-wiclax/event-wizard.md), the choice of discipline and event type can directly lead to a lap race configuration - a 24h mountain bike, a circuit car race or a circuit cross-country to name a few examples. You will then be able to specify some key information such as the duration of the event, the number of laps to be completed, the lap distance. After that all the settings relating to lap management can be found in the event options window, Laps tab.

Here we can specify: * specific criteria for each race, if necessary: number of laps, duration, lap distance * a specific first-lap distance, if applicable * general options applying to laps management ### Race start The `First crossing of the line is not a lap` option is here to manage the case where the start is given upstream of the finish line, or outside the circuit. Consequently, the first crossing of the line is recorded but does not increment the number of laps. The distance of the section between the start and the first crossing of the line can be specified. The option `Shifted Start - the first competitor crossing the line gives the start` allows you to manage a start signal and a time base corresponding to the first crossing of the line. ### Trial rounds Each stage/round can be labeled as a trial round or a qualifying round. ### Ranking on best lap Among the lap options, you can specify that the race (or stage) ranking is based on the best lap. ## Fixed duration races These are 24-hour type races, or any other duration after which the race is considered finished. ### End of the race The `Allow competitors to finish their last lap after time expires` option can be enabled or disabled. The `race duration + n laps` option specifies that after the duration expires - for example 12min - competitors are allowed to cross the line n+1 times. In other words, a duration + 1 lap setting allows the current lap to be finished and an additional one to be performed. **Final distance** In a 24-hour kind of race, it may happen that the race time stops strictly at the end of the duration and that the position of the stopped participants is then measured by the referees. It is possible from the results grid to display the *Last lap distance* column and edit its values directly in the grid. Entering this distance has the following effects: * calculates the total distance completed taking into account this last section * modifies the ranking in the event that a runner has overtaken another on this last section (both having the same total of laps) ## Fixed-lap races These are the races where the number of laps to be completed is initially known. Although it can be changed during the race. ### End of race The option `End of Race when the leader finishes his last lap` is applicable within the framework of a fixed number of laps. From the moment the leader has completed them, the following competitors are only authorized to finish their ongoing lap. ## Races with an undetermined number of laps This mode is for races where the number of laps to be completed can change during the competition. And which also do not have a set duration. ## Managing results Monitoring of rankings can be done at several levels: 1. the main results grid displays the synthetic ranking of the race, without the details of the laps 2. The Laps tab offers 2 viewing modes. The first is a raw list of all the passes and the second is a matrix of the laps that updates in real time You can switch from one mode to another using the buttons

above the grid.

{% hint style="info" %} When the number of laps becomes too large, it is possible to switch to compact mode by clicking on the button

{% endhint %} {% hint style="info" %} In relay mode, the matrix also provides a view of the cumulative laps, with a line per team and details of the team members who completed each lap. {% endhint %} {% hint style="info" %} In list of passages mode, you can request a quick filter to obtain the ranking for a given lap:

{% endhint %} ### Acquisitions In a lap race, it is important to note that the primary destination for acquisitions will be the finish line. This is where the lap count is incremented. ### Manual entries The results entry form presents the list of passage times on the timed lines.

You can here: * add or remove passages, via the + and - buttons below the list * change the time of one of the passages * view the status of a passage from its first cell. Either by the symbol drawn or by hovering over it to display more information

* change the status of a passage row with a right click on the same column:

### Intermediate splits and segments For lap races, an intermediate split point means a point of the circuit, which competitors must pass on each lap. The segments are also a part of the circuit and are repeated on each lap. ## Printout As with race monitoring, you can choose to print either the main results grid or the lap matrix. In the case of the results grid, you can ask in the print data selection to get one detail column for each lap. ## Circuit mode The so-called "circuit" mode applies when the event is initially created for the motor sport discipline. It integrates the management of race events, which are reflected by the flags that are clicked to switch from one status to another. The processing of the passages is affected accordingly, for example a crossing of the line when the race is suspended is recorded but not counted, and it receives a suspended race status.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.wiclax.com/en/all-competition-types/lap-race-circuit.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.