> For the complete documentation index, see [llms.txt](https://docs.theiamarkerless.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theiamarkerless.com/apollo-v2024/troubleshooting/error-messages/qualisys-calibration-has-inconsistent-fov.md).
# Qualisys calibration has inconsistent FOV
### Explanation
This error message may arise when loading a calibration file exported from Qualisys Track Manager after performing a wand calibration. It indicates that the selected calibration file has inconsistent field of view parameters for the cameras contained within the calibration file. The field of view parameters are important for determining the area of the camera sensor used in the recording of the calibration trial.
The FOV parameters may be inconsistent if the videos for the currently loaded trial were recorded at a camera resolution that differs from that used during the wand calibration. The resolution of the videos must be consistent between the calibration trial and the recorded movement trials.
### Possible Solutions
Perform a new wand calibration using the same camera resolutions as used for your movement trials. If the cameras have not moved since the movement trials were recorded, it may be possible to record and export a new wand calibration file using the same video resolutions as used for the movement trials. This would allow the videos to be calibrated properly.
---
# 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.theiamarkerless.com/apollo-v2024/troubleshooting/error-messages/qualisys-calibration-has-inconsistent-fov.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.
