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

# Power, vision and signals

Besides the report card, a match page has more views for digging in.

| View            | What it shows                                                                                                                                                                                                            |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Power**       | Battery numbers (resting voltage, lowest voltage, internal resistance, worst sags), supply current over the match stacked by mechanism, energy by mechanism, and time at current limits. Experimental parts are labeled. |
| **Vision**      | Each Limelight's dropouts, tags seen, latency and position jumps, how far its pose was from odometry, and a timeline per camera from the first enable.                                                                   |
| **Performance** | Robot loop time (target 20 ms), CAN and CPU load, time in each robot state, closed-loop tracking, and where auto ended. Experimental.                                                                                    |
| **Signals**     | Everything the log recorded. Pick up to four numeric signals to chart.                                                                                                                                                   |

Several views compare this match with the median of the event's other checked matches. Systems check runs aren't counted in those medians.

If a view says there's no data, the match is missing the file it needs, usually the roboRIO `.wpilog`, or a signal hasn't been mapped in [Signals](https://docs.raidrobotics.org/raidlogs/programmers/signals-and-mechanisms.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/match-views.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.
