> 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/arby/albramj-altalymyh/creating-a-reservoir-system.md).

# نمذجة أنظمة خزانات الأحواض

ستتعلم في هذا البرنامج التعليمي كيفية إضافة بنية تحتية جديدة إلى نموذج يتضمن الخزان ومحطة المعالجة ومصدر المياه الجوفية الذي سيوفر الطلب.

يرجى ملاحظة أن هناك عقدتين في WaterStrategy و Pywr تمثلان الخزانات. الأول هو **تخزين** العقدة والثانية هي **خزان** عقدة.

كلا العقدتين تخزنان الماء. تعمل عقدة الخزان تمامًا مثل storage node، ومع ذلك فهي تحتوي على معايير مدمجة تسمح لك بتحديد *تبخر* و *ترسب* مباشرة على العقدة. للتمثيل *تبخر* و *ترسب* باستخدام storage node، يلزم وجود مستجمعات المياه وعقدة الإخراج.


---

# 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/arby/albramj-altalymyh/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.