# Prediction dashboard

* **Before the event:** Checklist to quickly prepare and test predictive live tracking.
* **During the race:** Relevant information for monitoring and adjusting the prediction.
* **After the race:** With the purpose of analyzing the prediction all data for each athlete is prepared and linked in a map, in diagrams, and in a table.

![Dashboard to monitor reads from the timing system in order to compose a live visualization of the race](/files/BlVTqxAsLLTWHuWciXiB)

**Status:** Checklist for settings required to conduct predictive tracking. The status tab also provides an auto-check of the forwarding settings in RACE RESULT.

**Readers:** When Racemap receives detections, the locations of corresponding readers are shown on a map. There is a hint for readers that are placed too far from the shadowtrack, and its reads are not considered for prediction (rejected reads). The track is also shown as an elevation profile with the corresponding readers' locations.

**Transponders:** Table showing various information of the last received read for each transponder: recorded- and received timestamp, location, reader id. Additionally, the start- and finish time is shown if imported to the participant data.

**Reads:** Continuously running list of all received reads from your timing system.

**Analysis:** Select one participant and analyze all its aggregated information. Data is linked in a map, a table, and in diagrams. 

**Parameters:** Set the parameters that impact predictive tracking.


---

# Agent Instructions: 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:

```
GET https://docs.racemap.com/prediction/dashboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.