Translation
We currently have two geometry pipelines that must stay aligned:
- Active/scoring path: reads cell/cube positions and stores them.
- Passive geometry path: builds CAD/mesh-based volumes.
Because these are separate, the same translation must currently be defined twice (once per path). It’s a duplication requirement to keep both pipelines consistent.
Rotation
- Rotation is not duplicated the same way: it is applied only in one path.
- Result: passive geometry rotates, active/scoring geometry does not → misalignment between scoring and passive volumes.
Expected
- Translation and rotation must be applied consistently to both pipelines.
- Ideally: a single transform definition feeds both pipelines (single source of truth).
Translation
We currently have two geometry pipelines that must stay aligned:
Because these are separate, the same translation must currently be defined twice (once per path). It’s a duplication requirement to keep both pipelines consistent.
Rotation
Expected