> 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-beams/creating-a-virtual-source.md).
# Creating a Virtual Source
Create Virtual Source
A Virtual Source is a point in space in which sound appears to be originating from, even though no physical source is present.
You can create two different types of Virtual Sources: Virtual Source Back and Virtual Source Front.
* **Virtual Source Back** creates a point in space behind an array and virtualizes a wavefront that emanates from this point in space.
* **Virtual Source Front** creates a point in space in front of an array and virtualizes a wavefront that converges on this point in space.
To add a Virtual Source to your array, you must first add an array using the **Create Array** option in the toolbar. Next, click **Create Virtual Source** in the contextual menu.
---
# 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-beams/creating-a-virtual-source.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.
