> 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/tutorials/using-allocation-penalties/exercise-1c-minimum-flow-properties.md).
# Exercise 1c Minimum Flow Properties
Note: Create a new network called Exercise 1d and setup the timestep before running the network as described in Exercise 1a.
### **Create the network**
Navigate to the left panel and click on **Build** to open the Nodes list.
Drag and drop to the workspace Map:
\- 1 input node 
\- 2 output nodes 
\- 2 link nodes 
Click on **edge**  to activate “link mode”, connect the nodes and fill their attributes as shown in the picture below:
Click again on **edge**  to deactivate “link mode”.
On the left panel click on **Run a Model** .
A new window will pop-up, click on **Submit**
Visualize the **simulated\_flow** results
### **Explanation**
The water distribution network is designed to ensure a mandatory input node supply of 20 Mm³/day. This configuration enforces a minimum and maximum flow of 20 Mm³/day, making it the total daily flow available for the entire network.
**Link1:** High Priority Allocation
* **Priority:** Link1 has the highest priority due to its most negative allocation penalty value.
* **Max Flow Configuration:** The network aims to allocate 8 Mm³/day to Link1, given the available flow.
* **Allocation:** With 20 Mm³/day available, 8 Mm³/day is allocated to Link1, leaving a remaining 12 Mm³/day for subsequent nodes.
**Output2:** Second Priority Allocation
* **Priority:** Output2 is the second priority node based on the allocation penalty value.
* **Max Flow Configuration:** The network targets an allocation of 8 Mm³/day to Output2, if available.
* **Allocation:** With 12 Mm³/day remaining after Link1's allocation, 8 Mm³/day is allocated to Output2, leaving a remaining 4 Mm³/day.
**Link2:** Remaining Flow Route
* **Max Flow Configuration**: Link2 does not have a maximum flow constraint.
* **Flow Dependency:** The flow through Link2 depends on downstream constraints rather than a specific max flow value.
**Output1:** Final Allocation Node
* **Configuration:** Output1 lacks both a maximum flow constraint and an allocation penalty value.
* **Flow Allocation:** Output1 through Link2 receives the remaining 4 Mm³/day flow in the network.
* **Flow Distribution:**
8 Mm³/day is received from Link1.
4 Mm³/day is received from Link2.
**Total Flow:** Output1 ultimately withdraws 12 Mm³/day.
---
# 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/tutorials/using-allocation-penalties/exercise-1c-minimum-flow-properties.md?ask=&goal=
```
`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.