> 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/use-wiclax/acquisition-of-timing-data/passage-conditions.md).
# Passage conditions
Passage conditions allow for more precise control of abnormal passing acquisition cases. For example, a lap of the circuit that is too fast to be real, or a race time that probably corresponds to a withdrawal.
## Settings
For the case of lap races, the minimum lap time (possibly race by race) is entered here:
For other conditions, you have to go through the settings screen for split points and segments, and click on the icon in the thumbnail of the desired split:
The form that opens allows you to enter as many conditions as you want, which will add up if they concern the same race:
The + button gives access to other types of conditions than the minimum race time:
Which allow you to reject a passage if:
| A minimum time between 2 points is not respected | |
| ------------------------------------------------------------------------ | ------------------------------------------------------------------- |
| The competitor was not previously detected at one or several checkpoints | |
| At least a number of previous checkpoints are missing | |
| Some custom condition is not met | |
{% hint style="info" %}
Note that most conditions assume that the passages will be integrated in the natural order. For example, if there is a segment time condition between a CP 1 and CP 2, and the CP 1 data is imported after that of CP 2, the times already integrated on the CP 2 will not be affected by the condition.
{% endhint %}
## Monitoring
When a passage is rejected due to a custom condition, its thumbnail displays the information like this:
Information also found in the history of passages on the results form:
---
# 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/use-wiclax/acquisition-of-timing-data/passage-conditions.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.