Read a result with its provenance
Provide the source revision, solver and version, material and boundary data, mesh, achieved step or time, and output definitions. A plot without its units, component, or deformation scale can be misleading.Review a structural result package
Separate three conclusions
A missing check should remain visible. Incomplete or unconverged results can help diagnose a problem but should not be presented as an accepted design result.
Compare like with like
Use the same physical inputs, measurement locations, field components, and averaging conventions. Explain any change in the model or numerical method. Keep color ranges consistent when comparing contour plots.Make a revision comparison table
Open and retain the deliverables
Adam opens supported.sim.json exports in its simulation viewer. Ask Adam to generate that export from the solved data when conversion is available, then open it from the task’s files. A native solver database does not automatically become a viewer file. Keep the raw solver outputs and native study as well.
The deformation control changes the display only; reported values remain unscaled. Controls depend on what the file contains. Setup text and comparison metrics describe the export; opening it does not independently verify the underlying solve.
For each plot, identify the field, units, region, step or time, and display scale. The simulation viewer displays an exported surface. For an interior slice, a time history, or a numerical probe, ask Adam to produce a separate plot or table from the source result data.
If the file shows This simulation result could not be opened, ask Adam to check and regenerate the viewer export while preserving the solver files. Renaming an arbitrary JSON file to
.sim.json does not convert it.
Use Troubleshooting for suspect results, or Repeat engineering work to preserve an accepted study brief.