> 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/jian-mo-ji-chu-zhi-shi/node-types/water-storage/storage-node.md).

# Storage Node

## 一般描述

这个 **storage node** 是可以储存水的通用节点，水有最小和最大体积限制。 [API 参考资料](https://pywr.github.io/pywr-docs/master/api/generated/pywr.nodes.Storage.html)。

## 主要属性

<table><thead><tr><th width="180.33333333333331">姓名</th><th width="316">描述</th><th>必填项</th></tr></thead><tbody><tr><td>分配罚款</td><td>通过节点的单位流量成本</td><td>可选</td></tr><tr><td>分钟_容</td><td>量存储器的最小容量。</td><td></td></tr><tr><td>默认为 0.0 可选最大值</td><td></td><td></td></tr><tr><td>_卷</td><td>存储空间的最大容量。默认为 0.0</td><td>必填项，如果未输入，则默认为 0</td></tr><tr><td>初始的_音量，初始_卷_pc</td><td>以绝对值或比例形式指定初始音量。如果<em>最大值，则两者都是必需的_卷</em> 是一个参数，因为不会在第一个时间步对该参数进行评估。如果两者都给出并且 <em>最大_体积</em>不是参数，则绝对值将被忽略</td><td>一个是必填</td></tr><tr><td>区域、级别</td><td>可选浮点数或用于定义 storage node 面积和等级的参数。这些值可通过 <em>get 获取_区域</em> 和 <em>get_level</em> 方法分别是</td><td>可选</td></tr></tbody></table>

## 例子

即将推出...


---

# 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/jian-mo-ji-chu-zhi-shi/node-types/water-storage/storage-node.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.