# First experiment

## Start with compilation

From your supplied checkout, validate and run the included keyword-spotting example:

```bash
uv run helx validate config examples/at110/kws_vela_only.yaml
uv run helx run --config examples/at110/kws_vela_only.yaml
```

This example downloads its model and compiles it with Vela. It needs network access, but no FVP or target hardware. Validation checks the configuration before the experiment runs.

The command prints result tables and a `Bundle:` path. Use that path to inspect the result:

```bash
uv run helx show results/kws_vela_only
uv run helx validate bundle results/kws_vela_only
```

A compilation result is not a simulated or measured device latency. Check which stages ran before comparing outputs.

## Add simulation

After completing `helx setup`, run the supplied full-pipeline example:

```bash
uv run helx run --config examples/at110/getting_started.yaml
```

It compiles a model, builds the selected runtime and executes it on the configured FVP. See [Simulation and runtimes](https://ambiqai.github.io/helia-estimator/guides/simulation/) for the choices and requirements.

## Recognize the completed run

The result includes tables followed by the bundle location. This **abbreviated illustrative output** shows the shape, not a recorded run:

```text
$ helx run --config examples/at110/kws_vela_only.yaml
...
Run: kws_vela_only
Model                   <resolved model>
...
Memory
...
Vela
...
Bundle: /path/to/helia-estimator/results/kws_vela_only
```

Use the path printed by your run with `helx show`. A full FVP run also includes counter and energy sections; [see representative results](https://ambiqai.github.io/helia-estimator/getting-started/results/#what-the-terminal-shows) with clearly labelled dummy metrics.