glast lat projectisoc cdr, 4 august 2004 document: lat-pr-04500section 4.11 glast large area...

GLAST LAT Project ISOC CDR, 4 August 2004

Document: LAT-PR-04500 Section 4.1 1

GLAST Large Area Telescope:GLAST Large Area Telescope:

Instrument Science Operations Center Instrument Science Operations Center CDRCDR

Section 4.1 Operations Planning & Interfaces

Lori [email protected]

Seth [email protected]

Gamma-ray Large Gamma-ray Large Area Space Area Space TelescopeTelescope



LAT Operations Planning and Command ProcessLAT Operations Planning and Command Process

GLAST Science Support Center

(GSSC)

Operations Plan

Command Plan Build &

Review

Mission Operations Center (MOC)

Final Science Timeline

Preliminary and Final Science Timelines

ISOC

Science Plan (Phase 2)

Feedback

Mission Planning

Verification & Validation

ATS Commands

File Uploads

Command Procedures

Command Plan

TDRSS ScheduleEngineering PlanMission Timeline

Command Plan



DefinitionsDefinitions

Science Plan – Observatory activities– Phase 1: ISOC maintains LAT science plan– Phase 2: Plan maintained by GSSC [Phase 2] and includes

guest investigator proposals, coordinated with GBM and LAT. GSSC assists in overall science plan evaluation and will manage the proposal process.

Operations Plan – Derived from evaluated performance of the LAT, the as-flown timeline, the science plan [for Phases 1 and 2], and calibration needs

Command Plan – The translation of the operations plan into ATS commands, file uploads and real-time operations procedures for one week of operating the LAT. Tables of parameter values and flight software are also part of the command plan.



Operations PlanningOperations Planning

Seth DigelSeth Digel



Operations Planning in the ISOCOperations Planning in the ISOC

Describing what goes on in this box

From the Operations Concept Document (LAT-SS-01378)


(GSSC)

Operations Plan


Review




ISOC


Feedback

Mission Planning


ATS Commands

File Uploads

Command Procedures

Command Plan


Command Plan



ISOC OrganizationISOC Organization

ISOC Manager

4.1.B.10Command, H&S

4.1.B.11 FSW

4.1.B.12 Performance V&O

4.1.B.13Science Products

4.1.B.14 Science Analysis

Software

Commanding

Health & Safety

Configuration

Thermal Control

Trigger

Filter

Testbed

Calibration

PerformanceTrending

Standard SourceMonitoring

IRF Generation

Level 1CRs, gammas,

diagnostics

Level 2Transients, GRBs

Pipeline Server

Simulation

Calibration

Reconstruction &Event Classif.

Transient SourceAnalysis

Databases

All ISOC teams are involved in this activity; input can also come from outside the ISOC) – CHS is the lead



Operations PlanOperations Plan

Monthly plan of LAT operations based on the overall science plan Science activities per se are not typically the driver

– For a scanning sky survey (Phase 1 and likely also most of Phase 2), the ‘science activities’ are the same all the time

– The science plan in Phase 2 will be developed by the GSSC The subsystems have calibration needs that occasionally will require

special observing modes (or scheduling of more than the usual number of TDRS contacts)

Most calibration data taking will not require specific orientations for GLAST

– Occasional exceptions will be, e.g., pointed observation of ‘standard candle’ celestial sources or possibly scans of the Earth limb and the nadir to characterize the albedo background

So, in general the operations plan may have no impact on the pointing of GLAST, and will be irrelevant in development of the contact schedule for TDRSS



Influences on the Operations PlanInfluences on the Operations Plan

[PVO] The calibration requirements of the subsystems, detailed in LAT-MD-00446 define the basic ‘recurrence time’ of the calibrations

[CHS] The as-flown timeline is monitored to determine whether requested calibration observations were made. [N.B. Again, many of the calibration observations can be made without interrupting science observations.]

[FSW] Approved software updates and table loads need to be scheduled

[SP] Routine processing of calibration data - not interpretation of results, but supports PVO

[SAS] Also supports PVO with, e.g., simulation software for the LAT



Appropriate OversightAppropriate Oversight

The organization of the scientific activities of the LAT collaboration outside of the ISOC is still being defined– This will be a major subject of the next collaboration

meeting, Sept. 27-29 at SLAC What seems likely right now: A committee with collaboration

and probably Project Scientist representation will oversee the science-related activities of the ISOC, i.e., will serve as the interface between science and operations

Examples of the science-operations interface:– Acceptance of updated algorithms for the LAT trigger or

event filtering (on board or on the ground)– Definitions of conditions when the LAT will autonomously

request a repointed observation



Regarding Phases 0 & 1Regarding Phases 0 & 1

Phase 0 – turn on and checkout of the LAT – a special case in almost every respect, although the internal interfaces in the ISOC will of course remain the same– Phase 0 does not have a science plan, but calibration

activities will be intense Phase 1 – the scanning sky survey year – For this year, the

ISOC will also need to define the science plan– Basically this will mean optimizing the rocking strategy,

and of course assessing/mitigating the impact on the sky survey from any pointed observations or unusual instrument modes required for calibration data taking



Command Plan GenerationCommand Plan Generation

Lori BatorLori Bator



Command Plan Generation in the ISOCCommand Plan Generation in the ISOC

Describing what goes on in these boxes

From the Operations Concept Document (LAT-SS-01378)


(GSSC)

Operations Plan


Review




ISOC


Feedback

Mission Planning


ATS Commands

File Uploads

Command Procedures

Command Plan


Command Plan



Command PlanCommand Plan

Generated by CHS team Contains all LAT commanding requirements to fulfill a one-

week period of the Operations Plan– ATS Load commands – File loads

• Table uploads, configuration changes, FSW loads – Command procedures

• Commands requested to be sent in real-time Verify and validate command plan elements on testbed Sent to GSSC about 2 weeks prior to upload

– GSSC incorporates command plan elements into Preliminary ScienceTimeline

Changes that don’t impact the observing schedule or TDRS contacts can be sent up to 4 days prior to upload in time for GSSC to generate Final Science Timeline



Planning for One Week’s ActivitiesPlanning for One Week’s Activities

*Minor changes that don’t affect observing schedule or TDRS contacts

July 30

Monday Tuesday Wednesday Thursday Friday Saturday Sunday

31 August 1 2

GSSC Sends Preliminary

Activity Timeline to MOC

3

MOC Requests TDRSS Contacts

for the Week

4 5

6

ISOC Generates Command Plan

7 8 9 10

ISOC Sends Command Plan to

GSSC

11 12

13 14 15 16 17 18 19

Deadline for ISOC to Send Changes* to

Week

20

GSSC Sends Final Activity

Timeline to MOC

21 22

MOC Uploads ATS

23

ATS Goes Active

24 25 26

27 28 29 30 31 September 1 2



Typical Month of PlanningTypical Month of Planning

July 30

ISOC Begins Generating

Command Plan for Week C

Monday Tuesday Wednesday Thursday Friday Saturday Sunday

31 August 1 2

WEEK AATS Goes Active

3

Review Command Plans for Week B & C Send Command Plan for Week C

4 5

Deadline for ISOC to Send Changes for

Week B

6


Command Plan for Week D

7 8 9

WEEK BATS Goes Active

10

Review Command Plans for Week C & D Send Command Plan for Week D

11 12


Week C

13


Command Plan for Week E

14 15 16

WEEK CATS Goes Active

17

Review Command Plans for Week D & E Send Command Plan for Week E

18 19


Week D

20


Command Plan for Week F

21 22 23

WEEK DATS Goes Active

24

Review Command Plans for Week E & F Send Command Plan for Week F

25 26


Week E

27


Command Plan for Week G

28 29 30

WEEK EATS Goes Active

31

Review Command Plans for Week F & G Send Command Plan for Week G

September 1 2


Week F



StatusStatus

Continuing to finalize details of commanding process with GSSC and MOC– Weekly GOWG meetings– Ops TIMs– Operations Data Products ICD (492-MOC-009)– Operations Agreement

Documented in ISOC Operations Plan (LAT-SS-01378)

glast lat projectisoc cdr, 4 august 2004 document: lat-pr-04500section 4.11 glast large area...

Documents

lat science plan phase

glast lat projectisoc

monthly plan of lat

command plan

pointing of glast

science products level

command process slide

tdrss slide