General mesh packages ask for a global size. Aeronautical desks ask for a flight point. HENMESH is built for the second habit — Flight, BL Wizard, and Phase 6 workbenches all read Mach / alpha / reference length.
Mach and farfield
Compressible cases need different farfield extents and shock-band awareness than low-speed UAV cruise. Record Mach with the case name and let the Rockets or External Aero workbench seed shock zones when appropriate.
Alpha and surface clustering
High alpha loads LE and suction peaks differently. Bias surface resolution where the physics will demand it — HEN-AI mesh generation can recommend LE/TE/wake refine flags from the same flight context.
Reference length
Chord, MAC, or body length proxies drive Re and y+ targeting. Wrong length → wrong BL → wrong CFD story in HENFLOW.
Engineering takeaway
If the mesh cannot name its Mach and alpha, it is not ready for aerospace CFD review.
How HENMESH helps you act
Set flight condition first, then size. Suite packages carry those flags into HENFLOW.