View segment definition

History

Mnemonic:

JUPITER_FD_WOL_FB

Name:

JUPITER_FD_WOL_FB

Description:

In the last week before the fly-by a WOL slot shall be combined with the
TCM slot at To– 3 days (i.e. a single 3-hr slot). Another 2-hour WOL slot shall be reserved at To + 12 hours.

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:

Contextual Parameters:

Comments:

Implementation in geopipeline:
Basic duration is 1 hour, considering that the total duration given by FD in the MPAD includes twice 30 mn slew time
One segment 12h after each FB closest approach
We add 30 mn before and after the block, total duration 2 hours
Before the FB, the geopipeline does not generate a WOL segment as it is assuming to be contained by the TCM segment at CA-3 days

Attachment file 1:

Attachment file 2:

Attachment file 3:

Attachment file 4:

Segment definition resources

	Category	Target	Instrument type	Value	Unit
Data rate Plasma 7.36 kilobits per second	Data rate	Plasma	In-Situ	7.36	kilobits per second

Segment definition instrument resources

	Category	Target	Instrument	Value	Unit

Close Cancel

JSOC Uplink Core System