> 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/francais/bases-de-la-modelisation/node-types/water-storage/storage-node.md).

# Storage Node

## Description générale

Le **storage node** est un nœud général capable de stocker de l'eau, qui a des restrictions de volume minimum et maximum. [API Référence](https://pywr.github.io/pywr-docs/master/api/generated/pywr.nodes.Storage.html).

## Attributs principaux

pc le

<table><thead><tr><th width="180.33333333333331">Nom</th><th width="316">Descriptif</th><th>Nécessaire</th></tr></thead><tbody><tr><td>pénalité d'allocation</td><td>Le coût par unité de flux via le nœud</td><td>Facultatif</td></tr><tr><td>minimum_volume</td><td>Le volume minimum de l'espace de stockage.</td><td>La valeur par défaut est 0.0 Max optionnel</td></tr><tr><td>_volume</td><td>Le volume maximum de l'espace de stockage. La valeur par défaut est 0.0</td><td>Obligatoire, la valeur par défaut est 0 si elle n'est pas saisie</td></tr><tr><td>initiale_volume initial_volume_</td><td>Spécifiez le volume initial en termes absolus ou proportionnels. Les deux sont requis si <em>max_volume</em> est un paramètre car il ne sera pas évalué lors de la première étape. Si les deux sont administrés et <em>max_</em>volume n'est pas un paramètre, alors la valeur absolue est ignorée L'</td><td>une est la zone requise</td></tr><tr><td>, le niveau,</td><td>flottant facultatif ou le paramètre définissant la surface et le niveau du storage node. Ces valeurs sont accessibles via le <em>get_surface</em> et <em>obtenir_niveau</em> méthodes respectivement</td><td>Facultatif</td></tr></tbody></table>

## Exemples

à venir...


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://water-strategy.gitbook.io/waterstrategy/francais/bases-de-la-modelisation/node-types/water-storage/storage-node.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 `build a script that syncs our docs to a CMS` 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.