> 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/commands-v3-state-machine/reference/glossary.md).

# Glossary

| Term                           | Meaning                                                                                                                                                                                                                      |
| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **AprilTag**                   | A printed square marker on the field. The Limelights see them and work out where the robot is.                                                                                                                               |
| **Command**                    | A piece of robot behavior that runs over time, like "move the arm to 60°" or "drive to this pose". See [Commands v3 in this project](https://docs.raidrobotics.org/commands-v3-state-machine/concepts/commands-v3.md).       |
| **Coroutine**                  | The way Commands v3 writes a command with steps: an ordinary method that calls `coroutine.yield()` to wait for the next loop.                                                                                                |
| **Default command**            | The command a mechanism runs when nothing else is using it. The drivetrain's is "drive from the joysticks".                                                                                                                  |
| **FOC**                        | Field Oriented Control. A Phoenix Pro feature that gives a motor about 15% more torque.                                                                                                                                      |
| **Hoot file (`.hoot`)**        | CTRE's log file: every signal of every CTRE device, written by Phoenix on its own.                                                                                                                                           |
| **Mechanism**                  | A part of the robot with its own motors, that only one command may use at a time. The Commands v3 name for a subsystem. See [Mechanisms](https://docs.raidrobotics.org/commands-v3-state-machine/guide/mechanisms.md).       |
| **MegaTag 1 / MegaTag 2**      | The two ways a Limelight works out the robot's pose: from tags alone, or from tags plus the gyro heading. See [Vision](https://docs.raidrobotics.org/commands-v3-state-machine/guide/vision.md#megatag-1-and-megatag-2).     |
| **Motion Magic**               | A CTRE control mode: a smooth, speed-limited move to a position, run inside the motor controller.                                                                                                                            |
| **Opmode**                     | One thing the robot can do (a teleop, an auto, a utility), listed on the Driver Station. See [Opmodes](https://docs.raidrobotics.org/commands-v3-state-machine/concepts/opmodes.md).                                         |
| **Pose**                       | Where the robot is on the field: x, y, and which way it's facing.                                                                                                                                                            |
| **Preload**                    | The game piece the robot starts a match holding. The simulator starts with one.                                                                                                                                              |
| **Request**                    | A command that holds up a flag while someone wants something. Buttons and autos make requests; the state machine acts on them. See [Requests](https://docs.raidrobotics.org/commands-v3-state-machine/concepts/requests.md). |
| **State**                      | What the superstructure is doing right now: IDLE, INTAKING, HOLDING or SCORING. Each state is one command that tells every mechanism what to do.                                                                             |
| **State machine**              | A set of states and the transitions between them. The superstructure is one. See [The superstructure state machine](https://docs.raidrobotics.org/commands-v3-state-machine/guide/superstructure.md).                        |
| **Superstructure**             | Every mechanism except the drivetrain, run together by one state machine.                                                                                                                                                    |
| **SysId**                      | WPILib's tool for measuring how a mechanism responds to voltage, to calculate its gains.                                                                                                                                     |
| **Transition**                 | A rule for when the state machine moves from one state to another.                                                                                                                                                           |
| **Trust (standard deviation)** | How far off we expect a vision estimate to be, in meters. Bigger means believe it less.                                                                                                                                      |
| **Tuner X**                    | CTRE's app for configuring and testing CTRE devices. It also generates `TunerConstants.java` for the swerve drive.                                                                                                           |
| **WPILog (`.wpilog`)**         | WPILib's log file: everything the code logs, everything in NetworkTables, and the Driver Station state.                                                                                                                      |


---

# 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/commands-v3-state-machine/reference/glossary.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.
