> For the complete documentation index, see [llms.txt](https://docs.phoenixlidar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phoenixlidar.com/spatialexplorer-8-and-9/user-interface/windows/project/rover/cameras/camera-acquisition-settings.md).
# Camera Acquisition Settings
The acquisition tab of camera settings displays each camera session in the **Sessions** window. A session is a set of image timestamps. Similar to how lidar sessions are organized, anytime you start and stop the camera, you create a camera session. The number of images recorded in the session is shown in parentheses next to the session. The camera configuration parameters used to record each session are displayed in the acquisition tab.
Individual sessions can be disabled by unchecking the session within the **Sessions** window. If disabled, the session will not be used when colorizing a pointcloud, nor when exporting image metadata.
{% hint style="warning" %}
These settings cannot be changed in Work Offline mode. They are simply read-only parameters.
{% 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.phoenixlidar.com/spatialexplorer-8-and-9/user-interface/windows/project/rover/cameras/camera-acquisition-settings.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.