Check units before rendering
A visually plausible scene can still be wrong by orders of magnitude.
Research note · November 14, 2026Research question
How should imported geometry and physical parameters declare their units?
Method
- Choose a known reference dimension and record the source asset’s length unit. Convert the asset once at a documented boundary and preserve the original scale metadata.
- Check mass, time, angle and force quantities independently. Do not infer a complete physical unit system merely because the geometry appears correctly sized.
- Construct a fixture with a deliberate millimeter-to-meter error. Compare bounding dimensions, mass-related parameters and resulting motion before reviewing the visual appearance.
Records to retain
- Source and target units
- Conversion factors
- Reference dimensions
- Physical parameter unit declarations
Source basis
glTF uses meters for linear distances, while ROS REP 103 specifies SI conventions and radians for angles. An importer that mixes conventions can produce a convincing render and an invalid physical model simultaneously.
Interpretation & limits
Rendering correctness is not simulation validation. Some formats omit physical properties entirely; choosing a unit does not supply missing mass or inertia. No conversion accuracy results are reported.
Next experiments
- Add unit-mismatch fixtures to the import review.
- Require explicit confirmation when source units are unknown.
References
Technical reference
Implementation details supporting this note, drawn directly from the maintained documentation. These are technical references, not additional papers or new experimental results. Expand a topic to inspect its method, fields and limits.