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

# Input Node

## General Description

Input nodes represent water inputs into the system.&#x20;

At each time step an input node can provide as much water as set by the **Max Flow** attribute. However, unlike [Catchment nodes](https://water-strategy.gitbook.io/water-strategy/modelling-fundamentals/node-types/catchment-node) which are required to release the volume of water that is defined in their Flow attribute,  input nodes are not required to release any water unless they have a non-zero **Min Flow**.

Input nodes are often used to represent sources that are defined by yields. They are often used to represent groundwater yields.

[API Reference](https://pywr.github.io/pywr-docs/master/api/generated/pywr.nodes.Input.html).

## 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 alllocation cost per unit flow via the node</td><td>Optional</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>

## 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-input/input-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.
