> For the complete documentation index, see [llms.txt](https://docs.amesa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amesa.com/tutorials/material-fusion/generate-activity-clusters-and-scenarios.md).
# Generate Activity Clusters and Scenarios
After creating a simulation, it's time to generate activity clusters and scenarios, unique operating regions where the agents need to perform differently to succeed.
## Activity Clusters
As part of simulation creation, AMESA automatically generates activity clusters. This process produces three things: a visual display of the clusters, labels for each cluster, and sensor ranges for each cluster.
## Scenarios
The sensor ranges for each cluster are used to create scenarios. Scenarios are a way to divide the state space into separate regions for training, so that agents can practice only in the conditions they need to control.
This file contains all the sensor ranges for each scenario for the Material Fusion example.
{% file src="/files/0MQUiPN8R2rSd2mgaZQH" %}
Before you set up scenarios,you must first [set up a use case](/build-multi-agent-systems/create-a-project.md).
Then set up scenarios by entering the sensor range information on the [scenarios page](/build-multi-agent-systems/configure-scenarios.md) in the Agent Orchestration Studio.
---
# 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://docs.amesa.com/tutorials/material-fusion/generate-activity-clusters-and-scenarios.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.