JSOC Uplink Core System
Home
›
Core
›
Segment definitions
› JUPITER_PHASE_MAX
View segment definition
History
Mnemonic:
JUPITER_PHASE_MAX
Name:
JUPITER_PHASE_MAX
Description:
Trajectories:
CReMA 3.0, CReMA 3.1, CReMA 3.2, CREMA_5_0, CREMA_5_0b23_1, CREMA_5_1_150lb_23_1, CREMA_5_1_150lb_23_1_a3, CREMA_5_1_150lb_23_1_b2
Prime Segment:
Group:
Working Group 4
Pointing
Pointing request file:
Slew Policy:
-
Pointing Target:
Scheduler
Scheduler Flag:
Scheduling Priority:
-
Observation Definitions
Observation definitions:
Advanced
Scheduling rules:
(+/-) 5 hours around max phase when > 175 deg and outside other main WG4 segments
Contextual Parameters:
Comments:
Opportunity implementation in geo-pipeline
-maximum allowed distance: < 2e6 km
-looking for 150 deg deg phase crossing events - maximum phase event searched only if a 150 deg event exists
-Define +-5 hours segments around those events, check for Moon flyby segment overlap or Malargue Downlink passes
NOTE: we check the overlap with the Donwlink pass, not with Malargue visibility -
;;With this assumption, we assume that the segment can be scheduled always at Malargue visibility start + 8h - this may not be the case in reality
;;but this allows to have less variation in phase angle due to the shift in time, when the phase is evolving rapidly
-In case of overlaps, shift segment in time for up to 20 deg phase offset - if no solution found, remove
-In case of overlap with Malargue downlink passes, we adjust to start or end within 30 mn of downlink start of end
-In case of overlap with moon flyby, we move the segment to the beginning or end of the moon segment, whichever is the closer in time
Final check after shifting: overlap with solar conjunction or eclipse: removed, segments outside of max distance: removed
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