Environment and operations¶
Follow environment assumptions into a result¶
The Console exposes environment effects where they are consumed. Open Sizing and budgets > Power, choose Downlink > Sunlight, then expand Analysis context and sources. This walkthrough uses the Symmetric deployable arrays starter.
The captured Sun-access factor is 0.82 while the incidence factor is 0. These describe different parts of the selected mode's sunlight generation basis; Sun access alone does not establish a Sun-facing array area. The irradiance factor, 1.006, remains a separate term.
Read Allocated duration and the Mode time allocation plot alongside those factors. To inspect the physical area behind the exposure, open Spacecraft > Placement and choose the matching Exposure scenarios entry. The placement walkthrough connects those areas to the recorded hardware and CAD.
For a warning or missing assumption, follow Open checks and evidence from the consuming subsystem. Keep the environment and operations records with the result when you need the full orbit, mode and applicability definitions.
Define the operating conditions¶
The same spacecraft can have different power, thermal and drag demands in a different orbit or attitude. Environment provides orbital geometry, radiation and atmosphere cases; operations defines when hardware is active and how the spacecraft is oriented. Read them together when tracing an unexpected load.
Specify the target orbit's altitude in km, inclination and relevant angular inputs in degrees, epoch, and either appropriate local-time or ascending-node information. Keep injection and target orbits distinct when defining maneuvers. Mode duration fractions sum to one; their payload, communications and propulsion activities must match the hardware states and timelines used by those models.
Native orbital model¶
The native analytic model supports LEO/SSO regimes from 160 to 2000 km, with eccentricity at most 0.01. It uses circular-orbit geometry within that bounded envelope; a supported input is not a high-fidelity propagated trajectory.
Here \(R_{\mathrm E}\) is Earth's equatorial radius, \(h\) the altitude and \(r\) the orbital radius, all in m. The gravitational parameter \(\mu\) is in m³/s², giving orbital period \(T\) in s. The beta angle is taken from an explicit value when available, otherwise derived from dated orbit/solar geometry. If the required geometry is absent, the model uses a conservative zero-beta default and records that limitation.
The spherical eclipse construction uses the critical beta angle \(\beta_{\mathrm{crit}}=\arcsin(R_{\mathrm E}/r)\). Above that magnitude there is no eclipse in this model; below it, the shadow geometry gives an eclipse fraction. Maximum eclipse duration is period times that fraction. Review the beta resolution method before using the duration as a mission prediction.
Keep physical factors separate¶
| Term | Meaning | Consumer responsibility |
|---|---|---|
| Orbital sunlight/eclipse fraction | Shadow geometry | Determines time available, not panel orientation |
| Sun access and mode activity | Operational availability | Must agree with timeline/state assumptions |
| Geometric projected area | Directional visible physical area, m² | Already includes incidence and represented occlusion |
| Flux, efficiency and degradation | Environmental/hardware response | Applied by the relevant subsystem, not hidden in geometric area |
Weighted mode summaries are duration-fraction weighted. Do not apply eclipse or incidence twice when moving from environment summaries to geometry-resolved EPS segments. Atmospheric density and radiation cases carry reference authority and applicability; a selected case does not represent a complete uncertainty model.
Outputs, failures and limits¶
Review result.operations, result.environment, face exposure and
result.geometry-environment-loading together. The environment result retains
orbit geometry, selected reference case, mode terms, assumptions and applicability.
The operations result records authored context; it does not independently verify
that a real mission follows that schedule.
Out-of-envelope orbit inputs are unsupported. Missing required attitude data must not become invented diffuse exposure. External environment products have a separate exchange/provenance contract and need matching orbit/mode definitions. Continuous propagation, detailed atmosphere/weather evolution and flight attitude replay remain outside the native analytic calculation.
Follow geometry loading next, or inspect environment fields. In EX01, the directional exposure is essential to understanding why a reported array area does not close the energy cycle.
