Units and coordinate conventions¶
Read units from the connected API’s field schema and artifact metadata. There is no single implicit length unit across all request types. Do not infer scale from a filename or from STL alone.
Context |
Convention |
|---|---|
Design document |
Declared |
Template parameters |
Template’s published parameter units; family parameters commonly use metres |
STEP / 3MF intake |
Embedded scale is inspected; CAD dimensions are normalized for the workflow |
STL intake |
Resolve from declared units, measured bounds and engineering context |
GD Structured Meshing controls |
Lengths ending in |
GD Hex-core Meshing |
Domain, surface spacing, layer heights, ports and refinement coordinates generally use m |
Hex-core CAD tessellation/weld tolerances |
Source CAD coordinates before unit conversion; inspect field metadata |
Wake lengths in intent controls |
Body lengths where explicitly declared |
Stored simulation mesh |
Metres |
Fluxcore |
Velocity m/s; pressure Pa; temperature K; density kg/m³; dynamic viscosity Pa·s |
Rotation |
Solver |
Thermal properties |
Conductivity W/(m·K), specific heat J/(kg·K), source power W |
Viewer section position |
|
Inspect the actual bounding box before defining a domain or refinement region. CAD world axes and the viewer’s camera orientation are different concepts: rotating a view does not rotate the geometry or change inlet direction.
For a 50 mm pipe, a measured diameter of 50 in a unitless surface and 0.05 in a metre mesh can describe the same geometry. Do not apply that conversion a second time downstream.
Correcting an existing mesh interpretation¶
Fluxcore expects metre meshes. A different interpretation requires the explicit mesh_unit_conversion contract, the source checksum and confirmation. It changes interpretation for the request, not the original artifact. OpenFOAM meshes must already use metres. Never use a scale factor to conceal an unresolved geometry-unit problem.
Engineering checks¶
Compare measured dimensions with one known physical length, verify the selected fluid/solid region and retain the unit evidence in the request context. If scale remains ambiguous, resolve it before spending compute. Use degrees for documented angle controls and Kelvin for solver temperatures; do not send Celsius numbers as Kelvin.