> 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/evaluate-performance/analyze-data.md).

# Analyze Data

## Benchmark Testing and Data Generation

After training a multi-agent system in AMESA, the system automatically runs a series of standardized tests to evaluate its performance. This benchmarking process:

1. Places the system in controlled testing environments
2. Records detailed metrics at each step of operation
3. Aggregates results to provide comprehensive performance statistics

The output of this testing process is compiled into a structured benchmark.json file, which contains rich performance data that can be analyzed to assess effectiveness, identify improvement opportunities, and compare different design approaches. This file is a performance record and a valuable analytics resource for optimizing your agentic systems.

## Downloading Benchmark Artifacts

To download benchmark data for further analysis:

1. Navigate to the "Training Sessions" page
2. Click the artifacts dropdown in the top right page of a trained system
3. Select "Benchmark"
4. The benchmark.json file will be saved to your local machine

<figure><img src="https://2216884851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6X1hFdU8qyyv3sgW7kkX%2Fuploads%2FwfDmet0gumnedjdi0CSk%2FScreenshot%202026-07-15%20at%202.06.56%E2%80%AFPM.png?alt=media&amp;token=7300a4de-8d9f-4992-949e-5949021c2775" alt=""><figcaption></figcaption></figure>

## Understanding the Benchmark.json File

The benchmark.json file contains structured data about the performance of a trained agent system. Here's how to interpret this file:

### File Structure

```
{
  "skill-name": {
    "scenario-0": {
      "scenario_data": { ... },
      "episode-0": [ ... ],
      "aggregate": { ... }
    }
  }
}
```

### Key Components

**Scenario Data**: Contains reference values for the scenario:

```
"scenario_data": {
  "sensor_one": {"data": 8.57, "type": "is_equal"}, 
  "sensor_two": {"data": 373, "type": "is_equal"}
}
```

**Episode Data**: Array of state-action pairs showing how the agent performed in each step:

```
[
  {
    "state": "{'sensor_one': array([311.2639], dtype=float32), ...}",
    "action": "[-1.253192]",
    "teacher_reward": 1.0,
    "teacher_success": false,
    "teacher_terminal": null
  },
  ...
]
```

**Aggregate Statistics**: Summary statistics for the entire benchmark:

```
"aggregate": {
  "mean": { ... },
  "medians": { ... },
  "std_dev": { ... },
  "max": { ... },
  "min": { ... }
}
```


---

# 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/evaluate-performance/analyze-data.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.
