# Next steps

You have a result bundle and a configuration file. The rest of the site is
organised by task, and this page maps the questions people ask after a
first profile onto the page that answers each one.

## Prerequisites

[First profile](https://ambiqai.github.io/helia-profiler/getting-started/first-profile/) and [Configure a run](https://ambiqai.github.io/helia-profiler/getting-started/configure-a-run/)
done.

## Steps

### By what you want to do

| I want to | Go to |
|---|---|
| Understand every file hpx wrote and the units in each column | [Output files](https://ambiqai.github.io/helia-profiler/guide/output/) |
| Compare two runs and know when a comparison is not fair | [Analysis and comparison](https://ambiqai.github.io/helia-profiler/guide/analysis-comparison/) |
| See per-layer cost on the model graph | [Model Explorer overlays](https://ambiqai.github.io/helia-profiler/guide/model-explorer/) |
| Try another engine: heliaAOT, TFLM or ExecuTorch | [Engines](https://ambiqai.github.io/helia-profiler/guide/engines/) |
| Build with `armclang` or ATfE instead of GCC | [Toolchains](https://ambiqai.github.io/helia-profiler/guide/toolchains/) |
| Move the arena or the weights to a different memory | [Memory placement](https://ambiqai.github.io/helia-profiler/guide/memory/) |
| Capture more counters, or counters from the memory and MVE domains | [PMU counters](https://ambiqai.github.io/helia-profiler/guide/pmu-counters/) |
| Measure power with a Joulescope or an INA228 | [Power measurement](https://ambiqai.github.io/helia-profiler/guide/power/) |
| Capture over USB CDC or UART instead of RTT | [Capture transports](https://ambiqai.github.io/helia-profiler/guide/transports/) |
| Run hpx from Python instead of the shell | [Python API](https://ambiqai.github.io/helia-profiler/reference/api/) |
| Script a batch of runs or wire hpx into CI | [Batch runs from YAML](https://ambiqai.github.io/helia-profiler/examples/batch-runs/) |
| Understand a failed run or an issue code | [Issue codes](https://ambiqai.github.io/helia-profiler/reference/issue-codes/) |

### By section

- [User guide](https://ambiqai.github.io/helia-profiler/guide/): Task pages in four groups: set up a run, measure, read results, and the concepts behind the pipeline.
- [Examples](https://ambiqai.github.io/helia-profiler/examples/): Recipes for engines, toolchains, boards, power capture and workflows. Each page identifies its configuration and validation status; some show illustrative output rather than a captured result.
- [Reference](https://ambiqai.github.io/helia-profiler/reference/): The command line, every configuration key, the issue codes and the Python API, all generated from the source, plus the compatibility baseline and the firmware wire protocol.

### For agents

Every page on this site has a Markdown rendition at its route plus
`index.md`, the whole site is in `llms-full.txt`, and the generated
reference ships as JSON: `reference/api/reference.json`,
`reference/cli/cli.json`, `reference/configuration/schema.json` and
`reference/issue-codes/issues.json`. Start from
[`llms.txt`](https://ambiqai.github.io/helia-profiler/llms.txt) for the index.

## Expected output

Nothing runs on this page. If none of the rows above matches your question,
the troubleshooting section of [First profile](https://ambiqai.github.io/helia-profiler/getting-started/first-profile/#troubleshooting-the-first-run) and the
[issue codes](https://ambiqai.github.io/helia-profiler/reference/issue-codes/) are the two places a failed run
sends you.

## What next

Whichever row you picked. The section landing pages carry the same map in
more detail.