ECSS System Engineering — Reference Frames (space-systems/ecss/e1009-frame)
Use when the task is to define or validate a spacecraft coordinate reference
frame under ECSS-E-ST-10C §5.4.1 — specifying origin, axis orientations,
handedness, time-dependence classification, naming, and frame-chain traceability.
Domain quick reference
- A reference frame is uniquely described by (a) its origin — a physically
identifiable point such as the spacecraft centre of mass or a sensor focal
point — and (b) three mutually orthogonal unit vectors that form a
right-handed coordinate triad (x, y, z such that z = x × y).
- Frames are categorized by their time-dependence:
- Inertial — origin and axes are fixed relative to the celestial sphere;
must carry an epoch (e.g. J2000.0); used as the root of the frame tree.
- Body-fixed — axes rotate with the spacecraft structure; time-varying
(changes with attitude); traced to an inertial root via the attitude
rotation sequence.
- Orbit-referenced — axes aligned with orbital position/velocity vectors
(e.g. radial–transverse–normal); time-varying and mission-phase-dependent.
- Planet-fixed — axes rotate with a planetary body (e.g. ECEF for Earth);
time-varying relative to inertial space.
- Topocentric — origin at a ground station or landing site; time-varying
due to planetary rotation.
- Naming: ECSS §5.4.1 requires names to be unambiguous, uppercase
alphanumeric with underscores, starting with a letter, and ≤ 64 characters
(e.g.
SC_BODY, ECI_J2000, RTN_ORB).
- Every non-root frame must reference a parent frame; the chain from any
leaf frame to the inertial root must be traceable without gaps.
Workflow
- Identify the origin: Record a physically identifiable anchor point
(e.g. spacecraft centre of mass, instrument aperture centre, ground-station
reference mark). Reject any frame whose origin is vague or
unverifiable from documentation.
- Assign axis directions: Specify three unit vectors. Each must have
magnitude 1.0 (within numerical tolerance). The pair (x, y) must be
orthogonal (x · y = 0). Derive z = x × y and confirm the result matches
the declared z axis; flag any deviation above tolerance.
- Categorize by time-dependence: Assign the frame type from the
enumeration above (inertial, body-fixed, orbit-referenced, planet-fixed,
topocentric). Inertial frames must carry an explicit epoch. Body-fixed and
orbit-referenced frames must be flagged as time-varying. Inertial frames
must be flagged as time-independent.
- Apply naming convention: Validate the frame name against the ECSS
convention — uppercase letters and digits, underscores allowed,
must begin with a letter, max 64 characters.
- Establish parent linkage: For every non-root frame, record the name
of its parent frame. Confirm the parent name appears in the defined
frame set. Flag any frame whose parent is undefined.
- Produce the frame record: Emit a complete frame definition record
with origin description, axis unit vectors, frame type, time-dependence
flag, epoch (if inertial), parent frame (if non-root), and name. A frame
record is complete only when all fields above are present and validated.
Pitfalls
- Using non-unit direction vectors (e.g. direction cosines not normalized)
leads to incorrect rotation matrix computation downstream; always normalize
and re-verify magnitude before recording.
- Omitting the epoch from an inertial frame makes the frame ambiguous across
precession epochs (e.g. J2000.0 vs. J2050.0 differ by non-negligible
amounts for high-precision pointing); treat a missing epoch as an error,
not a default.
- Marking a body-fixed or orbit-referenced frame as time-independent
conflates its instantaneous snapshot with the frame definition itself and
silently breaks any downstream attitude propagation that reads the
time-dependence flag.
- Leaving a non-root frame without a declared parent frame severs the
traceability chain; transformation from that frame to any other frame
becomes undefined and must be flagged as unresolved.
- Using lowercase or mixed-case frame names in a mixed-tool chain causes
silent mismatches in attitude software that performs case-sensitive name
lookups; enforce the uppercase convention at ingestion.
Behavior contract (gate 3)
The origin-description, axis orthogonality/handedness, time-dependence
consistency, naming convention, and frame-chain traceability logic is
exercised by the gate 3 contract test:
scripts/test_e1009_frame.py against scripts/e1009_frame_logic.py
(stdlib unittest, offline). Run:
python3 scripts/test_e1009_frame.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-frame3description: "Use when define and validate a spacecraft reference frame under ECSS-E-ST-10C §5.4.1: establish the frame origin and three orthogonal right-handed axes, label each axis with a physical direction reference, determine whether the frame is inertial or time-varying (body-fixed, orbit-referenced, or planet-fixed), supply an epoch for inertial frames, confirm the name follows the ECSS uppercase-alphanumeric convention, and verify that any child frame traces an unbroken chain back to a root inertial frame. Trigger: ecss, e-st-10-system-scope, reference-frame, coordinate-frame, axes, right-handed, inertial, body-fixed, orbit-referenced, frame-naming."4license: Apache-2.05compliance: STANDARDS-REF6standards:7 - id: ecss8 reference-only: true9gated: false10domain: space-systems11pack: space-systems12compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"13metadata:14 source: https://skillmd.com/skills/ashfordeou/e1009-frame15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-system-scope, reference-frame, coordinate-frame, axes, right-handed, inertial, body-fixed]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS System Engineering — Reference Frames (space-systems/ecss/e1009-frame)2324Use when the task is to define or validate a spacecraft coordinate reference25frame under ECSS-E-ST-10C §5.4.1 — specifying origin, axis orientations,26handedness, time-dependence classification, naming, and frame-chain traceability.2728## Domain quick reference2930- A reference frame is uniquely described by (a) its origin — a physically31 identifiable point such as the spacecraft centre of mass or a sensor focal32 point — and (b) three mutually orthogonal unit vectors that form a33 right-handed coordinate triad (x, y, z such that z = x × y).34- Frames are categorized by their time-dependence:35 - **Inertial** — origin and axes are fixed relative to the celestial sphere;36 must carry an epoch (e.g. J2000.0); used as the root of the frame tree.37 - **Body-fixed** — axes rotate with the spacecraft structure; time-varying38 (changes with attitude); traced to an inertial root via the attitude39 rotation sequence.40 - **Orbit-referenced** — axes aligned with orbital position/velocity vectors41 (e.g. radial–transverse–normal); time-varying and mission-phase-dependent.42 - **Planet-fixed** — axes rotate with a planetary body (e.g. ECEF for Earth);43 time-varying relative to inertial space.44 - **Topocentric** — origin at a ground station or landing site; time-varying45 due to planetary rotation.46- Naming: ECSS §5.4.1 requires names to be unambiguous, uppercase47 alphanumeric with underscores, starting with a letter, and ≤ 64 characters48 (e.g. `SC_BODY`, `ECI_J2000`, `RTN_ORB`).49- Every non-root frame must reference a parent frame; the chain from any50 leaf frame to the inertial root must be traceable without gaps.5152## Workflow53541. **Identify the origin**: Record a physically identifiable anchor point55 (e.g. spacecraft centre of mass, instrument aperture centre, ground-station56 reference mark). Reject any frame whose origin is vague or57 unverifiable from documentation.582. **Assign axis directions**: Specify three unit vectors. Each must have59 magnitude 1.0 (within numerical tolerance). The pair (x, y) must be60 orthogonal (x · y = 0). Derive z = x × y and confirm the result matches61 the declared z axis; flag any deviation above tolerance.623. **Categorize by time-dependence**: Assign the frame type from the63 enumeration above (inertial, body-fixed, orbit-referenced, planet-fixed,64 topocentric). Inertial frames must carry an explicit epoch. Body-fixed and65 orbit-referenced frames must be flagged as time-varying. Inertial frames66 must be flagged as time-independent.674. **Apply naming convention**: Validate the frame name against the ECSS68 convention — uppercase letters and digits, underscores allowed,69 must begin with a letter, max 64 characters.705. **Establish parent linkage**: For every non-root frame, record the name71 of its parent frame. Confirm the parent name appears in the defined72 frame set. Flag any frame whose parent is undefined.736. **Produce the frame record**: Emit a complete frame definition record74 with origin description, axis unit vectors, frame type, time-dependence75 flag, epoch (if inertial), parent frame (if non-root), and name. A frame76 record is complete only when all fields above are present and validated.7778## Pitfalls7980- Using non-unit direction vectors (e.g. direction cosines not normalized)81 leads to incorrect rotation matrix computation downstream; always normalize82 and re-verify magnitude before recording.83- Omitting the epoch from an inertial frame makes the frame ambiguous across84 precession epochs (e.g. J2000.0 vs. J2050.0 differ by non-negligible85 amounts for high-precision pointing); treat a missing epoch as an error,86 not a default.87- Marking a body-fixed or orbit-referenced frame as time-independent88 conflates its instantaneous snapshot with the frame definition itself and89 silently breaks any downstream attitude propagation that reads the90 time-dependence flag.91- Leaving a non-root frame without a declared parent frame severs the92 traceability chain; transformation from that frame to any other frame93 becomes undefined and must be flagged as unresolved.94- Using lowercase or mixed-case frame names in a mixed-tool chain causes95 silent mismatches in attitude software that performs case-sensitive name96 lookups; enforce the uppercase convention at ingestion.9798## Behavior contract (gate 3)99100The origin-description, axis orthogonality/handedness, time-dependence101consistency, naming convention, and frame-chain traceability logic is102exercised by the gate 3 contract test:103scripts/test_e1009_frame.py against scripts/e1009_frame_logic.py104(stdlib unittest, offline). Run:105python3 scripts/test_e1009_frame.py106107## Compliance108109- ECSS standards are freely downloadable (ESA); cite the source and110 paraphrase per standards-map.yaml.111- compliance: STANDARDS-REF, gated: false.