> For the complete documentation index, see [llms.txt](https://docs.optitrack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.optitrack.com/v2.3/motive-ui-panes/info-pane.md).
# Info Pane
The Info pane in Motive displays real-time tracking information of a rigid body selected in Motive. This pane can be accessed under the [View tab](/v2.3/motive-ui-panes/toolbar-command-bar.md) in Motive or by clicking [](https://v23.wiki.optitrack.com/index.php?title=File:Toolbar_Info.png) icon on the main toolbar. This pane lists out real-time tracking information for a selected rigid body in Motive. Reported data includes a total number of tracked rigid body markers, mean errors for each of them, and the 6 Degree of Freedom (position and orientation) tracking data for the rigid body.
{% hint style="info" %}
**Euler Angles**
There are many potential combinations of Euler angles so it is important to understand the order in which rotations are applied, the handedness of the coordinate system, and the axis (positive or negative) that each rotation is applied about. The following conventions are used for representing Euler orientation in Motive:
* Rotation order: XYZ
* All coordinates are \*right-handed\*
* Pitch is degrees about the X axis
* Yaw is degrees about the Y axis
* Roll is degrees about the Z axis
* Position values are in millimeters
{% endhint %}
---
# 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.optitrack.com/v2.3/motive-ui-panes/info-pane.md?ask=&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.
