Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Simulation status and result files

A submitted simulation runs asynchronously. The submission response returns a simulation ID, which is then used to check progress, stop the run, and download its results.

Submission and warnings

Vanellus rejects requests that cannot be validated. An accepted request can still return warnings about its setup. They do not prevent the run, but should be reviewed before relying on the result. Currently, all warnings relate to planned deprecations.

Status and result availability

While a simulation is running, its status document reports the current runtime, iteration, and mesh information. After it stops, two fields answer different questions:

  • status records why the run stopped, such as residual_converged, max_iterations_reached, canceled, or diverged.
  • completed records whether a result bundle was persisted and can be downloaded.

completed: true does not mean that the simulation converged or that its result is physically correct. For example, maximum-iteration, canceled, and diverged runs retain results for inspection.

Stopping a run also affects result availability:

  • Canceling stops at an iteration boundary and preserves partial fields and histories.
  • Killing stops immediately and does not preserve a result bundle.

A dry_run stops after meshing. Its geometry and placeholder fields are useful for checking the setup, but they are not a physical solution. See How simulations stop for every terminal status and its result behavior.

Result files

Every downloaded archive includes simulation_manifest.json, which records the simulation ID, terminal status, files included, and any requested files that could not be included.

Depending on the run and download selection, the archive can also contain:

  • fluid.vtu, with cell fields in the fluid region;
  • solid.vtu, with fields in component cells, including reference-temperature placeholders for insulating cells;
  • iteration_info.csv, with one row per SIMPLE iteration and columns for residuals, monitors, CTM junction temperatures, timings, and linear-solver diagnostics; and
  • request.json, containing the server-normalized simulation request when it is available. Re-running a simulation using this request should produce the same result (apart from a small amount of numerical noise).

The VTU arrays are cell-centered, and some arrays in solid cells are placeholders rather than solved fields. See VTU fields and domains before using those values quantitatively.

Some files are unavailable when the corresponding region or output was not produced. A selective download only changes which available files are packaged; the manifest always describes the resulting archive.

Use the files together:

  • VTU files show where values occur in the model.
  • Residuals show how the equation solves progressed.
  • Monitor and junction-temperature histories track the quantities configured in the request.
  • The terminal status explains why the run stopped.

See also