> 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/holoplot-plan/working-with-matrix-arrays.md).
# Working with Matrix Arrays
A Matrix Array is a collection of one or more HOLOPLOT X1 Modules (MD96, MD80-S or S21), or of one or more X2 modules (MD30) configured as a single unit.
X1 and X2 modules cannot be combined together inside the same array.
Arrays in HOLOPLOT Plan contain beams with tailored properties that are visualized in the Simulation and can later be deployed to real-world arrays for system configuration and sound reproduction. You can create an array in HOLOPLOT Plan using the Array Builder window (recommended), or design one externally in SketchUp and import it as a .glTF file.
{% hint style="info" %}
If you want to learn more about best practices with Array design, check out the guides on [How do I decide on the position of my Arrays](/user-guides/holoplot-system-design/system-design-best-practices/how-do-i-decide-on-the-position-of-my-arrays.md) and [What should be the size and aspect ratio of my Arrays?](/user-guides/holoplot-system-design/system-design-best-practices/what-should-be-the-size-and-aspect-ratio-of-my-arrays.md)
{% 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 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/holoplot-plan/working-with-matrix-arrays.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.
