View segment definition

History

Mnemonic:

JUPITER_FD_TCM

Name:

JUPITER_FD_TCM

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:

GENERIC

Pointing

Pointing request file:

Slew Policy:

Pointing Target:

Scheduler

Scheduler Flag:

Scheduling Priority:

Observation Definitions

Observation definitions:

Advanced

Scheduling rules:

Contextual Parameters:

Comments:

Opportunity implementation in geopipeline
2 hours blocks + 30 mn on both sides to allow for slew time [3 hours total], at -7d/-3d/+3d wrt FB events (closest approach)

NOTE: TCM may be needed also at apojove but less regularly - during discussion with FD, was agreed to not take those into account for the moment

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