> For the complete documentation index, see [llms.txt](https://docs.dryad.app/dryad-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dryad.app/dryad-documentation/silvanet-test-fires/overview.md). # Overview Use test fires with a set of Sensors to view fire alerts. {% hint style="danger" %} **About test fires** Running test fires are optional. If you plan on conducting fire tests, carefully follow the instructions provided in this section. {% endhint %} ## In this section
Test fire preparationA test deployment can include one Border Gateway and up to twenty sensors. Ensure you allow 14 days for sensor calibration.card-preparation-guidelines.jpg
Run test firescarefully follow the guidelines and steps provided in this topic to safely run test fires and generate fire alarms.card-run-test-fire.jpg
Modify fire setupsModify only one aspect of the test, such as distance between Sensors, location of fire pit or type of material burnt.card-modify-fire-setups.jpg
--- # 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.dryad.app/dryad-documentation/silvanet-test-fires/overview.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.