> For the complete documentation index, see [llms.txt](https://water-strategy.gitbook.io/waterstrategy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://water-strategy.gitbook.io/waterstrategy/tutorials/pywr-scenarios-reading-external-dataframe-and-adding-custom-rules/running-pywr-scenarios.md).
# Running pywr-scenarios
## Activate pywr-scenarios
On the left panel, click on *View Network Data* icon
This will open the right panel. In the section **Inputs**, type "*scenarios"* and click on *Add an Input* icon
A window will be displayed, type "*scenarios"*, select the **scenarios** attribute and click **Save** as shown in the following image
A new window will pop up, select **PYWR\_SCENARIOS** and click **Save**
As the H5 file contains 4 dataframes per key, this necessitates the **size**=four (4). In this case, the pywr-scenario will be named **Climate Change**, and no **Ensemble** names will be used to differentiate between them.
When a pywr-scenario is finally created, you will be able to see the following window:
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://water-strategy.gitbook.io/waterstrategy/tutorials/pywr-scenarios-reading-external-dataframe-and-adding-custom-rules/running-pywr-scenarios.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.