> For the complete documentation index, see [llms.txt](https://docs.segments.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.segments.ai/how-to-annotate/label-multi-sensor-data/sensors-list.md).
# Sensors list
For multi-sensor datasets, the sensors list can be opened and closed with the backtick key (\`) located to the left of the "1" key on a standard US or UK keyboard. This dropdown now also reflects the presence of the active object on a sensor. If the active object is present, a filled circle appears before the sensor name; an empty circle means that the object is not present. \
\
Additionally, hotkeys for navigating through the sensors are displayed on the right side of the sensor name. For example, pressing key **7** will change the view to **Cam back right**. These hotkeys now extend to the second row of the keyboard rather than only the digits. If there are too many sensors, it will not display a hotkey for it.
---
# 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.segments.ai/how-to-annotate/label-multi-sensor-data/sensors-list.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.
