> 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/establish-agent-feedback/about-simulation.md).

# Simulation Overview

A simulation is the part of the AMESA agent ecosystem that models the real world. It tells the agent system *what happens when it takes an action*, whether based on historical data, physics, business logic, or other dynamics. The simulator enables agents to learn how to make decisions safely, repeatedly, and at scale.

AMESA supports three types of simulations, giving you flexibility depending on your use case and available infrastructure.

***

### 🧠 Simulation Types

#### 1. Data-Driven Simulations (No-Code Option)

Use historical operational data to automatically generate a simulation in the AMESA UI.

* No coding required, just upload a properly formatted CSV
* Uses AMESA’s Training-as-a-Service
* Ideal for industrial and logistics workflows where historical data reflects real-world constraints

***

#### 2. Containerized Simulations Using AMESA’s Training Service

Bring your simulation, built in any language or framework, and connect it to AMESA via Docker.

* You define the simulation logic
* AMESA manages the training cluster and runtime
* Ideal for teams with existing physics-based or black-box models

This option provides you with complete flexibility while still leveraging AMESA’s infrastructure and tools.

***

#### 3. Containerized Simulations Using Your Own Azure Training Cluster

For enterprises managing their cloud infrastructure, you can run your simulation and training in your own Azure tenant.

* Simulation runs in a Docker container, just like above
* AMESA orchestrates training via your own Azure compute resources
* Gives you control over scaling, security, and cost management

***

### Explore AMESA’s Example Simulators

To understand how a simulator works inside the AMESA platform, you can explore our public Python [simulators hosted on Docker Hub](https://hub.docker.com/u/composabl). These simple environments are perfect for:

* Demos and POCs
* Self-guided learning
* Team education and experimentation

Use the CLI to Get Started

To list available simulators:

```bash
composabl sim list
```

To connect to one of the simulators:

```bash
composabl sim run
```

## Simulation Help

### Simulation Help

If you already have a simulator, the documentation will guide you through the process of connecting it to AMESA, whether you’re using our managed training or your infrastructure.

If you don’t yet have a simulator, you can:

* Start with a data-driven simulation
* Explore our example simulations
* Or work with a AMESA partner to develop one based on your system

[Contact us](mailto:info@composabl.com) for more information about finding a simulation partner.


---

# 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/establish-agent-feedback/about-simulation.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.
