JSOC Uplink Core System
Home
›
Core
›
Segment definitions
› J_FD_EPHEM_E
View segment definition
History
Mnemonic:
J_FD_EPHEM_E
Name:
J_FD_EPHEM_E
Description:
Trajectories:
CReMA 3.0, CReMA 3.1, CReMA 3.2
Prime Segment:
Group:
GENERIC
Pointing
Pointing request file:
Slew Policy:
-
Pointing Target:
Scheduler
Scheduler Flag:
Scheduling Priority:
-
Observation Definitions
Observation definitions:
3GM_HAA_CALIBRATION, HAA_STDBY, 3GM USO SWON
Advanced
Scheduling rules:
Contextual Parameters:
Comments:
Implementation in scheduler:
Slots of 1 hours of moon ephemerides once per day (right now between 2 downlinks, TODO: to be when there are no 1 downlink per day)
Slots can only be included during potential WG3 opportunity windows
Slots must be expanded +/- 30 minutes if not before/after fd_tcm, fd_wol or dl_ segments
Moon ephemerides priority rules:
--> if possible, the selected slot should be scheduled during visibility of MLG but outside DL windows (information regarding visibility and donwlink window time are computed by the geopipeline and provided in mission_timeline_event_file_X_Y (X_Y: crema version) file available from the timeline tool
--> if more than one option exists, then the scheduling priority should be
JUPITER_FD_EPHEM_GAN has priority over JUPITER_FD_EPHEM_CAL and both have priority over JUPITER_FD_EPHEM_EUR.
-SWI contribution taken as averaged moon monitoring rate of 0.33 kbps (1/16 of the rate 5.33 kbps, email from T. Cavalie on 28/09/2020)
FD: assumption of 3 images per slot , 37.09 Mbits (email from Daniele Gherardi on 30/09/2020)
Attachment file 1:
Attachment file 2:
Attachment file 3:
Attachment file 4:
Segment definition resources
Category
Target
Instrument type
Value
Unit
Segment definition instrument resources
Category
Target
Instrument
Value
Unit
Close
Cancel