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

# RiverSplit Node

## 一般描述

这个 **RiverSplit node** 是河流网络的分裂。它适用于需要将固定比例的流量分配给多条下游路径的简单案例。 [API 参考资料](https://pywr.github.io/pywr-docs/master/api/generated/pywr.domains.river.RiverSplit.html)。

## 主要属性

litLink 文档）。

<table><thead><tr><th width="180.33333333333331">姓名</th><th width="355">描述</th><th>必填项</th></tr></thead><tbody><tr><td>因素</td><td>施加额外分割的因素。额外数量_假设插槽比因子长度小一（根据 <em>pywr.nodes.</em> Multisp</td><td>可选</td></tr><tr><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 dynamically 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/riversplit-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 `build a script that syncs our docs to a CMS` 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.