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

# MultiSplitLink Node

## 一般描述

这个 **MultiSplitLink node** 是的扩展 [PieceWiseLink](https://app.gitbook.com/o/tUkZkKm5QY0V6IeofRg4/s/ODCd8VK2OOl9jOdp5KFf/~/changes/91/modelling-fundamentals/node-types/water-transport/piecewiselink-node) 其中包括其他可供连接的插槽。

从概念上讲，这个节点在内部看起来像下面这样，

```
         / -->-- X0 -->-- \
一个 -->-- Xo -->-- X1 -->-- Xi -->-- C
         \ -->-- X2 -->-- /
                 |
                 Bo -->-- Bi --> D
```

每个额外的插槽都会在 PieceWiseLink（即上面的 X2）和该类中的节点（即 Bo 和 Bi）中添加一个额外的子链接。

最后，提供了一种机制来（可选）固定最后一个非分割子链接（即 X1）和每个额外子链接（即 X2）之间的比率。该机制使用 *聚合节点* 内部。 [API 参考资料](https://pywr.github.io/pywr-docs/master/api/generated/pywr.nodes.MultiSplitLink.html)。

注意：用户在使用因子机制时必须小心。因子使用最后一个非分割子链接（即 X1 但不是 X0）。如果此连接受最大或最小流量约束，或者如果它存在另一个不受约束的链接（即 X0 不受约束），则整个节点的比率可能无法按预期强制执行。

## 主要属性

flow

<table><thead><tr><th width="180.33333333333331">姓名</th><th width="318">描述</th><th>必填项</th></tr></thead><tbody><tr><td>分配罚款</td><td>通过节点的单位流量成本</td><td>可选</td></tr><tr><td>最大_</td><td>节点上的最大流量约束</td><td>可选额外的</td></tr><tr><td>_插槽</td><td>要提供的额外插槽（和子链接）的数量。必须大于零。</td><td>可选</td></tr><tr><td>时段_n</td><td>ames 连接其他节点时用来指代插槽的名称。长度必须比额外数目多一_老虎机。第一个项目是指 PieceWiseLink 连接，每个额外插槽都有以下物品。</td><td>可选</td></tr><tr><td>因素</td><td>如果给定，则长度必须等于比 extra_slots 的数量多一个。每个项目是通过附加子链接的总流量所占的比例。如果特定子链接不需要系数，则使用 <em>无</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-transport/multisplitlink-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.