> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/raidlogs/pit-crew-guide/log-a-match.md).

# Log a match

After each match, get the logs into RAIDLogs. There are two ways.

## Log a match

1. Open **Matches** and click **Log a match**.
2. Pick the **Match type** and number (the next number is suggested), the battery and the drive team. A match video link, the robot code commit and a note are optional.
3. Choose the log files from the pit laptop and save. Keep this page open until the upload finishes.

## Upload logs

**Upload logs** takes a whole folder at once, for example a USB stick after several matches. Each file goes to the match its name or time points at: the file name first, then a file recorded beside it, then the schedule, then practice runs grouped by time. Check the list under **Where each file goes**, set anything to **Don't upload** if it shouldn't go, then upload.

## Which files

| File                     | From                      | Gives                                                              |
| ------------------------ | ------------------------- | ------------------------------------------------------------------ |
| `.wpilog`                | The roboRIO               | Brownouts, battery voltage, CAN bus stats, robot state, Limelights |
| `.hoot.wpilog`           | CTRE hoot logs, converted | Every motor and CAN device                                         |
| `.dslog` and `.dsevents` | The driver station        | Connection, packet loss, trip time                                 |

CTRE `.hoot` files aren't read directly: convert them first (see [Pit laptop tools](https://docs.raidrobotics.org/raidlogs/programmers/pit-laptop-tools.md)). Keep the CAN bus name in the file name; findings use it. A `.wpilog` over 250 MB isn't read.

The checks start on their own about 15 seconds after the last upload. Then open the match for its [report card](https://docs.raidrobotics.org/raidlogs/pit-crew-guide/report-card.md).


---

# 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.raidrobotics.org/raidlogs/pit-crew-guide/log-a-match.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.
