Open taldcroft opened 4 years ago
This has come up again in the context of ACA pre-review needing a source of predictive orbit events (perigee). A better solution is to use .orb
orbit event files here to populate events in kadi.commands v2, and then kadi events (Orbit
, OrbitPoint
) can be populated from commands. This will make the kadi ORBPOINT
commands be complete out into the future.
As usual this requires some rewriting command history when a new orbit event file comes out that supercedes previous events. Fortunately the orbit number is a unique key that allows for clean replacement (as opposed to event times that may slosh one way or another).
This came up again: https://chandramission.slack.com/archives/C016BRC0U5S/p1686596880066339
Would be good to do this in kadi commands as well.
EDIT: see the comment below.
Use the orbit events file e.g. /occweb/FOT/mission_planning/Backstop/FEB0320A/mps/er/DO20006.orpDefine rad zone as EEF1000 to XEF1000.