> 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/espanol/tutoriales/creating-a-reservoir-system.md).

# Modelización de sistemas de embalses de

En este tutorial, aprenderá cómo agregar nueva infraestructura a un modelo que incluye un embalse, una planta de tratamiento y una fuente de agua subterránea que abastecerá una demanda.

Tenga en cuenta que hay dos nodos en WaterStrategy y Pywr que representan depósitos. El primero es un **almacenamiento** nodo y el segundo es un **embalse** nodo.

Ambos nodos almacenan agua. El nodo de depósito funciona igual que un storage node, sin embargo, tiene parámetros integrados que permiten definir *evaporación* y *precipitación* directamente en el nodo. Para representar *evaporación* y *precipitación* con un storage node, se requieren un nodo de captación y de salida.


---

# 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://water-strategy.gitbook.io/waterstrategy/espanol/tutoriales/creating-a-reservoir-system.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.