> 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/example-test-plan.md).

# Fire test plan

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.

{% hint style="warning" %}
**Avoid contact with Sensors after deployment**

AFTER SENSORS HAVE BEEN DEPLOYED AND CALIBRATED, DO NOT INTERACT WITH THE SENSORS AS THIS WILL CAUSE ERRORS WITH SENSOR VALUES AND COULD ALSO RESET THE SENSOR CALIBRATION.
{% endhint %}

The following shows a suggested test plan for a four-week duration.

Week one:

| Days |   |   |
| ---- | - | - |
|      |   |   |
|      |   |   |
|      |   |   |

<table><thead><tr><th width="88">Week</th><th width="68">Day</th><th>Test type</th><th>Calibration period</th><th>Material</th><th>Sensor spacing</th></tr></thead><tbody><tr><td>1 and 2</td><td>1 </td><td>Initialize</td><td>14 days</td><td>Calibration</td><td>n.a.</td></tr><tr><td>3</td><td>1</td><td>Preparation</td><td>1 day</td><td>Douglas Fir</td><td>5 m</td></tr><tr><td>3</td><td>2</td><td>Change material</td><td>1 day</td><td>Creosote railroad ties</td><td>5 m</td></tr><tr><td>3</td><td>3</td><td>Change material</td><td>1 day</td><td>Pressure-treated poles</td><td>5 m</td></tr><tr><td>3</td><td>4</td><td>Change distance</td><td>1 day</td><td>Douglas Fir</td><td>10 m</td></tr><tr><td>3</td><td>4</td><td>Change distance</td><td>5 hr</td><td>Douglas Fir</td><td>15 m</td></tr><tr><td>3</td><td>5</td><td>Change distance</td><td>1 day</td><td>Douglas Fir</td><td>80 m</td></tr><tr><td>3</td><td>5</td><td>Change distance</td><td>1 day</td><td>Douglas Fir</td><td>100 m</td></tr><tr><td>4</td><td>6 - 10</td><td>Change location</td><td>5 days</td><td>Calibration</td><td>n.a</td></tr><tr><td>5</td><td>11</td><td>Initial</td><td>1 days</td><td>Douglas Fir</td><td>5 m</td></tr><tr><td>5</td><td>12</td><td>Material</td><td>1 day</td><td>Larch</td><td>5 m</td></tr><tr><td>5</td><td>13</td><td>Material</td><td>1 day</td><td>Maple</td><td>5 m</td></tr><tr><td>5</td><td>14</td><td>Distance</td><td>1 day</td><td>Douglas Fir</td><td>10 m</td></tr><tr><td>5</td><td>14</td><td>Distance</td><td>1 day</td><td>Douglas Fir</td><td>15 m</td></tr><tr><td>5</td><td>15</td><td>Distance</td><td>1 day</td><td>Douglas Fir</td><td>80 m</td></tr><tr><td>5</td><td>15</td><td>Distance</td><td>1 day</td><td>Douglas Fir</td><td>100 m</td></tr></tbody></table>


---

# 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/example-test-plan.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.