# runtime_records

The runtime versions this heliaPROFILER records, and whether each is qualified for a precision on a board and clock.

Every name on this page is imported from `helia_profiler`.

**API tier:** `experimental`

Generated from the `src/helia_profiler` tree `fe269596788d6ab1604cf433559e96b5f48c1d13`.

[Machine-readable model](https://ambiqai.github.io/helia-profiler/reference/api/helia_profiler/runtime_records.json)

What heliaPROFILER says about one runtime version, precision and target.

**API tier:** `experimental`

`dataclass`

The repository and commit a runtime version is built from.

**API tier:** `experimental`

`dataclass`

A board class and clock the runtime is qualified on, and why.

**API tier:** `experimental`

`dataclass`

One runtime version: its source, supported precisions and qualified targets.

**API tier:** `experimental`

`dataclass`

The answer for one runtime version, precision and target, with the record it came from.

**API tier:** `experimental`

`cached`

Every runtime record shipped with this heliaPROFILER, by name then version.

**API tier:** `experimental`

Whether ``name`` at ``version`` is qualified for ``precision`` on ``board`` at ``clock``.

``board`` and ``clock`` must be a built-in board and one of its CPU clock
profiles (records qualify built-in boards only, so a ``target.custom_boards``
name is refused too), and ``precision`` one of :data:`PRECISIONS`; anything
else raises ``ValueError``, the precision first.

A version without a record, or a precision its record does not declare,
is unsupported here, even when an engine's own version check would build
it: this heliaPROFILER makes no claim about it.

**API tier:** `experimental`

---

Machine-readable: [`runtime_records.json`](https://ambiqai.github.io/helia-profiler/reference/api/helia_profiler/runtime_records.json) · [`runtime_records.md`](https://ambiqai.github.io/helia-profiler/reference/api/helia_profiler/runtime_records.md), complete and lossless.