> 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-output/loss-link-node.md).

# 损失 Link Node

## 一般描述

一个 **丢失链接** 允许定义流经此节点的固定比例流量损失。损失链接通常用来表示 **饮用水处理工程** 这会造成一些过程损失。

定义的最大和最小流量属性应用于损失后的净输出。

节点本身在其 flow 属性中记录净输出（任何连接的记录器都将使用该属性）。

## 主要属性

<table><thead><tr><th width="181.33333333333331">姓名</th><th width="342">描述</th><th>必填项</th></tr></thead><tbody><tr><td>分配罚款</td><td>通过节点的单位流量成本</td><td>可选</td></tr><tr><td>损失系数</td><td>损失_因子：浮点数或参数。流经此节点的流量比例。必须大于或等于零。该值要么是总流量的比例，要么是净流量的比例，具体取决于<code>损失的价值_因子类型</code>。</td><td>可选，默认为 0</td></tr><tr><td>损失因子类型</td><td>选择 “总流量” 或 “净流量”（默认），指定损失系数是分别作为总流量还是净流量的比例适用。</td><td>可选，默认为 “net”</td></tr><tr><td>最大流量</td><td>节点上的最大流量约束</td><td>可选</td></tr><tr><td>最小流量</td><td>节点上的最小流量约束</td><td>可选</td></tr></tbody></table>

## 示例

<figure><img src="https://2456626420-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FroBiEJ09sszXPUfSv5uk%2Fuploads%2Fgit-blob-fc182b8aa043189e95c262a8fdd0c268b93fdd59%2Fimage%20(62).png?alt=media" alt=""><figcaption></figcaption></figure>

在此示例中，10流入节点的总水量中有百分比流失。


---

# 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-output/loss-link-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.