View segment definition

History

Mnemonic:

JUPITER_FD_WOL

Name:

JUPITER_FD_WOL

Description:

Flight dynamics wheel off-loading slot, outside of Flyby preparation and recuperation

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:

GENERIC

Pointing

Pointing request file:

Slew Policy:

Pointing Target:

Scheduler

Scheduler Flag:

Scheduling Priority:

Observation Definitions

Observation definitions:

Advanced

Scheduling rules:

from MPAD:
;2 hours long WOL slots shall be reserved every 72 h (or shorter).
Note that after discussion with Ignacio we assume that the FD block duration given always include twice a 30 mn slew

Contextual Parameters:

Comments:

;There is in principle no restriction on in-situ science during WOL slots, except for instrument-specific operational constraints.

Implementation in geopipeline:
;;We assumed that the time given by FD in the MPAD always include 30 mn slew time on both sides
;;So the basic duration of the WOL is 1h -
The WOL is scheduled adjacent to a DL segment: For each DL pass, we schedule a WOL slot of wol_seg_duration ending right at the beginning of the malargue visibility - we do not need to add the slew time of 30 mn at the end of the WOL because it is already taken into account in the DL segment - we only add the slew time at the beginning of the block - the total duration appears in this case to be 1.5 hours

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

JSOC Uplink Core System