> For the complete documentation index, see [llms.txt](https://docs.racemap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.racemap.com/prediction/dashboard.md).

# Prediction dashboard

The dashboard supports you during all phases of predictive tracking and provides insights into data processing.

* **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](https://1672210197-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LSRNxaH2Ju9Flr7JhJD%2Fuploads%2Fgit-blob-e9658f9242da2818e1bd5c65b24a9247a0746310%2Fprediction%20-%20tab.gif?alt=media)

**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](/glossary.md#read), 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](/glossary.md#rejected-read)). Reader distance is one of several rejection causes; the Analyse tab lists every read with its [mappings](/glossary.md#mapping) and states the reason for each rejection individually. 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**](/glossary.md#read)**:** 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
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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.