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

# Loss Link Node

## General description

A **loss link** allows for the definition of a fixed proportional loss of flow that goes through this node.  Loss links are often used to represent **potable water treatment works** which incur some process losses.

The Max and Min flow attributes that are defined are applied to the net output after losses. 

The node itself records the net output in its flow attribute (which would be used by any attached recorders).

## Primary Attributes

<table><thead><tr><th width="181.33333333333331">Name</th><th width="342">Description</th><th>Required</th></tr></thead><tbody><tr><td>Allocation Penalty</td><td>The cost per unit flow via the node</td><td>Optional</td></tr><tr><td>Loss factor</td><td>loss_factor : float or Parameter. The proportion of flow that is lost through this node. Must be greater than or equal to zero. This value is either a proportion of gross or net flow depending on the value of <code>loss_factor_type</code>.</td><td>Optional, defaults to 0</td></tr><tr><td>Loss Factor Type</td><td>Either "gross" or "net" (default) to specify whether the loss factor is applied as a proportion of gross or net flow respectively.</td><td>Optional, defaults to "net" </td></tr><tr><td>Max Flow</td><td>The maximum flow constraint on the node</td><td>Optional</td></tr><tr><td>Min Flow</td><td>The minimum flow constraint on the node</td><td>Optional</td></tr></tbody></table>

## Example

<figure><img src="/files/IL0lAaXMNJBoQrViSnrb" alt=""><figcaption></figcaption></figure>

In this example 10% of the gross amount of water flowing into the node is lost.


---

# 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/modeling-basics/node-types/water-output/loss-link-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.