> 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/additional-exercises.md). # Additional Exercises 1. **Use the video below to define a monthly release rule that represents a minimum environmental flow downstream of the reservoir.** You are free to define the monthly flows that you feel are appropriate. Please use a new scenario by cloning the **'Demand with GW scenario'.** *Hint: This can be done by defining a monthly parameter on the Max Flow of the release rule.* How does the environmental flow affect the simulated volume of the reservoir? How does it affect downstream flows? Please show the plots generated for these output parameters. 2. Create a new scenario called **'Dry scenario'** by cloning the **'Demand with GW scenario'**. In this new scenario, update the catchment Flow parameter on the Catchment node to the time series found in column **'Reservoir inflow 1'** from the below link.

How does this inflow scenario impact reservoir storage? Try out different values of **Max Flow** on the Example demand node. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://water-strategy.gitbook.io/waterstrategy/tutorials/creating-a-reservoir-system/additional-exercises.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.