Check a simulation result

Check why a simulation stopped and which outputs are usable before passing its result into further analysis.

Confirm what completed

Inspect the result manifest before reading field values:

jq '{status, deployment, successful_files, omitted_files}' \
  results/baseline/simulation_manifest.json

Confirm that the expected history and VTU files are present. max_iterations_reached, canceled, and diverged can all produce downloadable diagnostic results even though the simulation did not converge.

Inspect non-converged outcomes

Vanellus only reports residual_converged or monitor_converged after the corresponding configured criteria have passed; you do not need to verify that decision manually.

Use iteration_info.csv when the simulation stopped without convergence:

• for max_iterations_reached or canceled, check how much the recorded quantities were still changing; and
• for diverged, use the histories only to diagnose where the instability began.

Also review mass and energy balance monitors when they were included in the request. A convergence status describes why iteration stopped; it does not assess whether a monitored value is acceptable for the application.

Check the fields

Inspect the original cell data in fluid.vtu and solid.vtu. Check for:

• non-finite values;
• temperatures exactly 500 °C above or below the reference temperature, which indicate that the solver safeguard was reached; and
• values read from regions where that field is only a placeholder.

Flow fields in solid.vtu and temperatures in insulating components are placeholders. A dry-run archive contains geometry and placeholder fields only.

See also

• Analyze results with Python extracts histories and cell fields.
• Inspect simulation results in ParaView gives the spatial inspection workflow.
• Simulation status and result files explains artifact availability.
• How simulations stop explains every terminal status.
• Monitors and derived quantities explains balances and monitored fields.