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

# PiecewiseLink Node

## 一般描述

这个 **PiecewiseLink node** 是 Node 的扩展，表示非线性 [链接](/waterstrategy/zhong-guo-ren/jian-mo-ji-chu-zhi-shi/node-types/water-transport/link-node.md) 使用逐件成本函数。该对象旨在模拟提供特定流速有好处，但超过固定限值会发生变化（或零）成本的情况。 [API 参考资料](https://pywr.github.io/pywr-docs/master/api/generated/pywr.nodes.PiecewiseLink.html)。

这个节点是使用复合节点结构实现的，如下所示：

```
        | 单独的域名         |
输出-> 子链接 0-> 子输出-> 输入
       -> 子链接 1 ---^
       ...             |
       -> 子链接 n ---|
```

这意味着路由不会直接穿过此节点，因为中间有单独的域。取而代之的是，为每个子链接和输出/输入节点的连接创建了几条新路由。路径中断的原因是为了避免在同一条路径中存在多个 PieceWiseLinks 时路径数量几何增加。

## 主要属性

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>min_流</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 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/piecewiselink-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.