ECSS Coordinate Transformations — Definition and Convention (space-systems/ecss/e1009-transform-def)
Use when the task is to document every coordinate transformation in a spacecraft
or system model per ECSS-E-ST-10-09C §5.4.9 — pairing a verbal description and a
rotation-matrix equation with a figure reference for each transform, enforcing a
declared row-column convention across the whole model, and checking that numerical
precision is uniform throughout.
Domain quick reference
- §5.4.9 requires that each transformation be expressed in three complementary
forms: a verbal statement naming the origin and destination frames, a
mathematical 3×3 rotation matrix written relative to the parent frame, and a
graphical illustration (figure or drawing) that makes the angular relationship
unambiguous.
- All rotation matrices in the model must follow one declared row-column
convention — typically the Direction Cosine Matrix (DCM) convention where
rows are the child-frame unit vectors expressed in the parent frame, or an
alternative active/passive sign convention. Mixing conventions within one
model is a root cause of sign errors; the convention is an attribute of the
model, not of individual transforms.
- A valid rotation matrix is orthogonal: the product of its transpose with
itself equals the identity matrix (R^T R = I) and its determinant equals +1.
A determinant of -1 signals an improper rotation (reflection); both conditions
are checked as part of the definition audit.
- Precision consistency means all transforms in the set carry the same number
of significant decimal places. An entry defined to two decimal places while
others carry fifteen-digit floating-point values introduces a hidden error
budget that the model does not account for.
- Each matrix is referenced to its parent frame — the frame from which the
rotation is measured. That parent frame must appear in the model's defined
frame set; an undefined parent frame breaks the transformation chain.
Workflow
- List every coordinate transformation in the model and confirm that each one
names a parent frame and a child frame. Reject any entry that is missing
either frame name before continuing.
- For each transform, check that a verbal description is on record and that it
references the parent frame by name. A description that says "rotation about
Z" without naming the parent frame is incomplete.
- Verify that a figure reference is on record for each transform (drawing
number, figure label, or equivalent). Flag any entry without a graphical
reference as incomplete per §5.4.9.
- Declare the model-wide row-column convention (DCM, active, or passive).
Check that every transform entry carries the same declared convention; flag
any that deviate.
- For each rotation matrix, verify orthogonality: compute R^T R and compare to
the 3×3 identity matrix within a tolerance (default 1 × 10^-6 Frobenius
norm). Also check that the determinant equals +1 within the same tolerance.
Flag non-orthogonal matrices and matrices with determinant ≠ +1 separately.
- Confirm that every parent frame named in the transform set is present in the
model's defined frame list. Flag transforms whose parent frame has no
definition on record.
- Check numerical precision consistency across all matrices: compute the
maximum number of significant decimal places used in each matrix, assign
each a precision level (low ≤ 2 dp, medium 3–6 dp, high ≥ 7 dp), and flag
any entry whose precision level differs from the set's highest level.
- Aggregate findings by transform entry; a transform is compliant when it has
a verbal description, a figure reference, an orthogonal matrix with
determinant +1, a parent frame on record, the model-wide convention, and
precision consistent with the rest of the model.
Pitfalls
- Defining the rotation matrix relative to the child frame instead of the
parent frame — §5.4.9 requires the parent-frame reference; inverting the
relation without documenting it is a common source of cascading sign errors
in the transformation chain.
- Omitting the graphical representation on the grounds that the matrix is
sufficient — the figure is not optional; it is the one artifact that makes
the angular sense unambiguous to reviewers who did not build the model.
- Leaving the row-column convention undeclared and trusting that all engineers
share the same assumption — when the convention is implicit, the first
engineer to hand the model to a new team member inherits an integration risk.
- Treating orthogonality as guaranteed because the matrix was generated by a
library — accumulated floating-point error in long transformation chains can
push R^T R away from identity; the check is a safeguard, not a formality.
- Defining some transforms at full floating-point precision and others to two
or three rounded places — the lower-precision entries dominate the total
angular error budget and the inconsistency is invisible until the model is
compared end-to-end.
Behavior contract (gate 3)
The transform-completeness, orthogonality, parent-frame, convention, and
precision-consistency logic is exercised by the gate 3 contract test:
scripts/test_e1009_transform_def.py against
scripts/e1009_transform_def_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1009_transform_def.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e1009-transform-def3description: "Use when define each coordinate transformation in a spacecraft or system4 model under ECSS-E-ST-10-09C §5.4.9: specify every transform with a verbal statement,5 a rotation-matrix equation, and a figure reference; express each matrix relative to6 its parent frame using a declared row-column convention; and verify that numerical7 precision is consistent across all entries in the model. Check orthogonality8 (R^T R = I, determinant +1) for each rotation matrix, confirm the parent frame is9 in the defined frame set, and flag any transform missing its verbal description,10 figure reference, or declared convention. Trigger: ecss, e-st-10-system-scope,11 coordinate-transformation, rotation-matrix, parent-frame, row-column-convention,12 precision-consistency, frame-definition."13license: Apache-2.014compliance: STANDARDS-REF15standards:16 - id: ecss17 reference-only: true18gated: false19domain: space-systems20pack: space-systems21compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"22metadata:23 source: https://skillmd.com/skills/ashfordeou/e1009-transform-def24 domain: space-systems25 subdomain: ecss26 tags: [ecss, e-st-10-system-scope, coordinate-transformation, rotation-matrix, parent-frame, row-column-convention, precision-consistency, frame-definition]27 version: 0.1.028 author: Aero Agent Skills29---3031# ECSS Coordinate Transformations — Definition and Convention (space-systems/ecss/e1009-transform-def)3233Use when the task is to document every coordinate transformation in a spacecraft34or system model per ECSS-E-ST-10-09C §5.4.9 — pairing a verbal description and a35rotation-matrix equation with a figure reference for each transform, enforcing a36declared row-column convention across the whole model, and checking that numerical37precision is uniform throughout.3839## Domain quick reference4041- §5.4.9 requires that each transformation be expressed in three complementary42 forms: a verbal statement naming the origin and destination frames, a43 mathematical 3×3 rotation matrix written relative to the parent frame, and a44 graphical illustration (figure or drawing) that makes the angular relationship45 unambiguous.46- All rotation matrices in the model must follow one declared row-column47 convention — typically the Direction Cosine Matrix (DCM) convention where48 rows are the child-frame unit vectors expressed in the parent frame, or an49 alternative active/passive sign convention. Mixing conventions within one50 model is a root cause of sign errors; the convention is an attribute of the51 model, not of individual transforms.52- A valid rotation matrix is orthogonal: the product of its transpose with53 itself equals the identity matrix (R^T R = I) and its determinant equals +1.54 A determinant of -1 signals an improper rotation (reflection); both conditions55 are checked as part of the definition audit.56- Precision consistency means all transforms in the set carry the same number57 of significant decimal places. An entry defined to two decimal places while58 others carry fifteen-digit floating-point values introduces a hidden error59 budget that the model does not account for.60- Each matrix is referenced to its parent frame — the frame from which the61 rotation is measured. That parent frame must appear in the model's defined62 frame set; an undefined parent frame breaks the transformation chain.6364## Workflow65661. List every coordinate transformation in the model and confirm that each one67 names a parent frame and a child frame. Reject any entry that is missing68 either frame name before continuing.692. For each transform, check that a verbal description is on record and that it70 references the parent frame by name. A description that says "rotation about71 Z" without naming the parent frame is incomplete.723. Verify that a figure reference is on record for each transform (drawing73 number, figure label, or equivalent). Flag any entry without a graphical74 reference as incomplete per §5.4.9.754. Declare the model-wide row-column convention (DCM, active, or passive).76 Check that every transform entry carries the same declared convention; flag77 any that deviate.785. For each rotation matrix, verify orthogonality: compute R^T R and compare to79 the 3×3 identity matrix within a tolerance (default 1 × 10^-6 Frobenius80 norm). Also check that the determinant equals +1 within the same tolerance.81 Flag non-orthogonal matrices and matrices with determinant ≠ +1 separately.826. Confirm that every parent frame named in the transform set is present in the83 model's defined frame list. Flag transforms whose parent frame has no84 definition on record.857. Check numerical precision consistency across all matrices: compute the86 maximum number of significant decimal places used in each matrix, assign87 each a precision level (low ≤ 2 dp, medium 3–6 dp, high ≥ 7 dp), and flag88 any entry whose precision level differs from the set's highest level.898. Aggregate findings by transform entry; a transform is compliant when it has90 a verbal description, a figure reference, an orthogonal matrix with91 determinant +1, a parent frame on record, the model-wide convention, and92 precision consistent with the rest of the model.9394## Pitfalls9596- Defining the rotation matrix relative to the child frame instead of the97 parent frame — §5.4.9 requires the parent-frame reference; inverting the98 relation without documenting it is a common source of cascading sign errors99 in the transformation chain.100- Omitting the graphical representation on the grounds that the matrix is101 sufficient — the figure is not optional; it is the one artifact that makes102 the angular sense unambiguous to reviewers who did not build the model.103- Leaving the row-column convention undeclared and trusting that all engineers104 share the same assumption — when the convention is implicit, the first105 engineer to hand the model to a new team member inherits an integration risk.106- Treating orthogonality as guaranteed because the matrix was generated by a107 library — accumulated floating-point error in long transformation chains can108 push R^T R away from identity; the check is a safeguard, not a formality.109- Defining some transforms at full floating-point precision and others to two110 or three rounded places — the lower-precision entries dominate the total111 angular error budget and the inconsistency is invisible until the model is112 compared end-to-end.113114## Behavior contract (gate 3)115116The transform-completeness, orthogonality, parent-frame, convention, and117precision-consistency logic is exercised by the gate 3 contract test:118scripts/test_e1009_transform_def.py against119scripts/e1009_transform_def_logic.py (stdlib unittest, offline). Run:120python3 scripts/test_e1009_transform_def.py121122## Compliance123124- ECSS standards are freely downloadable (ESA); cite the source and125 paraphrase per standards-map.yaml.126- compliance: STANDARDS-REF, gated: false.