Diagnostics — where the optimisation is
The most useful thing NEURAX produces, and how to read it.
The metrics tell you what a design costs. The diagnostics tell you what to do about it. They appear under the analysis in the Architecture tab.
Reading a row by its colour#
| Colour | Label | What it means |
|---|---|---|
| Red | Blocking | The design cannot be compiled as drawn. The block responsible is named. |
| Amber | Warning | It compiles, but something is not part of the model or not modelled. |
| Grey | Note | Context. Nothing to act on. |
Rows are ordered by that list, so what blocks you is always at the top. A summary line above them says what was found. Each row names its block when it has one and, after the arrow, what to do about it.
Issues#
The Issues block lists problems found in the design itself: a block the compiler does not model, a missing or invalid parameter, shapes that do not connect, a block connected to nothing, a design with no input. The inspector shows a count and jumps you there.
Page 30 of 33. This guide is in English for now. It is the same guide that is built into the NEURAX desktop app (the ? button, or F1). Found a mistake? Tell us.