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

# RiverSplitWithGauge Node

## General Description

The **RiverSplitWithGauge node** is a split in the river network with a minimum residual flow (MRF). As per *RiverSplit* but by default creates another route in the underlying object to model a MRF. This route is such that the MRF is not part of forced ratios. The intent of this object is to model the case where a proportion of flow can be abstracted above the MRF (e.g. 90% of flow above MRF). [API Reference](https://pywr.github.io/pywr-docs/master/api/generated/pywr.domains.river.RiverSplitWithGauge.html).

## Primary Attributes

<table><thead><tr><th width="152.33333333333331">Name</th><th width="397">Description</th><th>Required</th></tr></thead><tbody><tr><td>mrf</td><td>The minimum residual flow (MRF) at the gauge</td><td>Required</td></tr><tr><td>mrf_cost</td><td>The cost of the route via the MRF</td><td>Required</td></tr><tr><td>cost</td><td>The cost of the other (unconstrained) route</td><td>Required</td></tr><tr><td>factors</td><td>The factors to force on the additional splits. Number of extra_slot is assumed to be one less than the length of factors (as per <em>MultiSplitLink</em> documentation)</td><td>Required</td></tr><tr><td>slot_names</td><td>The identifiers to refer to the slots when connect from this Node. Length must be one more than the number of extra slots required</td><td>Required</td></tr></tbody></table>

## Examples

coming soon...


---

# 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-transport/riversplitwithgauge-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.