Overview
Simulation results are only as useful as your ability to extract, interpret, and communicate them. Scoping results to specific regions, comparing across load cases, computing safety margins, exporting data, and writing reports can be just as time-consuming as the setup itself. Nexus can scope, extract, compare, and report results directly from solver output. Describe what you want to know and Nexus will find it — whether it’s a single peak stress value or a structured engineering report ready for design review.What Nexus can help with
- Results extraction — Query maximum, minimum, and average values for any result quantity (stress, strain, deformation, temperature, pressure, velocity) across the whole model or scoped to specific regions or named selections.
- Safety factor and margin — Calculate safety factors against yield, ultimate, or fatigue limits for any body, face, or region.
- Load case comparison — Compare results across multiple load cases or design variants and summarise the critical case.
- Path and probe results — Extract values along a defined path or at specific probe points for plotting and export.
- Data export — Export result arrays to CSV, Excel, or text format for further analysis or plotting outside the solver.
- Report generation — Generate a structured results summary — model setup, mesh statistics, key results, and conclusions — formatted for engineering review.
Example prompts
Extract key results
Extract key results
Compare load cases
Compare load cases
Extract path results
Extract path results
Generate an engineering report
Generate an engineering report
Thermal results
Thermal results
Tips for postprocessing prompts
- Name the result quantity precisely — “Von Mises stress”, “principal stress S1”, “total deformation”, “equivalent plastic strain”, “heat flux” — the exact name avoids ambiguity in multi-physics models.
- Scope to named selections — “Scope to the weld fillet named selection” is more reliable and repeatable than “near the weld”.
- Ask for units — Nexus will confirm the unit system in use alongside each value.
- Tailor reports to the audience — “For a design review with a non-simulation audience” will produce a different level of technical detail than “for the simulation team”. Both are valid — just say which.
- Combine with comparison — Ask Nexus to compare current results to a previous run or a target threshold in the same prompt: “Is the safety factor above 2 everywhere? If not, list the regions where it falls below.”