> For the complete documentation index, see [llms.txt](https://docs.ceruleansonar.com/c/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ceruleansonar.com/c/rov-locator/fundamentals-useful-to-system-designers/accuracy-expectations.md).

# Accuracy Expectations

Many factors affect the accuracy of an ROVL system. In this section, we show some real data and discuss the factors in play in this test.

For this test, we took an ROVL system out on an ice-covered freshwater lake. By using an ice-covered lake, we were able to ensure the system elements were not moving around due to currents and wind. We used a Mk III system but the results for a Mk II system would be very similar. 

We cut a hole in the ice for the transceiver in a place where the water was about 8 meters deep, and lowered the transceiver down about 3 meters. We then cut holes for the transponder at distances of about 110 meters, 200 meters, and 295 meters. The water depth increased slowly from the 8 meters at the transceiver to about 15 meters at the 295-meter distance. The bottom undulates along the path and there are vegetation patches to the side.

The transponder was lowered through the hole in the ice slowly to a depth of about 10 meters (with data being accumulated during the drop). 

We used an inexpensive topside GPS at the transceiver location, placed on the ice and not moved during the test.

This test setup is not an ideal environment for sonar, for many of the reasons described earlier in [this section](/c/rov-locator/fundamentals-useful-to-system-designers.md). It does illustrate the accuracy expectations for real-world systems.

The image below is a snip of the test displayed on CeruleanMap. In the following pages we will look in more detail at each of the areas.

<figure><img src="/files/vG4HDpfDLeZiJ1TYSpLq" alt=""><figcaption><p>Overall Test Results</p></figcaption></figure>


---

# 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.ceruleansonar.com/c/rov-locator/fundamentals-useful-to-system-designers/accuracy-expectations.md?ask=<question>&goal=<endgoal>
```

`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.