FORCAST Line Operation #1

Pasquale Temi NASA-Ames

“Observatory Level” Line-

opsFORCAST Line-ops #1 is the first activity that involve an integrated test and a characterization plan at the Observatory LevelIt is indeed our first chance to test on ground the Observatory as an integrated system

FORCAST Line-ops #1 will contain Observatory elements that have not been formally verified. This Line ops represents an opportunity to perform planned tests that would establish the readiness of the various Observatory elements to proceed. For MCCS, it will represent the first time that significant new functionality has been integrated with aircraft and Telescope Assembly (TA) hardware and software. For the Science Instrument, it will also represent the first time that FORCAST software is integrated with MCCS software while controlling the SI hardware mounted on the TA

“Observatory Level” Line-ops Objectives

Determine to what extent the combined TA-MCCS-FORCAST integrated Observatory is ready for conducting the Short Science flight series #1 .

Enable the Science Instrument development team and Mission Operation team to assess the current capabilities of the Observatory for executing the science operations, in preparation for Short Science flight Series #1

System evaluation will be performed to ensure that system functions in the expected manner when placed in the intended environment.

Segment 2 – Tracking dates

TA ActivationFCF

2009

2010

  Science Flight   Platform Flight  TA Flight  Ground Testing  Data Analysis  Contingency Flight

ISF

FRR #3 AFSRB

Assumptions and Approach

• Line Op Definition:– FORCAST Line Op #1 is an Observatory-level evaluation for

SS1 and a risk-reduction activity• FORCAST Line Op #1 is not formal V&V “for credit”• Subsystems are not in formal SS1 configuration

• Observatory Configuration and Line Op Entrance Criteria: – MCCS (incl. EB4), TA, FORCAST are “SS1-like”– Detailed entrance criteria and configuration prerequisites are

given in the Plan and in forthcoming Test Procedures– Assume subsystem verifications, respective ICD verifications,

and PCA results are already available before onset of Line Op

• Requirements– Tests are against Observatory-level requirements of ES Level B

and of SE01-013 (down-selected for ES)

• Acceptance and Approvals:– Plans, Procedures, and Test Results will be placed under CM

and all accepted by SOFIA Program Chief Engineer– Detailed test procedures, available before TRR– Any PRs will be submitted to Program Chief Engineer;

Corrective Action/Deviation/Waiver will be in accordance with Program process

• Coordination:– Pasquale Temi is lead and POC– On-aircraft tests will be coordinated between Science, Platform

Engineering, and Aircraft Ops, in accordance with June 23, 2009 memo, “Coordinating Test Activities Onboard the SOFIA Aircraft”

– Ongoing weekly planning meetings with TA, MCCS, FORCAST and Ops representatives

– Final coordination is through Program Integration IPT

Assumptions and Approach

Observatory Level Line-ops Structure

SOFIA Observatory Integration Test Plan

for Line-ops #1

Cavity D

oo

r S

ystem

Telescope Assembly

Sci

ence

Inst

rum

ent

FO

RC

AS

T

MCCS

Line Operations #1 test is conducted at the Observatory level, with the Platform Systems configuration very close to the Short Science #1 configuration, and with FORCAST integrated with the TA and MCCS subsystems.

Short Science Configuration.Power distribution available at SI rack, rack patch panel and TA patch panel

SW at Engineering Build 4; all other subsystems at Short Science Configuration

Cavity door and TA aperture fully operational under MCCS control

Short Science #1 ConfigurationFully operational TA, balanced with FORCAST installed; Inertial stabilization Mode Available; Tracker available on all three images; SMA fully functional

Requires Support from:TA operators, FORCAST operators, MCCS operators, Mission Ops support, Aircraft Ops support

Test Plan - Structure

Approach1) List of requirements needed for ES (from Level B and -

013)2) Identify the appropriate (series of) test associated to

each requirement3) Identify SI flight scenarios4) Identify Mission Ops. flight scenarios 5) Write test Plan & Test Procedures 6) Prioritize the listObservatory check out and ICD functional check will asses if each

subsystem is ready for integration prior to line operations

Test Plan fields:Configuration/Environment:Prerequisites:Test Description:Exit Criteria:

Personnel Requirement:Estimated duration:Requirements:

Prerequisites MCCS

1. MCCS at Engineering Build 42. MCCS (EB4)-FORCAST SIL Test Completed3. Surrogate Data Acquisition System operational4. Platform and Experimenters Networks configured 5. NTP and IRIG-B operational6. TO and MD Workstations operational7. MADS audio data stored and available for transfer 8. MCCS TAIPS data stored and available for transfer9. MCCS Workstation and PIS data stored and available for transfer 10.MCCS Housekeeping stored and available for transfer 11.Science Transfer System available for connection to Experimenter

Network 12.Science Data Cache and Network available for data migration activities

Cavity door and TA aperture fully operational under MCCS control

Prerequisites - TA & SITA Prerequisites:1. Short Science #1 Configuration2. Fully operational TA, balanced with FORCAST installed; 3. Conical reflective secondary mirror button installed4. Inertial stabilization Mode Available; 5. Tracker available on all three imagers; 6. SMA fully functional (will have already been verified to move

reliably and repeatably through their whole range. Chopping performance will have already been thoroughly tested in the hangar using the LabView oscilloscope equipment).

SI Prerequisites:1. FORCAST fully operation in Short Science Configuration mounted on

the instrument flange2. Power distribution available at SI rack, rack patch panel and TA patch

panel3. Access to the backend of SI instrument4. Install and remove FORCAST calibration Box

“Observatory Level” Line-ops – TA Tests

5.2 TA Tests5.2.1 Basic Controllability and Housekeeping Evaluation5.2.2 TA Gyro Alignment and Quasi-static Flexible Body Compensation Check5.2.3 Off-Axis Pointing Accuracy Check5.2.4 TA Gyro Drift Check5.2.5 Coarse Drive Coupled Mode Evaluation

MCCS Centric Test Cases

Test Authors Dur Notes

Scen 0 – 1st Pointing A. Meyer 3 Night, door open, on tarmacInitialization of Sky to TA coord (ERF to IRF)

Scen 1 – Setup SI Boresight

R. Grashuis 2 Night, door open, on tarmacAlignment of SI Ref Frame to TA (SIRF to IRF)

Scen 3 – Unchopped Nods

R. Grashuis 1 Night, door open, on tarmacNodding between defined beams (for SS1, simple moves via goto)

Scen 4 – ROF Update

A. Meyer 3 Night, door open, on tarmacPrediction of time remaining and rewind of the Line of Sight to maximize time where Rotation of Field remains frozen during observations

Scen 5 – Chopper Setup

S. Adams 4 Night, door open, on tarmac2-pt chop @ various freq., throws, offsets, angles

Scen 6 – Chop & Nod S. Adams 3 Night, door open, on tarmacNodding and chopping

Coordinated Motion W. Miller? 6 Night, door open, on tarmacTracking aperture position relative to TA position

Prerequisites - TA & SI Tests with dependencies on night operations

MCCS Centric Test Cases

Prerequisites - TA & SI Tests with no dependencies on night operations

Some tests are not MCCS per se; however, they deal with transfer and ingestion of MCCS of data into the DCS

Test Authors Dur Notes

Administrative E. Moore/J. Rasmussen

2 No constraint (hangar/tarmac, door open/closed, day/night)MCCS login, print, receive images, print, etc.

Data Transfer N. Callis 3 No constraint (hangar/tarmac, door open/closed, day/night)Transfer of SI, MCCS, data to Transfer System

Data Ingestion R. Shuping 2 No constraint (hangar/tarmac, door open/closed, day/night)Archival from Transfer System into DCSExport from DCS

MCCS Test Case Sequencing

• Test Case Sequencing

14

Administrative

Scenario 0

Scenario 1

Scenario 5

Scenario 4

Coordinated Motion

Data Transfer

Data Ingestion

Scenario 3

Scenario 3 may be optional - it involves nodding, which for SS1/EB4, should only be TA positioning using standard

ta_pos.goto, which is tested in Scenario 0, although not in

application of nodding concepts

No constraint on night, door, or tarmac

On sky at night, door open

“Observatory Level” Line-ops – SI Tests

5.3 SI Tests5.3.1 FOR-HO-1: INF Pressure Test5.3.2 FOR-HO-2: Grounding Scheme Checkout5.3.3 FOR-HO-3: SMA Interface5.3.4 FOR-LO-1: Alignment of FORCAST to TA5.3.5 FOR-LO-2: SMA Focus5.3.6 FOR-LO-2a:Occulting Masks Test5.3.7 FOR-LO-3: Ground Bore Sight Determination5.3.8 FOR-LO-4: TA Emissivity5.3.9 FOR-LO-5: Chop and Nod Settle Times; Image Quality5.3.10 FOR-LO-6: Optimum Chop Frequency5.3.11 FOR-LO-7: Plate Scale5.3.12 FOR-LO-8: Asymmetric Chop5.3.13 FOR-LO-9: Pointing Stability5.3.14 FOR-LO-10: Header Population for Acquired Data5.3.15 FOR-LO-11: Data Reduction Pipeline Verification for C2N and C2ND Modes

“Observatory Level” Line-ops – Operational

Tests

5.4 Operational Tests (Simulated Flight Operational Scenarios: FORCAST operational scenarios integrated with OPS SIM #8 flight simulations)

5.4.1 FOR-LO-13: Flight Scenario for Determining Frame5.4.2 FOR-LO-14: Flight Scenario for Focus Determination5.4.3 FOR-LO-15: Flight Scenario of Standard Star5.4.4 FOR-LO-16: Flight Scenario for Science Object (standard chop and nod off source) 5.4.5 FOR-LO-17: Flight Scenario for Science Object (scan mode) - Waived - MCCS functionality not available until GREAT line ops5.4.6 FOR-LO-18: Flight Scenario for Science Object (quick step and stare mode)

Flight Plan with three legs will be generated, incorporating FORCAST scenarios

Briefed at pre-flight briefingImplemented on day one as part of the SIM #8

simulated flight

Test Sequence Test # Test Description Group Location Duration Parallel # days # nights Prerequisites

  DAY 1 - TA Hangar tests         1    

5.2.1 Basic controllability and HK eval TA Hangar 4       Needs MCCS h&s/w & TA configured

5.2.5 CD coupled mode eval TA Hangar 2       Needs TA 5.2.1

  Total Hours     6        

  DAY 2 - SI & MCCS Hangar tests         1    

5.1.1 Admin test case MCCS Hangar 2       Needs MCCS h&s/w & TA configured

5.1.9 data transfer MCCS Hangar 3 yes      

5.3.1 INF pressure test HO-1 Hangar -3 yes     Needs FORCAST installed

5.3.2 Grounding scheme check HO-2 Hangar 4       Needs FORCAST installed

5.3.3 SMA interface HO-3 Hangar 1       Needs SMA checkout complete

  Total Hours     7        

  NIGHT 1 - CDDS & SI tests           1  

5.3.4 Alignment of FORCAST to TA (pupil) LO-1 Line 2       Needs FORCAST hangar tests complete

5.3.6 Occulting Masks Test LO-2a Line 2       Needs pupil imaging

5.1.10 MCCS-TA-CDDS coordinated motion MCCS Line 6       Needs pupil imaging

  Total Hours     10        

  NIGHT 2 - TA & SI tests           1  

5.2.2 TA Gyro alignment and QS FBC check TA Line 1       Needs TA 5.2.1

5.2.3 off axis pointing accuracy check TA Line 1       Needs TA 5.2.1

5.2.4 TA gyro drift check TA Line 1       Needs TA 5.2.1

5.3.5 SMA FOCUS (unchopped) LO-2 Line 2       Needs FOR-LO-1

5.3.7 Ground Boresight determination LO-3 Line 4       Needs FOR-LO-2

  Total Hours     9        

  NIGHT 3 - MCCS tests           1  

5.1.2 scenario 0 - First Pointing MCCS Line 3       Needs TA, CDDS, basic SI complete

5.1.3 scenario 1- Set up SI Boresight MCCS Line 2       Needs scenario 0

5.1.4 scenario 3 - Unchopped nodding MCCS Line 1       Needs scenario 1

  Total Hours     6        

  NIGHT 4 - MCCS tests           1  

5.1.5 scenario 4 - ROF update MCCS Line 3       Needs scenario 1

5.1.6 scenario 5 - Chopper Setup MCCS Line 4       Needs scenario 1

  Total Hours     7        

Time line

  NIGHT 5 - SI tests           1  

5.3.9 chop & nod settle times, IQ LO-5 Line 4       Needs Scenario 3 & 5

5.3.10 optimum chop frequency LO-6 Line 2       Needs Scenario 5

5.3.12 asymmetric chop L0-8 Line 2       Needs Scenario 5

        8        

  DAY 6 - Ops Sim         1    

5.4.7 pre-flight Ops Hangar 4 yes     day shift on day of flight sim

  Total Hours     4        

  NIGHT 6 - Ops Sim           1  

5.4.8 flight simulation - night 1 Ops Line 6       Needs TA, CDDS, MCCS and some SI complete

  In-Flight Frame rates LO-13 flight 1   yes      

  In flight Focus (chopped) LO-14 flight 1   yes      

  In flight std star obs LO-15 flight 1   yes      

  In flight science object obs LO-16 flgiht 1   yes      

  In flight quick step obs LO-18 flight 1   yes      

  Total Hours     6        

  DAY 7 - Ops Sim & MCCS tests         1    

5.4.10 post flight Ops Hangar 1 yes     day shift on day after flight sim

5.1.8 data ingestion MCCS Hangar 2 yes      

5.1.9 data transfer MCCS Hangar 3 yes      

  Total Hours     6        

  NIGHT 7 - SI tests           1  

5.3.11 plate scale LO-7 Line 2       Needs FOR-LO-3, 5 & 6

5.3.13 pointing stability LO-9 Line 2       Needs FOR-LO-2

5.3.8 TA emissivity LO-4 Line 4       Needs CDDS complete

5.3.14 header population L0-10 Line   yes      

5.3.15 data reduction pipeline verification LO-11 Line   yes      

  Total Hours     8        

Test # Test Description Group Location Duration Parallel # days # nights Prerequisites

Time line

  DAY 8 - Ops Sim         1    

5.4.7 pre-flight Ops Hangar 4 yes     day shift on day of flight sim

  Total Hours     4        

  NIGHT 8 - Ops Sim           1  

5.4.9 flight simulation - night 2 Ops Line 6        

  In-Flight Frame rates LO-13 flight 2   yes      

  In flight Focus (chopped) LO-14 flight 2   yes      

  In flight std star obs LO-15 flight 2   yes      

  In flight science object obs LO-16 flight 2   yes      

  In flight quick step obs LO-18 flight 2   yes      

  Total Hours     6        

  DAY 9 - Ops Sim & MCCS tests         1    

5.4.10 post flight Ops Hangar 1 yes     day shift on day after flight sim

5.1.8 data ingestion MCCS Hangar 2 yes      

  Total Hours     3        

  NIGHT 9 - SI/Aircraft test           1  

5.3.16 emi/emc ground testing LO-12 Line 8       need more info on test duration

  Total Hours     8        

                 

  Totals         6 9  

  Contingency nights           5  

                 

Test # Test Description Group Location Duration Parallel # days # nights Prerequisites

Time line

  Aug Sept Oct Nov Dec Jan Feb Mar                                  Test Plan Draft                Status Meeting                Test Plan Final                Test Procedures                TRR                Line-ops #1                                 Quick Look Results                Final Analysis report