Review mesh quality and acceptance¶
Assess the delivered mesh against both geometric quality and the intended physics. The saved quality report and simulation mesh are the evidence; a surface preview alone cannot establish volume-cell quality.
Review cell count, positive cell volumes, orthogonal quality, nonorthogonality, skewness, aspect ratios, size ratios and region summaries when returned. Interpret distributions and locations, not only a single minimum or maximum. High aspect ratio can be intentional in a wall layer, but its orientation and surrounding quality still matter.
Inspect narrow passages, sharp curvature, boundary-layer transitions, local-refinement transitions and physical interfaces. Confirm all required boundary and material names. A quality pass does not establish mesh independence.
Count targets and review¶
A verified mesh that misses its permitted target-count range can enter awaiting_decision. Compute has finished; stop polling as if it were still running. Read the actual count, requested range, quality evidence and result.review.
Use review_job to accept or discard that saved candidate under the user’s decision or explicitly delegated authority. Acceptance enables downstream use without remeshing; neither decision starts another mesh. A pending candidate cannot be used for simulation.
A new attempt requires a reviewed change and a new intended submission, including reviewed_job_id where required. Retain the old result. Do not quietly relax quality constraints or start repeated attempts to chase a target count.
Establish adequate resolution¶
Compare at least the relevant engineering outputs across a deliberate resolution sequence. Keep physical settings and output definitions consistent. Record achieved y+, force or pressure-drop changes, thermal quantities and convergence evidence as appropriate. The acceptable difference is an engineering requirement to state, not a universal percentage.