Skip to main content

Synthetic Covariance

Overview​

info

Synthetic covariance can be used with Satcat Screener to compute collision probability values for CDMs using the 18SDS / SP ephemeris catalog.

While the SP ephemeris catalog as generated by the United States Space Force does not include covariance information, Satcat Operations generates synthetic covariance for each new SP ephemeris catalog using a statistical approach based on historical ephemeris overlap residuals. This allows Satcat Screener to compute risk metrics which require state uncertainty information, such as collision probability, on generated CDMs.

note

Use of synthetic covariance requires an active Satcat Operations Pro or Enterprise tier subscription.

Concept and Implementation​

Typically, covariances in predictive ephemerides are generated by propagating an initial covariance derived from an orbit determination process, which accounts for measurement errors and dynamic model uncertainties. In contrast, Satcat generates synthetic covariance by statistically analyzing historical ephemeris overlap residuals to estimate the uncertainty associated with each new SP ephemeris ephemeris for each individual object. Satcat's synthetic covariance system uses a rolling 21-day window to continuously update the synthetic covariance estimates for a given object as new ephemeris data becomes available, as object characteristics and tracking conditions evolve over time. All synthetic covariance statistics are measured for each individual object separately.

Because synthetic covariance relies on a sufficient history of ephemeris overlap residuals, it may not be available for newly tracked objects or for objects with limited historical data.

Currently, Satcat only generates synthetic covariance for the SP ephemeris catalog.

Usage​

Use of synthetic covariance is disabled by default for backwards compatibility. To enable synthetic covariance for a screening created in the Satcat UI, enable the "Use Synthetic Covariance" option in the "Advanced options" section. When using the Satcat API or Python SDK, set allow_synthetic_covariance to true in the screening request.

Groups can set default_allow_synthetic_covariance to true to make synthetic covariance the default for screenings in that group. A screening request can override the group default by setting the parameter explicitly to true or false.

When viewing the Conjunction Event Page for a given CDM, you can identify whether synthetic covariance was used for an object's state at TCA by examining the "Primary Source Details" / "Secondary Source Details" > "Covariance Method" field for the primary or secondary object respectively.