> 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-transport/riversplitwithgauge-node.md).

# RiverSplitWithGauge Node

## 一般描述

这个 **RiverSplitWithGauge node** 是河网中残留流量 (MRF) 最小的分裂。按照 *Riversplit* 但默认情况下，在底层对象中创建另一条路径来建模 MRF。这条路径使得MRF不是强制比率的一部分。该对象的目的是模拟可以在MRF上方抽取一定比例的流量（例如，900\_\_% 的流量高于MRF）的情况。 [API 参考资料](https://pywr.github.io/pywr-docs/master/api/generated/pywr.domains.river.RiverSplitWithGauge.html)。

## 主要属性

成本成本本

<table><thead><tr><th width="152.33333333333331">姓名</th><th width="397">描述</th><th>必填项</th><th></th></tr></thead><tbody><tr><td>mrf</td><td>仪表处的最小残留流量 (MRF)</td><td>必填项</td><td></td></tr><tr><td>mrf_</td><td></td><td></td><td></td></tr><tr><td>通过 MRF 的路径</td><td></td><td></td><td></td></tr><tr><td>成本</td><td>所需</td><td>其他（不受约束的）路径的成</td><td>所需</td></tr><tr><td>因素</td><td>施加额外分割的因素。额外数量_假定槽位比因子长度小一（按照 <em>MultSplitLink</em> 文档）</td><td>必填项</td><td></td></tr><tr><td>插槽名称</td><td>从该节点连接时引用插槽的标识符。长度必须比所需的额外插槽数多一个</td><td>必填项</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 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/jian-mo-ji-chu-zhi-shi/node-types/water-transport/riversplitwithgauge-node.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.