> 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-and-running-a-simple-model/creating-and-running-a-model/creating-a-new-scenario.md). # Creating a New Scenario Please watch the video for additional detail. {% embed url="" %} ### Create new scenario and compare with Baseline Scenarios allow users to explore and evaluate different conditions or management strategies within the water system model. 1\. To create a new scenario, click on the **Clone a scenario** icon. (To 'clone' is to 'make a copy of').

choose **Baseline** as the scenario to clone, add a name to your scenario, in this case 'With abstraction', and click **Clone**.

You will see the new scenario is automatically made active.

At the moment, the new scenario is an exact clone of the **baseline** scenario. In this scenario, we will assign a demand to the demand node. Change the max\_flow of the demand output node to 5.0 Mm3/day

**Run** the new scenario and then view the **simulated\_flow** of the demand node.

Now, the amount of water supplied to the demand node is no longer 0. The demand node attempts to abstract 5.0 Mm3/day of water. However, when there is not enough water in the river the full 5.0 Mm3/day cannot be abstracted. Lets view the simulated\_flow of the river output node.

Lets compare the river outflow in both scenarios. Add the baseline scenario to the view by selecting it in the menu and then pressing the Play ![](/files/YAQTE1s985CDqQto75LZ)button.

We can see that the less water reaches the river outlet in the **With abstraction** scenario and sometimes there is no water flowing into the river outlet. --- # 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-and-running-a-simple-model/creating-and-running-a-model/creating-a-new-scenario.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.