> 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/italiano/tutorial/pywr-scenarios-reading-external-dataframe-and-adding-custom-rules/reading-h5-dataframe-for-pywr-scenarios.md).

# Lettura di DataFrame h5 per scenari pywr

Vai al nodo del bacino **Giorni Weir,** fai clic su Modifica **Flusso**

<figure><img src="https://2382307583-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBg8BcxZRxPP2vxAwzrhK%2Fuploads%2Fgit-blob-122f78f6caa50d6525b64a7edbb7532b0c31aa7c%2Fimage%20(42).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

Si aprirà una nuova finestra, seleziona **PYWR\_PARAMETRO** e fai clic **Salva**

<figure><img src="https://2382307583-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBg8BcxZRxPP2vxAwzrhK%2Fuploads%2Fgit-blob-2d3f81de6e093c76b9f7a27004f7da6634059481%2Fimage%20(43).png?alt=media" alt=""><figcaption></figcaption></figure>

Incolla la seguente configurazione e **Salva**

```json
{
	«key»: «Days Weir»,
	«scenario»: «Cambiamenti climatici»,
	«type»: «DataFrameParameter»,
	«url»: «Tamigi_afflussi_Scenari PyWR S.H5",
	«index_col»: «passo temporale»,
	«parse_dates»: vero
}
```

Dovrebbe assomigliare alla seguente immagine

<figure><img src="https://2382307583-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBg8BcxZRxPP2vxAwzrhK%2Fuploads%2Fgit-blob-a16ac6d1504585edb44dc44adc4946dfc1d9207f%2Fimage%20(44).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

Ripetere la procedura per la captazione **Inferiore\_Thames** utilizzando la seguente configurazione

```json
{
	«key»: «Lower Thames»,
	«scenario»: «Cambiamenti climatici»,
	«type»: «DataFrameParameter»,
	«url»: «Tamigi_afflussi_Scenari PyWR S.H5",
	«index_col»: «passo temporale»,
	«parse_dates»: vero
}
```

## Risultati

Poiché il numero totale di simulazioni è quattro, ciò è dovuto al fatto che stiamo usando una sola **scenari pywr** configurazione per **Cambiamenti climatici**, che contiene 4 scenari. Ciascuno di questi scenari verrà eseguito separatamente e il risultato di tutte e 4 le simulazioni verrà visualizzato in ogni risultato di output, come mostrato di seguito

<figure><img src="https://2382307583-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBg8BcxZRxPP2vxAwzrhK%2Fuploads%2Fgit-blob-7b985a4169f74776d6a0f395dce2058d3f7ca16e%2Fimage%20(45).png?alt=media" alt=""><figcaption><p>simulato_flusso (inferiore)_Tamigi)</p></figcaption></figure>

<figure><img src="https://2382307583-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBg8BcxZRxPP2vxAwzrhK%2Fuploads%2Fgit-blob-e1c64630c4a4be54dae8d96da6d1a9b2b83600eb%2Fimage%20(48).png?alt=media" alt=""><figcaption><p>simulated_volume (Nuovo serbatoio)</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/italiano/tutorial/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.
