Make more useful / complete orbit points and rad zones

[taldcroft]

EDIT: see the comment below.

Use the orbit events file e.g. /occweb/FOT/mission_planning/Backstop/FEB0320A/mps/er/DO20006.orp

Define rad zone as EEF1000 to XEF1000.

2020:018:07:29:50.943   2824  EEF1000   ELECTRON 1 RADIATION ENTRY 0                           
 2020:018:07:57:50.943   2824  EPF1000   PROTON 1 RADIATION ENTRY 0                             
 2020:018:08:47:12.009   2824  EALT0     ALTITUDE ZONE ENTRY0                                   
 2020:018:08:47:13.650   2824  XALT0     ALTITUDE ZONE EXIT 0                                   
 2020:018:10:11:17.258   2824  EPERIGEE  ORBIT PERIGEE                                          
 2020:018:11:35:20.462   2824  EALT0     ALTITUDE ZONE ENTRY0                                   
 2020:018:11:35:21.765   2824  XALT0     ALTITUDE ZONE EXIT 0                                   
 2020:018:14:27:50.943   2824  XPF1000   PROTON 1 RADIATION EXIT 0                              
 2020:018:16:21:50.943   2824  XEF1000   ELECTRON 1 RADIATION EXIT 0                            
 2020:018:16:30:31.193   2825  EASCNCR   ORBIT ASCENDING NODE CROSSING                          
 2020:018:17:24:34.165   2825  XQF015M   PROTON FLUX EXIT FOR ENERGY 0 LEVEL 1 KP 5 MEAN        
 2020:018:18:00:34.165   2825  XQF005M   PROTON FLUX EXIT FOR ENERGY 0 LEVEL 0 KP 5 MEAN        
 2020:018:18:04:34.165   2825  XQF003M   PROTON FLUX EXIT FOR ENERGY 0 LEVEL 0 KP 3 MEAN        
 2020:018:18:04:34.165   2825  XQF013M   PROTON FLUX EXIT FOR ENERGY 0 LEVEL 1 KP 3 MEAN        
 2020:018:23:34:04.593   2825  EALT1     ALTITUDE ZONE ENTRY 1                                  
 2020:018:23:34:05.453   2825  XALT1     ALTITUDE ZONE EXIT 1                                   
 2020:019:17:55:11.704   2825  EAPOGEE   ORBIT APOGEE                                           
 2020:020:04:28:30.605   2825  EQF005M   PROTON FLUX ENTRY FOR ENERGY 0 LEVEL 0 KP 5 MEAN       
 2020:020:04:44:30.605   2825  EQF015M   PROTON FLUX ENTRY FOR ENERGY 0 LEVEL 1 KP 5 MEAN       
 2020:020:12:16:11.788   2825  EALT1     ALTITUDE ZONE ENTRY 1                                  
 2020:020:12:16:13.576   2825  XALT1     ALTITUDE ZONE EXIT 1                                   
 2020:020:19:52:30.605   2825  EQF003M   PROTON FLUX ENTRY FOR ENERGY 0 LEVEL 0 KP 3 MEAN       
 2020:020:21:48:30.605   2825  EQF013M   PROTON FLUX ENTRY FOR ENERGY 0 LEVEL 1 KP 3 MEAN       
 2020:020:23:07:47.383   2825  EEF1000   ELECTRON 1 RADIATION ENTRY 0                           

[taldcroft]

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.

• /occweb/FOT/mission_planning/Backstop/Ephemeris (recent)
• /occweb/FOT/mission_planning/Backstop/Ephemeris/Archive (archive)

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).

[taldcroft]

This came up again:
https://chandramission.slack.com/archives/C016BRC0U5S/p1686596880066339

[taldcroft]

Would be good to do this in kadi commands as well.