> 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.md).

# Silvanet Test Fires

- [Overview](https://docs.dryad.app/dryad-documentation/silvanet-test-fires/overview.md): Use test fires with a set of Sensors to view fire alerts.
- [Fire test plan](https://docs.dryad.app/dryad-documentation/silvanet-test-fires/example-test-plan.md): Use this suggested test plan for a four week duration to prepare test fires and to modify the deployment of devices including changing Sensor spacing, location and fire materials.
- [Test fire preparation](https://docs.dryad.app/dryad-documentation/silvanet-test-fires/test-preparation.md): A test fire deployment can include one Border Gateway and only twenty sensors, without the need for a Mesh Gateway. Ensure you allow 14 days for sensor calibration.
- [Run test fires](https://docs.dryad.app/dryad-documentation/silvanet-test-fires/run-test-fires.md): Carefully follow the steps described in this topic to run test fires.
- [Modify fire setups](https://docs.dryad.app/dryad-documentation/silvanet-test-fires/modifying-setups.md): After completing the initial fire test, perform additional tests by modifying elements such as Sensor distance/location, fire pit location and fire test material.


---

# 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.md?ask=<question>&goal=<user_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.