> For the complete documentation index, see [llms.txt](https://docs.holoplot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.holoplot.com/user-guides/holoplot-system-deployment/venue-validation.md). # Venue validation ## On site The HOLOPLOT system use 3D models in HOLOPLOT Plan to accurately represent the arrays and venues in real life. In order to achieve precision for your system the exact array and target zone positions in your venue must be verified on site to match the HOLOPLOT Plan model before tuning.

Array Placement in Space

Sometimes this means updating Coverage Beam parameters. When the model is corrected, Coverage Beams should be re-optimized before they are tuned. {% hint style="warning" %} Ensure you have on-site internet access to the desktop or laptop running plan on site. Beam optimization requires internet access. {% endhint %} ## Best practices

Reference Point

* Identify reference point in the venue (0,0,0) * Mark reference measures with tape in the venue * Adapt your model depending on the measurements taken

Draw Polygon Tool Select

Use the **Draw Polygon tool** to measure the distances in your venue. You can use the keys to snap the tool to an axis. If the model is incorrect, you can either rework the model in SketchUp or change the position of zones and Arrays in HOLOPLOT Plan.

Cursor Z-Value

Using the **Draw Polygon Tool** you are also able to identify the height of the array (bottom edge) by placing the cursor and reading the Z-value. When your model and the beams are correct, you can export the setup and load it onto the controller. 1. Go to: **File > Export to Controller** 2. Select a name and save it as **\* .holoplot** file.
--- # 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.holoplot.com/user-guides/holoplot-system-deployment/venue-validation.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.