E1004 Annex J Debris/Meteoroid Flux Model Reference Data
Overview
ECSS-E-ST-10-04C Annex J is an informative annex on the meteoroid and
orbital-debris flux models a mission environment analysis draws on: it
does not mandate a single model, it flags that every published model
(natural meteoroid or catalogued orbital debris) carries an
applicability envelope (altitude range, epoch range, particle-diameter
range) and a stated uncertainty band, and that an analysis is only
traceable if it names the model used and stays inside that envelope.
This is a reference-data leaf: it does not compute an impact risk, it
categorizes candidate flux models against a case's parameters and
supplies the lookup, applicability, and uncertainty-bounding logic a
mission engineer runs before trusting a model's output.
Two model families must be categorized and handled separately:
- Meteoroid models (e.g. a Grün-class interplanetary flux model)
— natural particles, effectively time-invariant over a mission
lifetime, applicable across a wide altitude range because the
population is not orbit-bound.
- Orbital-debris models (e.g. ORDEM-class or MASTER-class
engineering models) — anthropogenic catalogued and sub-catalogued
objects, whose flux depends on altitude band and drifts with epoch
as the debris population grows and decays, so a debris model is only
valid for the altitude band and epoch window it was built for.
This leaf implements:
- A reference table of illustrative flux models with their family,
applicability envelope (altitude, epoch, particle diameter), and
uncertainty factor.
applicability_gaps / is_model_applicable — check a case's
parameters against one model's envelope and report which dimensions
(if any) fall outside it.
applicable_models / recommend_model — list every model whose
envelope covers a case, and pick the tightest (lowest-uncertainty)
one among them.
uncertainty_bounds / cross_check_reported_flux — compute the
low/high bound around a nominal or reported flux value using the
model's uncertainty factor, and flag a reported flux that cites a
model outside its own applicability envelope.
When to invoke this skill
- Choosing which meteoroid or orbital-debris model to run (or cite) for
a shielding, penetration-risk, or micrometeoroid-and-orbital-debris
(MMOD) budget analysis at a given orbit and epoch.
- Reviewing a vendor- or tool-supplied flux number and checking whether
the model it claims to come from actually covers the case's altitude,
epoch, and particle-size range before the number is used downstream.
- Propagating a flux-model uncertainty band into a risk or probability-
of-no-penetration calculation instead of treating a model's nominal
output as exact.
Not for the MMOD penetration/risk calculation itself, hypervelocity-
impact damage equations, or the trapped-radiation environment
(e1004-trapped-leo and siblings) — this leaf only selects and bounds
the input flux model.
Data provenance and fidelity notice
The model registry in scripts/e1004_ref_debris_logic.py
(grun_interplanetary, ordem, master) is an illustrative
reference set built from widely published, generic descriptions of
the class of meteoroid and orbital-debris engineering models used in
astrodynamics practice (a Grün-class interplanetary meteoroid model,
NASA's ORDEM-class LEO debris engineering model, ESA's MASTER-class
LEO-through-GEO debris model) — it is not a transcription of the
standard's Annex J tables, and the envelope bounds and uncertainty
factors are representative order-of-magnitude values, not the current
released version's exact figures. For mission-grade, traceable
analysis, replace the registry entries with the specific model
version, applicability envelope, and uncertainty figures published by
the model's current release notes, keeping the same function interface
(applicability_gaps, uncertainty_bounds, recommend_model). The
applicability and uncertainty-bounding logic is model-registry-
independent and does not need to change when the entries are updated.
Steps
- Categorize the object family.
classify_object_family(object_family)
accepts "meteoroid" or "debris"; raises ValueError for any
other value.
- Check one model's applicability.
applicability_gaps(model_name, object_family, altitude_km, epoch_year, diameter_m) returns a dict
of the dimensions (family, altitude_km, epoch_year,
diameter_m) that fall outside that model's envelope for the case
(empty dict means fully applicable). is_model_applicable(gaps)
reduces that to a boolean. Raises ValueError for an unknown
model_name.
- List every applicable model.
applicable_models(object_family, altitude_km, epoch_year, diameter_m) returns the sorted names of
every registered model with no gaps for the case; raises
ValueError for an unrecognized object_family.
- Recommend a model.
recommend_model(object_family, altitude_km, epoch_year, diameter_m) returns the applicable model with the
lowest uncertainty factor; raises ValueError when no registered
model covers the case (the case needs a model outside this
registry, not a silent default).
- Bound a flux value.
uncertainty_bounds(model_name, nominal_flux)
returns (low, high) using the model's uncertainty factor
(nominal_flux / factor, nominal_flux * factor); raises
ValueError for a negative flux or an unknown model.
- Cross-check a reported flux/model pairing.
cross_check_reported_flux(model_name, object_family, altitude_km, epoch_year, diameter_m, reported_flux) returns
{"issue": "reported_flux_outside_model_envelope", "model": ..., "gaps": {...}} when the pairing is out of envelope, or {"issue": None, "model": ..., "uncertainty_low": ..., "uncertainty_high": ...}
when it is applicable. Do not accept a reported flux number until
issue is None.
Pitfalls
- Using a debris model's flux number outside its epoch window (the
catalogued population changes over time) and treating it as still
current --
applicability_gaps flags an out-of-range epoch_year
for exactly this reason.
- Applying a LEO-scoped debris model's flux at GEO, or vice versa, just
because it was the model on hand -- check
altitude_km applicability
before reuse; a model with no envelope coverage for a case is not the
best available answer, it is inapplicable.
- Reporting a model's nominal flux as a single number in a risk
calculation without carrying its uncertainty band -- every registered
model has a nontrivial
uncertainty_factor; downstream margin
calculations must use uncertainty_bounds, not just the nominal
value.
- Picking the first applicable model found instead of the tightest one
--
recommend_model selects the lowest-uncertainty applicable model;
a wider-envelope, higher-uncertainty model should only be used when
no tighter model covers the case.
Behavior contract (gate 3)
The model-applicability, model-selection, and uncertainty-bounding
logic is exercised by the gate 3 contract test:
scripts/test_e1004_ref_debris.py against
scripts/e1004_ref_debris_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1004_ref_debris.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e1004-ref-debris3description: "Use when selecting a meteoroid or orbital-debris flux model for a4 spacecraft environment analysis per ECSS-E-ST-10-04C Annex J: determine5 whether a candidate model (natural meteoroid or catalogued orbital debris)6 is applicable to a case's altitude, epoch, and particle-diameter range,7 compute the model's stated uncertainty band around a nominal flux value,8 and validate a reported flux/model pairing against the model's9 applicability envelope so an out-of-envelope claim is flagged rather than10 accepted at face value. Trigger: ecss, e-st-10-04c, meteoroid flux, orbital11 debris flux, flux model applicability, model uncertainty factor, ORDEM,12 MASTER, Annex J."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/e1004-ref-debris24 domain: space-systems25 subdomain: ecss26 tags: [ecss, e-st-10-04c, debris, meteoroid, flux-model, uncertainty, annex-j, orbital-debris]27 version: 0.1.028 author: Aero Agent Skills29---3031# E1004 Annex J Debris/Meteoroid Flux Model Reference Data3233## Overview3435ECSS-E-ST-10-04C Annex J is an informative annex on the meteoroid and36orbital-debris flux models a mission environment analysis draws on: it37does not mandate a single model, it flags that every published model38(natural meteoroid or catalogued orbital debris) carries an39applicability envelope (altitude range, epoch range, particle-diameter40range) and a stated uncertainty band, and that an analysis is only41traceable if it names the model used and stays inside that envelope.42This is a reference-data leaf: it does not compute an impact risk, it43categorizes candidate flux models against a case's parameters and44supplies the lookup, applicability, and uncertainty-bounding logic a45mission engineer runs before trusting a model's output.4647Two model families must be categorized and handled separately:48491. **Meteoroid models** (e.g. a Grün-class interplanetary flux model)50 — natural particles, effectively time-invariant over a mission51 lifetime, applicable across a wide altitude range because the52 population is not orbit-bound.532. **Orbital-debris models** (e.g. ORDEM-class or MASTER-class54 engineering models) — anthropogenic catalogued and sub-catalogued55 objects, whose flux depends on altitude band and drifts with epoch56 as the debris population grows and decays, so a debris model is only57 valid for the altitude band and epoch window it was built for.5859This leaf implements:601. A reference table of illustrative flux models with their family,61 applicability envelope (altitude, epoch, particle diameter), and62 uncertainty factor.632. `applicability_gaps` / `is_model_applicable` — check a case's64 parameters against one model's envelope and report which dimensions65 (if any) fall outside it.663. `applicable_models` / `recommend_model` — list every model whose67 envelope covers a case, and pick the tightest (lowest-uncertainty)68 one among them.694. `uncertainty_bounds` / `cross_check_reported_flux` — compute the70 low/high bound around a nominal or reported flux value using the71 model's uncertainty factor, and flag a reported flux that cites a72 model outside its own applicability envelope.7374## When to invoke this skill7576- Choosing which meteoroid or orbital-debris model to run (or cite) for77 a shielding, penetration-risk, or micrometeoroid-and-orbital-debris78 (MMOD) budget analysis at a given orbit and epoch.79- Reviewing a vendor- or tool-supplied flux number and checking whether80 the model it claims to come from actually covers the case's altitude,81 epoch, and particle-size range before the number is used downstream.82- Propagating a flux-model uncertainty band into a risk or probability-83 of-no-penetration calculation instead of treating a model's nominal84 output as exact.8586Not for the MMOD penetration/risk calculation itself, hypervelocity-87impact damage equations, or the trapped-radiation environment88(`e1004-trapped-leo` and siblings) — this leaf only selects and bounds89the input flux model.9091## Data provenance and fidelity notice9293The model registry in `scripts/e1004_ref_debris_logic.py`94(`grun_interplanetary`, `ordem`, `master`) is an **illustrative95reference set** built from widely published, generic descriptions of96the class of meteoroid and orbital-debris engineering models used in97astrodynamics practice (a Grün-class interplanetary meteoroid model,98NASA's ORDEM-class LEO debris engineering model, ESA's MASTER-class99LEO-through-GEO debris model) — it is not a transcription of the100standard's Annex J tables, and the envelope bounds and uncertainty101factors are representative order-of-magnitude values, not the current102released version's exact figures. For mission-grade, traceable103analysis, replace the registry entries with the specific model104version, applicability envelope, and uncertainty figures published by105the model's current release notes, keeping the same function interface106(`applicability_gaps`, `uncertainty_bounds`, `recommend_model`). The107applicability and uncertainty-bounding logic is model-registry-108independent and does not need to change when the entries are updated.109110## Steps1111121. **Categorize the object family.** `classify_object_family(object_family)`113 accepts `"meteoroid"` or `"debris"`; raises `ValueError` for any114 other value.1152. **Check one model's applicability.** `applicability_gaps(model_name,116 object_family, altitude_km, epoch_year, diameter_m)` returns a dict117 of the dimensions (`family`, `altitude_km`, `epoch_year`,118 `diameter_m`) that fall outside that model's envelope for the case119 (empty dict means fully applicable). `is_model_applicable(gaps)`120 reduces that to a boolean. Raises `ValueError` for an unknown121 `model_name`.1223. **List every applicable model.** `applicable_models(object_family,123 altitude_km, epoch_year, diameter_m)` returns the sorted names of124 every registered model with no gaps for the case; raises125 `ValueError` for an unrecognized `object_family`.1264. **Recommend a model.** `recommend_model(object_family, altitude_km,127 epoch_year, diameter_m)` returns the applicable model with the128 lowest uncertainty factor; raises `ValueError` when no registered129 model covers the case (the case needs a model outside this130 registry, not a silent default).1315. **Bound a flux value.** `uncertainty_bounds(model_name, nominal_flux)`132 returns `(low, high)` using the model's uncertainty factor133 (`nominal_flux / factor`, `nominal_flux * factor`); raises134 `ValueError` for a negative flux or an unknown model.1356. **Cross-check a reported flux/model pairing.**136 `cross_check_reported_flux(model_name, object_family, altitude_km,137 epoch_year, diameter_m, reported_flux)` returns138 `{"issue": "reported_flux_outside_model_envelope", "model": ...,139 "gaps": {...}}` when the pairing is out of envelope, or `{"issue":140 None, "model": ..., "uncertainty_low": ..., "uncertainty_high": ...}`141 when it is applicable. Do not accept a reported flux number until142 `issue` is `None`.143144## Pitfalls145146- Using a debris model's flux number outside its epoch window (the147 catalogued population changes over time) and treating it as still148 current -- `applicability_gaps` flags an out-of-range `epoch_year`149 for exactly this reason.150- Applying a LEO-scoped debris model's flux at GEO, or vice versa, just151 because it was the model on hand -- check `altitude_km` applicability152 before reuse; a model with no envelope coverage for a case is not the153 best available answer, it is inapplicable.154- Reporting a model's nominal flux as a single number in a risk155 calculation without carrying its uncertainty band -- every registered156 model has a nontrivial `uncertainty_factor`; downstream margin157 calculations must use `uncertainty_bounds`, not just the nominal158 value.159- Picking the first applicable model found instead of the tightest one160 -- `recommend_model` selects the lowest-uncertainty applicable model;161 a wider-envelope, higher-uncertainty model should only be used when162 no tighter model covers the case.163164## Behavior contract (gate 3)165166The model-applicability, model-selection, and uncertainty-bounding167logic is exercised by the gate 3 contract test:168scripts/test_e1004_ref_debris.py against169scripts/e1004_ref_debris_logic.py (stdlib unittest, offline). Run:170python3 scripts/test_e1004_ref_debris.py171172## Compliance173174- ECSS standards are freely downloadable (ESA); cite the source and175 paraphrase per standards-map.yaml.176- compliance: STANDARDS-REF, gated: false.