> 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/reading-h5-dataframe-for-pywr-scenarios.md).

# Reading h5 DataFrame for pywr-scenarios

Go to the catchment node **Days Weir,** click Edit **Flow**

<figure><img src="/files/LYvSzzqqJHzfkYjnvHGK" alt="" width="563"><figcaption></figcaption></figure>

A new window will pop up, select **PYWR\_PARAMETER** and click **Save**

<figure><img src="/files/Zv9znCZtA6ReMU47JmQR" alt=""><figcaption></figcaption></figure>

Paste the following configuration and **Save**

```json
{
	"key": "Days Weir",
	"scenario": "Climate Change",
	"type": "DataFrameParameter",
	"url": "Thames_inflows_pywrScenarios.h5",
	"index_col": "timestep",
	"parse_dates": true
}
```

It should look like the following image

<figure><img src="/files/QWnGKnYC4eVYi0aaKBLh" alt="" width="563"><figcaption></figcaption></figure>

Repeat the procedure for catchment **Lower\_Thames** using the following configuration

```json
{
	"key": "Lower Thames",
	"scenario": "Climate Change",
	"type": "DataFrameParameter",
	"url": "Thames_inflows_pywrScenarios.h5",
	"index_col": "timestep",
	"parse_dates": true
}
```

## Results

As the total number of simulations is four, this is because we are using a single **pywr-scenarios** setup for **Climate Change**, which contains 4 scenarios. Each of these scenarios will run separately, and the result of all 4 simulations will be displayed each output result, as shown below

<figure><img src="/files/rJtOToc3eytzJLsxCsvM" alt=""><figcaption><p>simulated_flow (Lower_Thames)</p></figcaption></figure>

<figure><img src="/files/043H76LPNGMynmT0ivNd" alt=""><figcaption><p>simulated_volume (New Reservoir)</p></figcaption></figure>


---

# 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/reading-h5-dataframe-for-pywr-scenarios.md?ask=<question>&goal=<endgoal>
```

`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.