> 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/identify-agent-skills/activity-clusters-in-amesa.md).

# Activity Clusters in AMESA

Activity clusters are generated as part of simulation creation. You can see the clusters as one of the steps in creating your simulation.&#x20;

You can also view the clusters later:

1. Go to the Simulators page from the main dashboard
2. Click on your simulator
3. Click on the Activity Clusters tab
4. Choose whether to view the clusters as a list of sensor variable ranges or as a graph.

<figure><img src="https://2216884851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6X1hFdU8qyyv3sgW7kkX%2Fuploads%2F13etB1efDtnMskId0Vob%2FScreenshot%202026-07-15%20at%204.19.21%E2%80%AFPM.png?alt=media&amp;token=d3c16038-4468-4ed9-8e1f-5ae2b13102a6" alt=""><figcaption></figcaption></figure>

Activity cluster graphs show a multi-dimensional space represented in two dimensions. For this reason, the X and Y axis are not meaningful in the visualizations.

Use the list view to capture the variable ranges to use in populating the [Scenarios](https://docs.amesa.com/build-multi-agent-systems/configure-scenarios.md) page when you are setting up your use case.

<figure><img src="https://2216884851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6X1hFdU8qyyv3sgW7kkX%2Fuploads%2FOz8O1K4rEUReM9VBRo01%2FScreenshot%202026-07-15%20at%204.22.08%E2%80%AFPM.png?alt=media&amp;token=42bbe91a-6fed-4154-b963-32412305e2a1" alt=""><figcaption></figcaption></figure>


---

# 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://docs.amesa.com/identify-agent-skills/activity-clusters-in-amesa.md?ask=<question>&goal=<user_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.
