> 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/readme.md).

# RAIDLogs

RAIDLogs turns the robot's logs into a short list of things to check before the next match. After each match the pit crew uploads the robot's CTRE hoot, WPILib and driver station logs; within about two minutes RAIDLogs runs its checks and writes a ranked list, catching problems like a loose CAN connector or a sagging battery before they fail on the field.

## Who this is for

| Role        | What you do                                                       | Start here                                                                                    |
| ----------- | ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| Pit crew    | Set up events, upload logs after each match, read the report card | [Log a match](https://docs.raidrobotics.org/raidlogs/pit-crew-guide/log-a-match.md)           |
| Drive coach | Read matches and post the drive team's debrief from Slack         | [Debrief from Slack](https://docs.raidrobotics.org/raidlogs/drive-team/debrief-from-slack.md) |
| Programmer  | Everything pit crew can, plus tune the checks and map log signals | [Checks](https://docs.raidrobotics.org/raidlogs/programmers/checks.md)                        |
| Admin       | Seasons, users and API keys                                       | [Manage](https://docs.raidrobotics.org/raidlogs/admin/manage.md)                              |

New here? Start with [Sign in and get a role](https://docs.raidrobotics.org/raidlogs/getting-started/sign-in-and-access.md).

## How it fits with the other RAID apps

* **RAIDSystems** owns the robot's history. RAIDLogs copies its revisions, so each match is checked against the robot as it was that day.
* **@RAID in Slack** is one bot shared by the RAID apps. Debriefs come to RAIDLogs; scouting questions go to RAIDScout.


---

# 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/readme.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.
