> 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/zhong-guo-ren/jiao-cheng/creating-and-running-a-simple-model/making-changes-to-a-model/adding-a-reservoir.md). # 添加水库 请观看视频，向前一教程中构建的模型添加水库节点。为此，请创建模型的副本，如视频所示，然后在 **带抽象的** 场景 {% embed url="" %} 拖放一个 **存储** ![](/files/wdm086VmOjIzdcpeB2AV) 网络上的节点。然后删除连接的链接 **集水区** 节点到 **链接** 节点。连接 **集水区** 节点到 **存储** 节点，然后连接 **存储** 节点到 **链接** 节点。 最初设置为 **最大\_卷** 从 storage node 到 0 Mm3 和 **初始\_音量\_pc** 变为 0 然后运行模型。 然后克隆 **用\_抽象** 场景并创建一个名为的新场景 **'带有存储和抽水功能的水库'。** 在新场景中，设置 **最大\_卷** 从 storage node 到 6 Mm3 和 **初始\_音量\_个人电脑** 到 0.33。然后，水库将在 30% 已满时开始模拟。或者 **初始\_卷** 可以设置为 1.8 Mm3。要么 **初始\_卷** 要么 **初始\_音量\_pc** 需要设置。
运行模型并查看 **模拟\_水库的体积**。
水库每个旱季都会清空，每个雨季都会填满。 对比一下 **模拟\_流** 在需求节点上 **'带有存储和抽水功能的水库'** 和 **'带抽象感'** 场景\*\*。\*\*
存储减少了需求节点的赤字。但是，我们可以看到，即使有存储，有时需求节点也无法收到其 0.7 Mm3 的全部需求。 ## 运动 我们看到，在情景1下，水库每年都会清空。即使在旱季，对水库的需求必须有多低才能保持一定的储量？ --- # 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/zhong-guo-ren/jiao-cheng/creating-and-running-a-simple-model/making-changes-to-a-model/adding-a-reservoir.md?ask=&goal= ``` `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.