Logs
Logs is the conjunction event's history as a single timeline. Each entry records what changed, when, and which CDM or upload caused it.
Entry Types
| Entry | What it records |
|---|---|
| First conjunction ingested by Satcat | The conjunction event opening, on its first CDM |
| New source added | An originator issuing CDMs for this conjunction event for the first time |
| CDM update | A new CDM, with its Pc, miss distance, and recommendation |
| Risk level changed | A crossing into a different risk level, with the previous and new value |
| Ephemeris uploaded | An ephemeris upload affecting this conjunction event, and whether it was OPERATIONAL |
| Operator file received | A file received from the other operator |
| Mitigation planned | A mitigation plan created or updated, with its expected result |
| Org intends to mitigate | A change in declared mitigation intent |
| Conjunction event TCA has passed | The conjunction event moving into its historical state |
What an Entry Shows
Each entry carries the fields relevant to its type. A CDM update reports Pc value, MD (Total RSS) with its Radial, In-track, and Cross-track values, TCA delta, and Recommendation. A mitigation plan reports Expected Pc, Expected MD, and Delta-v. A risk level change reports the Risk level before and after.
Where a previous value exists, it is shown beside the new one and marked with the direction risk moved. Direction is evaluated per metric rather than per entry: a falling miss distance is an increase in risk, while a falling Pc is a decrease.
An expected value on a mitigation plan that has not been operationalized is marked as projected rather than measured.