> 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-a-reservoir-system/additional-exercises-using-allocation-penalties-and-control-rules.md). # 使用分配罚款和控制规则来平衡来源 ## 使用分配罚款来平衡来源分配罚款可用于平衡需求来源的使用。在之前的练习中 **水库示例** 静态分配惩罚为-200。参数可用于使分配补偿根据水库的实时存储量而变化。这可以通过以下方式完成 **插值音量参数。** 一旦水库的分配补偿变为动态的，就可以将其与其他来源的分配罚款一起使用，以平衡水库的使用。 1。克隆 **'添加水库 P 和 E** 场景并命名新的场景 **'平衡来源'** 2。编辑水库节点的 “分配惩罚” 属性（“成本” 属性）并将其类型更改为 **'PYWR\_参数'**

3.在 JSON 选项卡中，粘贴以下 JSON 代码。此插值体积参数在水库已满时为其分配惩罚为 0，在水库空置时为-200 分配惩罚。当水库处于满水和空水之间时，分配罚款将在 0 和-200 之间进行插值。 ``` { “类型”：“插值音量参数”， “节点”：“示例水库”， “音量”：[ 0， 25 ]， “价值观”：[ -200， 0 ]， “interp_kwargs”：{ “种类”：“线性” }， “评论”：“交易量：Mm3，值：分配惩罚” } ``` 4。在地下水输入节点上，设置 **最大\_流** 到 0.02 并设置 **分配罚款**至 50.0。50 的正分配惩罚使得地下水节点仅在水库的分配罚款小于-**1234567890**\_\_（即水库已满 **1234567890**% 时）才使用地下水节点。这意味着当水库快满时，将不使用地下水。只有在水库充分消耗后，地下水节点才会开始向需求供水。

5。运行模型并查看 **模拟\_流** 地下水输入节点并与之比较 **GW 的需求；** 还有 **模拟\_卷** 水库节点并将两者与水库节点进行比较 **添加水库 P 和 E**。

如你所见 **平衡场景** 这是 **橙色**，使用地下水源的次数少于前一方案。如果地下水节点的许可证有限，则这是保持许可证量的一种方法。这将在另一个教程中显示。 *提示：只要勾选分配罚款 Pywr 的时间序列输出，你就能看到模拟的分配惩罚\_参数。目前，模拟罚款被称为 **模拟\_成本** 在水库上*

--- # 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/zhong-guo-ren/jiao-cheng/creating-a-reservoir-system/additional-exercises-using-allocation-penalties-and-control-rules.md?ask=&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.