When something looks wrong

The usual causes, in the order to check them.

The parameter count is far too low#

Almost always the layer stack. Check the layer body is connected back to the layer_stack block and that num_layers is right. See "Repeated layers".

A block seems to be ignored#

Check it is connected at both ends. A block with no path from the input is not part of the model, and the Issues block will say so.

The analysis will not run#

Read the message — it names the cause. The usual ones are no machine selected (open the machine button in the toolbar), an empty canvas, or a missing Input or Output block. If a shape cannot be resolved, the diagnostic names the block.

Two analyses of the same design differ#

They should not. Something changed in the parameters, the hyperparameters or the machine between the runs: open each from the toolbar to see which setting moved.

A file will not open#

Open takes JSON and TOML design files. Published-model configurations go through Import. A file written by a newer NEURAX says so rather than opening partially.

Save says it cannot write in place#

The file may have moved or become read-only since you opened it. NEURAX falls back to Save As so you can choose a new location.

An error mentions a defect in NEURAX#

Then it is not your design. Save the design (Ctrl+S) and attach the JSON or TOML design file to a bug report — it reproduces what failed.

Page 32 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.