Output and monitoring controls¶
Choose outputs before submitting the simulation so the saved evidence can answer the engineering question.
Control |
Purpose |
|---|---|
|
Publish final solution fields; keep true for post-processing |
|
Intermediate iteration/physical-step output cadence; 0 disables intermediates, not final export |
|
History reporting interval within the allowed schema range |
|
Exact wall selections, directions, reference area/length/speed and history policy |
|
User’s assessment standard for force stability and residual behaviour |
Force modes include end_only, interval, history, both, every_step and off. Discover exact constraints in ForcesConfig. Choose the patches deliberately: a domain wall or fixed-velocity wall can alter the meaning of the integrated force.
Use a positive explicit reference area for a prescribed coefficient convention, or explicitly select and disclose the projected-area estimate. Record drag/lift directions, moment reference dimensions and operating velocity. Coefficients computed with different references are not directly comparable.
Saved volume VTU/CGNS fields support interior sections and velocity streamlines. Boundary-only VTP data supports surface inspection but cannot supply an interior flow field. Do not infer missing fields from a screenshot or create a streamline from surface-only data.
After completion, assess_convergence evaluates saved evidence and view_convergence_history prepares its chart. These operations do not run Fluxcore again. See results.