ECSS Space Radiation — Sensor Background from Direct Ionisation (space-systems/ecss/e1012-bg-direct)
Use when the task is to predict the background count rate in a spaceborne
sensor caused by direct ionisation of its active volume by charged
particles, following ECSS-E-ST-10-12C §10.4.2. The procedure covers
identifying the contributing particle populations, computing the deposited
energy for each population using its linear energy transfer (LET) and the
sensor geometry, filtering out populations that fall below the detection
threshold, and comparing the accumulated rate against the sensor background
allocation.
Domain quick reference
- Direct ionisation is the mechanism by which a charged particle (proton,
electron, heavy ion) traverses the active detector volume and transfers
energy to the material through Coulomb interactions with bound electrons.
In semiconductor sensors this creates free electron-hole pairs; in
scintillators it produces photons. If the resulting signal exceeds the
detection threshold the crossing is recorded as a background event.
- Linear energy transfer (LET) quantifies the mean energy deposited per
unit areal density along the particle track, in units of MeV·cm²/mg (or
equivalently MeV·cm²/g × 10⁻³). The stopping power in MeV/cm equals
LET × material density (mg/cm³). For a sensor with known thickness and
material density, the energy deposited per crossing is
LET × density_mg_cm3 × path_length_cm.
- Particle populations that contribute to direct-ionisation background
in typical Earth orbits are: trapped protons, trapped electrons,
galactic cosmic-ray protons, galactic cosmic-ray heavy ions, and solar
energetic protons and heavy ions. Each population has a distinct flux
spectrum and LET range. Each is treated as a separate contributor.
- Detection threshold: only crossings that deposit energy at or above
the threshold produce a recorded background event. Populations whose
deposited energy falls below the threshold are excluded from the
background sum.
- Geometry factor: for a flat detector illuminated by an isotropic
omnidirectional flux, only particles arriving from the forward hemisphere
can traverse the detector face. The effective rate of hits is
flux × area × 0.5 (hemisphere factor = 0.5 for isotropic illumination
of one face).
- Background allocation: the total accumulated rate is compared against
the sensor-level background allocation derived from the instrument
performance requirement. An exceedance is a finding that requires
shielding, threshold adjustment, or environmental mitigation.
Workflow
- Identify the orbit environment and retrieve the omnidirectional particle
flux (particles/cm²/s) for each relevant population (trapped protons,
trapped electrons, GCR protons, GCR heavy ions, SEP protons, SEP heavy
ions). Each population must be assigned one of the recognised type
identifiers; an unrecognised type is rejected before it enters the
calculation.
- Record the sensor geometry and material: active area (cm²), active
thickness (cm), material density (g/cm³), and the detection threshold
(MeV of deposited energy). Reject any sensor spec with non-positive
dimensions or density.
- For each particle population, compute the deposited energy per crossing:
E_dep [MeV] = LET [MeV·cm²/mg] × density [g/cm³] × 1000 [mg/g] × thickness [cm].
This assumes normal-incidence path length equal to the active thickness;
a mean chord calculation (4V/S for a convex body) may be substituted for
a full geometry model.
- Apply the detection threshold: a population contributes to the background
only if
E_dep ≥ threshold_mev. Populations below threshold are recorded
as sub-threshold contributors but carry zero rate.
- For each contributing population, compute the hit rate:
rate [events/s] = flux [/cm²/s] × area [cm²] × 0.5.
The factor 0.5 is the hemisphere factor for isotropic illumination of a
single flat detector face.
- Sum the hit rates across all contributing populations to obtain the total
background rate (events/s).
- If a background allocation (budget) is on record, compare the total rate
against it. Flag any exceedance. If no budget is recorded, flag the
missing allocation as a finding — absence of a budget is not a pass.
- Report: total background rate, per-population breakdown (deposited energy,
above/below threshold, individual rate), budget comparison status.
Pitfalls
- Omitting a particle population because its individual contribution seems
small — in high-inclination or deep-space orbits, GCR heavy ions can
dominate background even at low flux because their high LET ensures every
crossing is above threshold.
- Applying the flux directly as a hit rate without the hemisphere factor —
an omnidirectional flux already integrates over 4π steradians; dividing
by two (0.5) for one-sided illumination is mandatory to avoid a factor-of-two
overestimate.
- Treating a sub-threshold population as a zero-risk population without
recording it — changes in threshold (e.g. electronics aging) or in the
LET (e.g. higher-Z particles) can promote a sub-threshold contributor into
a significant one; the sub-threshold list must be retained in the assessment.
- Using path length equal to the sensor diagonal rather than the mean chord
or normal-incidence thickness — this inflates deposited energy and can
cause an over-conservatism that masks real mitigation options.
- Leaving the background allocation unset and interpreting "no exceedance"
as compliant — a missing allocation means the performance requirement was
never captured, which is itself a finding.
Behavior contract (gate 3)
The particle validation, deposited-energy calculation, threshold filtering,
hit-rate accumulation, and budget-comparison logic are exercised by the gate 3
contract test: scripts/test_e1012_bg_direct.py against
scripts/e1012_bg_direct_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e1012_bg_direct.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e1012-bg-direct3description: "Use when predict the sensor background count rate produced by direct ionisation of the active detector volume by charged particles under ECSS-E-ST-10-12C §10.4.2: identify the charged particle populations (trapped protons, trapped electrons, galactic cosmic rays, solar energetic particles) at the target orbit, compute the energy deposited per crossing particle from its linear energy transfer (LET) and sensor geometry, retain only populations whose deposited energy meets or exceeds the detection threshold, accumulate the background event rate across all contributing populations using particle flux and sensor cross-section, and compare the aggregated rate against the sensor background allocation. Trigger: ecss, e-st-10-12c, sensor-background, direct-ionisation, charged-particle, let, deposited-energy, detection-threshold."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/e1012-bg-direct15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-10-12c, sensor-background, direct-ionisation, charged-particle, let, deposited-energy, detection-threshold]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Space Radiation — Sensor Background from Direct Ionisation (space-systems/ecss/e1012-bg-direct)2324Use when the task is to predict the background count rate in a spaceborne25sensor caused by direct ionisation of its active volume by charged26particles, following ECSS-E-ST-10-12C §10.4.2. The procedure covers27identifying the contributing particle populations, computing the deposited28energy for each population using its linear energy transfer (LET) and the29sensor geometry, filtering out populations that fall below the detection30threshold, and comparing the accumulated rate against the sensor background31allocation.3233## Domain quick reference3435- **Direct ionisation** is the mechanism by which a charged particle (proton,36 electron, heavy ion) traverses the active detector volume and transfers37 energy to the material through Coulomb interactions with bound electrons.38 In semiconductor sensors this creates free electron-hole pairs; in39 scintillators it produces photons. If the resulting signal exceeds the40 detection threshold the crossing is recorded as a background event.41- **Linear energy transfer (LET)** quantifies the mean energy deposited per42 unit areal density along the particle track, in units of MeV·cm²/mg (or43 equivalently MeV·cm²/g × 10⁻³). The stopping power in MeV/cm equals44 LET × material density (mg/cm³). For a sensor with known thickness and45 material density, the energy deposited per crossing is46 `LET × density_mg_cm3 × path_length_cm`.47- **Particle populations** that contribute to direct-ionisation background48 in typical Earth orbits are: trapped protons, trapped electrons,49 galactic cosmic-ray protons, galactic cosmic-ray heavy ions, and solar50 energetic protons and heavy ions. Each population has a distinct flux51 spectrum and LET range. Each is treated as a separate contributor.52- **Detection threshold**: only crossings that deposit energy at or above53 the threshold produce a recorded background event. Populations whose54 deposited energy falls below the threshold are excluded from the55 background sum.56- **Geometry factor**: for a flat detector illuminated by an isotropic57 omnidirectional flux, only particles arriving from the forward hemisphere58 can traverse the detector face. The effective rate of hits is59 `flux × area × 0.5` (hemisphere factor = 0.5 for isotropic illumination60 of one face).61- **Background allocation**: the total accumulated rate is compared against62 the sensor-level background allocation derived from the instrument63 performance requirement. An exceedance is a finding that requires64 shielding, threshold adjustment, or environmental mitigation.6566## Workflow67681. Identify the orbit environment and retrieve the omnidirectional particle69 flux (particles/cm²/s) for each relevant population (trapped protons,70 trapped electrons, GCR protons, GCR heavy ions, SEP protons, SEP heavy71 ions). Each population must be assigned one of the recognised type72 identifiers; an unrecognised type is rejected before it enters the73 calculation.742. Record the sensor geometry and material: active area (cm²), active75 thickness (cm), material density (g/cm³), and the detection threshold76 (MeV of deposited energy). Reject any sensor spec with non-positive77 dimensions or density.783. For each particle population, compute the deposited energy per crossing:79 `E_dep [MeV] = LET [MeV·cm²/mg] × density [g/cm³] × 1000 [mg/g] × thickness [cm]`.80 This assumes normal-incidence path length equal to the active thickness;81 a mean chord calculation (4V/S for a convex body) may be substituted for82 a full geometry model.834. Apply the detection threshold: a population contributes to the background84 only if `E_dep ≥ threshold_mev`. Populations below threshold are recorded85 as sub-threshold contributors but carry zero rate.865. For each contributing population, compute the hit rate:87 `rate [events/s] = flux [/cm²/s] × area [cm²] × 0.5`.88 The factor 0.5 is the hemisphere factor for isotropic illumination of a89 single flat detector face.906. Sum the hit rates across all contributing populations to obtain the total91 background rate (events/s).927. If a background allocation (budget) is on record, compare the total rate93 against it. Flag any exceedance. If no budget is recorded, flag the94 missing allocation as a finding — absence of a budget is not a pass.958. Report: total background rate, per-population breakdown (deposited energy,96 above/below threshold, individual rate), budget comparison status.9798## Pitfalls99100- Omitting a particle population because its individual contribution seems101 small — in high-inclination or deep-space orbits, GCR heavy ions can102 dominate background even at low flux because their high LET ensures every103 crossing is above threshold.104- Applying the flux directly as a hit rate without the hemisphere factor —105 an omnidirectional flux already integrates over 4π steradians; dividing106 by two (0.5) for one-sided illumination is mandatory to avoid a factor-of-two107 overestimate.108- Treating a sub-threshold population as a zero-risk population without109 recording it — changes in threshold (e.g. electronics aging) or in the110 LET (e.g. higher-Z particles) can promote a sub-threshold contributor into111 a significant one; the sub-threshold list must be retained in the assessment.112- Using path length equal to the sensor diagonal rather than the mean chord113 or normal-incidence thickness — this inflates deposited energy and can114 cause an over-conservatism that masks real mitigation options.115- Leaving the background allocation unset and interpreting "no exceedance"116 as compliant — a missing allocation means the performance requirement was117 never captured, which is itself a finding.118119## Behavior contract (gate 3)120121The particle validation, deposited-energy calculation, threshold filtering,122hit-rate accumulation, and budget-comparison logic are exercised by the gate 3123contract test: scripts/test_e1012_bg_direct.py against124scripts/e1012_bg_direct_logic.py (stdlib unittest, offline). Run:125python3 scripts/test_e1012_bg_direct.py126127## Compliance128129- ECSS standards are freely downloadable (ESA); cite the source and130 paraphrase per standards-map.yaml.131- compliance: STANDARDS-REF, gated: false.