> 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/creating-a-reservoir-system/adding-a-source-representing-groundwater.md). # Adding a Source Representing Groundwater In this section an [Input ](https://water-strategy.gitbook.io/water-strategy/modelling-fundamentals/node-types/input-node)node representing a groundwater source will be added to the reservoir system. The demand node will receive water from both groundwater and the reservoir. Groundwater is modeled as a yield. ## Create a new scenario Clone the **'Demand with treatment losses'** scenario and call the new one **'Demand with GW'** ## **Add an input node** Add an **Input** node below the demand node as shown below. Rename the node to 'Groundwater well'

Add groundwater input

**###Notice**: to maintain the same behaivior in each of the previous scenarios, the Max Fow of the input node must be set to 0 in each scenario. This can be done by clicking on the edit button on the Max Flow attribute of the Input node.

Edit the max flow

and then by setting a Max Flow of 0 Mm3/day in the text box:

Set max flow to 0

and before saving the changes, select all scenarios so the 0 flow applies to all scenarios:

Select all scenarios

and then click on **save**. ## Groundwater inflow setting Next, we need to set the yield of the groundwater in this scenario. Set the **Max Flow** of the node to be **0.02 Mm3/day** instead of 0**.** This will represent the maximum possible supply of the input node at each time step.

Groundwater input

Then, run this scenario.

Run the scenario

## View and compare the results Compare the **simulated\_volume** of the reservoir to that of the **'Demand with treatment losses'** scenario.

Select the scenario to compare

Compare the reservoir volume

## Exercises and questions --- # 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/creating-a-reservoir-system/adding-a-source-representing-groundwater.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.