> 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/scenarios.md). # Scenarios Scenarios in WaterStrategy allow users to simulate and explore various water management strategies by adjusting different elements of a model. They provide a framework for understanding how changes in inputs, assumptions, or data might influence outcomes under different conditions. WaterStrategy offers two types of scenarios to address various needs in water management modeling: 1. **WaterStrategy Scenarios:** This type is used when users need to adjust specific behaviors, parameters, or data at a localized or smaller scale. These scenarios are ideal for cases where only certain elements of the model need to be tweaked without altering the entire dataset. It allows for targeted modifications, making it easier to test the effects of individual changes within the system. 2. **Pywr-scenarios:** This scenario type is designed to handle more complex cases, particularly those involving uncertainty. It specializes in combining data across multiple scales, allowing for a comprehensive assessment of different variables. This approach is especially useful when working with uncertain inputs or when modeling future conditions, as it enables you to explore how different combinations of data and assumptions may impact the outcomes. --- # 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/modeling-basics/scenarios.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.