# Presentation: 672674

## Science Data Planning & Processing Review

***GODDARD SPACE FLIGHT CENTER***

***July 21, 1999***

*Final Review Version 07/20/99*

*New Millennium Program’s First Earth Observing Mission*

## Agenda

***Agenda***

***Introduction/Background/Mission Overview ******	******N. Speciale******	******15 min***
***Science Validation Overview******	******S. Ungar******	******10 min***
***Technology Validation Overview******	******N. Speciale******	******5 min***
***System Overview******	******N. Speciale******	******30 min***
***Ground System Status******	******D. Mandl******	******30 min***
***S/C and Instrument Operations******	******B. Trout ******	******15 min***
***Flight Dynamic Operations ******	******J. Howard******	******10 min***
***Mission Planning******	******T. Brakke******	******20 min***
***Data Processing Arch & Ops******	******R. Reider******	******20 min***
***Lunch/Spacecraft Tour******	******	******Noon - 1:00 p.m.***
***Science Element Status/Schedules***
***FDSS                                                       ******	******R. Defazio   ******	******15 min***
***TRW******	******C. Segal******	******25 min***
***SSC******	******V. Zanoni******	******15 min***
***SVF******	******L. Ong******	******20 min***
***MIT******	******J. Evans******	******20 min***
***GSFC AC******	******G. McCabe******	******15 min***
***EDC ******	******J. Boyd******	******15 min***
***Summary******	******N. Speciale******	******20 min***
***Panel Recommendations ******	******	******4:30 - 5:00 P.M***

## Review Purpose/Scope

***Review Purpose/Scope***

***To provide the overall status of EO-1 science data planning and processing and associated operations preparations.***
*Addresses concerns from the Delta MOR held in 1/99*
*Emphasis on the Science Planning and Processing*
*Flight operations was sufficiently discussed at the Delta MOR, some information may be repeated here for clarity **.*

## Review Goals

***Review Goals***

***That we understand the requirements, expectations and interfaces for the end-to-end EO- 1 science processing and planning system***
***That  we have end-to-end and element designs that will meet these requirements***
***That we have an valid operations concept***
***That we have enough schedule to complete the development and test it, if not we have a descope plan and have identified launch/early orbit functions that are necessary to complete first.***

## Review Board

***Review Board***

***Chris Stevens (NMP-JPL) Bryant Cramer, Pete Spidaliere, Dale Schulz, Joy Henegar, Steve Ungar, John Boyd (EDC), Paul Ondrus (ESDIS)***
***RFA process***
*Submit paper form or electronically from EO-1 web site by COB 7/22*
***Splinter groups and management discussions to be held on 7/22 and 7/23***

## Mission Overview

***Validate revolutionary technologies contributing to the reduction of cost and increased capabilities for future land imaging missions***
***Revolutionary land imaging instruments on EO-1***
*Hyperion*
*Advanced Land Imager (ALI)*
*Atmospheric Corrector (AC)*
***Revolutionary Spacecraft technologies on EO-1***
*X Band Phased Array Antenna (XPAA)*
*Pulse Plasma Thruster (PPT)*
*Light Weight Flexible Solar Array (LFSA)*
*Carbon-Carbon Radiator (CCR)*
*Enhanced Formation Flying (EFF)*
***More on website:  eo1.gsfc.nasa.gov***

***Mission Overview***

## Mission Overview

***Launching December 15, 1999 from Vandenberg Air Force Base on a Delta launch vehicle***
***Orbit: 705 km circular sun synchronous, 98.2 degree inclination***
***Flies one minute behind Landsat and collects nearly identical images for comparison purposes***
***For each image collected***
*Approximately 13 Gbits of scene data from Hyperion, ALI and AC is collected and stored on the on-board solid state data recorder at high rates per DCE. *
*When in range of ground station, data is transmitted to ground and forwarded via tape to GSFC for analysis and validation by EO-1 science and technology teams*
*3- 4 scenes (DCE’s ) collected and downlinked on daily basis*

***Mission Overview***

## Background

***EO-1 Mission ground operations concept changed radically with addition of Hyperion in 7/98***
*Higher visibility*
*More complex interfaces*
*Addition of commercial, DoD and Academia constituency *
***Delta Mission Operations Review covered MOC/FDF functions sufficiently***
*However full science planning and processing flow still not well defined.  *

## Background

***Delta MOR resulted in Request for Action to better define science planning and processing, requirements, interfaces and  data flow***
***In Feb 99’ formed EO-1 SDPWG , weekly meetings to address data planning and processing shortfalls.***
*Included all major elements (GSFC,TRW,MIT/LL,FOT,SSC,EDC)*
*Held face to face meeting in March 99’and  internal review April 99’*

## Background

***Since April 99,  made significant progress in baselining requirements, finalizing ICD’s and implementing and testing core requirements. ***
*** ******However, there are still some significant issues and areas of concerns (readiness) which may require additional resources or descoping of requirements to have launch ready science planning and processing system.***
***This review will hopefully surface all remaining issues and additional splinter groups will be formed  to tackle unresolved issues. ***

## Uniques Aspects ofEO-1 Science Processing System

***This is not a science mission, only data necessary to validate instrument technologies is required for mission success.  Science planning and processing system sized and costed for this expectation.***
***Small science team (15-20 investigators), selection based on fulfilling instrument validation goals.***
***Overall goal is to capture and process 85-90% of requested scenes for SVT and commercial interests. Therefore:***
*No extensive reprocessing of data is planned nor funded, minimal redundancy, no hot backups in place.*
*Processing timeframes are long (over two weeks during nominal ops)*
*Data quality assessment is minimal, only that necessary to quickly diagnose failure mechanisms to subsystem level are in place.*
*Rescheduling of  image is most likely recourse in case data is lost*
*Operations of processing system will be conducted on a 5/day a week, prime shift basis.*
*Limited budget and operations staffing*

## Science Validation Overview

***Science Validation Overview***

***Dr. Steve Ungar***

## Pictorial Overview of Science Objectives

***Pictorial Overview of Science Objectives***

## Relative Swath Widths

***Relative Swath Widths***

***EO-1 Footprint:   WRS-based scene 60 seconds behind L7***

**AC: 185-km wide x 170 km**

**ALI: 37.5-km wide x 170 km**

**Hyperion: 7.5-km wide x 170 km**

## Technology Validation Overview

***Technology Validation Overview***

***Nick Speciale***

## Technology Validation Overview

***Major technologies are in instrument and will be validated via paired scene comparison with Landsat 7 scenes***
***Other technologies (except EFF and PPT) are passive requiring only trending data periodically to provide necessary validation data.***
***NRA proposals selection based on creation of a  Science Validation Team to ensure that instrument technologies are completely validated and can eventually meet future Landsat 8 performance requirements***
***Instrument checkout team will provide first sixty day validation and characterization of instrument technologies. ***
***Lead technologists will support checkout and testing and validation of spacecraft technologies ***
***Metrics:  Validation plans completed by end of mission (1yr)***

## Mission Profile

- Launch	L+2mo	L+4mo	L+6mo	L+8mo	L+10m 	L+1yr

- Extended

## System Overview

***Nick Speciale***

## System Overview Agenda

***System Overview Agenda***

***Major Requirements/Definitions***
***Science data flow from S/C through G/S***
***Special data services***
***System Context***
***System Description***
***Issues/Concerns***

## Major Requirements

***Schedule best 3-4 of prioritized scene’s daily (17Gbits/scene or DCE).  Usually all 3 instruments will image same ground track simultaneously.***
***2-3 X-band downlinks daily to ground stations***
*Spitzbergen is prime G/S during nominal Ops period*
*Wallops is prime G/S during EOC.*
***Maximum of 80 Gbit of data per day processed by MOC to level zero DLT’s***
***Approx. 1000 DCE’s over mission life; 200 for commercial Hyperion users***
***Level 1R data processing based on SVT or commercial user request***

## Definitions

***Definitions***

_***Data Collection Event***_
***A scheduled data image collection which  usually (90% of time) involves simultaneous imaging by all three instruments covering a full L7 long track (apprx 17Gbits of data), includes all necessary dark, lights cals before and after actual ground scene imaging event.  ***
***AC - 185 x170 km swath***
***ALI - 37.5 x 185 km swaths***
***Hyp - 7.5km x 185km (about 9 Hyp. cubes)***
***Average of 3-4 DCE’s per day***

***The EO-1 high rate solid state recorder which captures DCE data from each instrument along with State of Health and ancillary data (only during DCE) from C&DH/ACDS system.  This data is organized into separate files and downlinked as separate virtual channel data (ie.  VC9/file id xxx is Hyp SWIR data from DCE event yyy)***
***The WARP can store about 48Gbits of data (3-4 DCE’s) before data must be downlinked and files released for new images***

***Wideband Advanced Recorder Processor***

## Definitions

_***Trended  Instrument SOH Data***_
***Since the WARP only captures instrument SOH data during the DCE (<5%) for output onto DLT tapes, instrument teams wanted particular instrument SOH parameters trended on 24 hr basis (conv to eng units).  This data can be accessed thru the MOC by the instrument checkout teams TBD hours after the recorded engineering data is received by the MOC.  All of this data is transmitted via the S-band link.***
_***Recorded Engineering Data***_
***The C&DH/ACDS system captures in its own SSR SOH/engineering data from all S/C instruments and subsystems over a 24 hour period.  This data will be downlinked daily and instrument checkout teams will have access to the data base.  MOC web based tools will  allow them to playback and process this data upon request for requested time periods.***

_***Metadata (Data About Data)***_
***Currently metadata definitions for EO-1 image data is defined by the instrument checkout teams (documented in ICD in HDF formats).***
***There is concern this may be insufficient for the eventual SVT team or for long term archive of EO-1 data via EDC.***
_***S-band Contingency Data***_
***The WARP can downlink stored DCE image data via a 2Mbps S-band link in case the X-band downlink fails.  This output will be used during the initial instrument checkout to speed processing of instrument data (less than one shift turnaround) to ensure proper initial instrument operations.  Small files (<125Mbytes) will be downlinked via this method, processed and ftp transferred to instrument c/o teams during first 7 days of inst turnon.***

## Slide 23

## Science Data Processing Products

***Science Data Processing Products***
***and General Timelines***

## Special Data Services

***To support timely instrument checkout and image reconstruction, the following special data output products were agreed to for all instrument teams. (Individual ICD for each interface define the particular data formats).***
*A subset of  Instrument and S/C SOH and engineering data collected by WARP during each DCE shall be processed to engineering units.  A special file (in HDF format) will be written to each DLT with this data, *
*A set of trended (sequential print) SOH parameters will be trended daily in engineering units from received stored engineering data (from ACDS ) and made accessible electronically to instrument checkout teams*
*All recorded SOH engineering data will be made accessible electronically  for processing into engineering units via a web based interface.  *
*During initial instrument turn on and ops (first few days) the S-band contingency mode utilized to support quick turnaround deliverery of L0 processed small image sets (<125Mbytes) to instrument teams (see DPS timeline for S-band contingency processing).*
*To expedite instrument validation after this initial turnon the Wallops G/S will be utilized to for collection of full images via X-band  and expedited delivery  and  turnaround will occur in the DPS (see DPS timeline for EOC processing)  *

## Science System Context(L+2  through L+12)

## System DescriptionGround Stations Science Planning and Processing Functions

***System Description****Ground Stations Science Planning and Processing Functions*

***Provides X-band down linked data to the MOC via tape (mailed to MOC twice per week during normal ops)***
***Provides raw X-band data storage for up to 30 days***
***Provides S-band data interface to the MOC***
*Electronically transfers recorded State of Health (SOH) post pass*
*Provides real-time data to the MOC*
*Provides early orbit and contingency operation S-band science data to the MOC electronically post-pass*
***Real time and post pass data quality monitoring statistics.***

## Ingests AMPEX DCE tapes from the EPGN
Processes AMPEX DCE tapes to HDF Level 0 data files for ALI, AC, and Hyperion
Processes selected DCE housekeeping from WARP data to engineering units onto DLT in HDF format.
Provides tapes (DLT) of the Level 0 data products (including the DCE housekeeping files) to the instrument teams  
Overnight Fed Ex. Once per day in the L to L+2 month time
Distributed twice a week after L+2 months
Provides the capability to provide small (<125MB) level 0 data sets electronically during initial instrument checkout (first few days) and during  contingencies.
Provides access recorded spacecraft SOH data electronically 
Provides access to selected instrument SOH trending data electronically throughout mission

***Ingests AMPEX DCE tapes from the EPGN***
***Processes AMPEX DCE tapes to HDF Level 0 data files for ALI, AC, and Hyperion***
***Processes selected DCE housekeeping from WARP data to engineering units onto DLT in HDF format.***
***Provides tapes (DLT) of the Level 0 data products (including the DCE housekeeping files) to the instrument teams  ***
*Overnight Fed Ex. Once per day in the L to L+2 month time*
*Distributed twice a week after L+2 months*
***Provides the capability to provide small (<125MB) level 0 data sets electronically during initial instrument checkout (first few days) and during  contingencies.***
***Provides access recorded spacecraft SOH data electronically ***
***Provides access to selected instrument SOH trending data electronically throughout mission***

***System Description****MOC**Science Processing Functions*

## Provides orbit/attitude data to the Mission Planning Office to aid in planning and to the instrument/science teams
Receives a prioritized schedule of prime/alternate targets from the Mission Planning Office, updates to long term plan received weekly
Ingests NCEP cloud predicts to remove scenes from plan
Accesses the Landsat 7 target list schedule to ensure paired scenes are scheduled with L7
Provides image tracking database updates to the Mission Planning Office on DCE status:
Includes return link quality information
DCE scheduling information
DCE processing status

***Provides orbit/attitude data to the Mission Planning Office to aid in planning and to the instrument/science teams***
***Receives a prioritized schedule of prime/alternate targets from the Mission Planning Office, updates to long term plan received weekly***
***Ingests NCEP cloud predicts to remove scenes from plan***
***Accesses the Landsat 7 target list schedule to ensure paired scenes are scheduled with L7***
***Provides image tracking database updates to the Mission Planning Office on DCE status:***
*Includes return link quality information*
*DCE scheduling information*
*DCE processing status*

***System Description****MOC**Science Planning Functions*

## Consists of *Mission Scientist, Mission Technologist and Operations Director (during nominal ops)
Responsible for updating long term scene acquisition plan (accepts inputs from MSO and Stennis for commercial image requests)
Submits prioritized scene list to MOPSS, resolves with MOPSS schedule conflicts, revises Long Term Acquistion Plan.

Note: 
	During EOC, mission planning office is chaired by mission manager and consists of mission director, mission technologist, instrument checkout team representatives and spacecraft checkout team representative

***Consists of *Mission Scientist, Mission Technologist and Operations Director (during nominal ops)***
***Responsible for updating long term scene acquisition plan (accepts inputs from MSO and Stennis for commercial image requests)***
***Submits prioritized scene list to MOPSS, resolves with MOPSS schedule conflicts, revises Long Term Acquistion Plan.***
*Note: *
*	**During EOC, mission planning office is chaired by mission manager and consists of mission director, mission technologist, instrument checkout team representatives and spacecraft checkout team representative*

***System Description****Mission Planning**Office*

## System DescriptionMissionScienceOffice

***Receives scene and calibration requests from the MPO.***
***Receives scheduling guidelines and priorities from the MPO.***
***Submits prioritized scene list to MOPSS, resolves with MOPSS schedule conflicts, revises Long Term Acquisition Plan.***
***Provides ALI and AC performance assessments after Checkout phase.***
***Provides assessments for the processed images for updating the LTAP.***

***System Description****Mission**Science**Office*

## System DescriptionScience Validation Facility

***Provides level 0 and/or level 1 products to the SVT.***
***Provides ALI MS/PAN level 1 processing upon SVT request.***
***Provides AC level 1 processing upon SVT request after Checkout phase.***
***Requests HSI Level 1 data from TRW for distribution to SVT.***
***Receives calibration coefficient updates from MIT/LL.***
***Provides the level 0 data archive for the life of the mission.***

***System Description****Science Validation Facility*

## Ingests Level 0 data provided by the MOC
Produces Hyperion Level 1data for all data received
Provides Hyperion scene and calibration requests to the Mission Planning Office
Provides Level 1 data and associated metadata to the SVF upon request
Receives Level 1 AC or ALI products from the SVF upon request for comparisons 
Provides capability to access the following electronically from the MOC:
Recorded SOH data made available for early orbit and on contingency basis
Selected trending data made available electronically by the MOC 
Flight Dynamics products
Small DCE data files (<125MB) during initial instrument c/o

***Ingests Level 0 data provided by the MOC***
***Produces Hyperion Level 1data for all data received***
***Provides Hyperion scene and calibration requests to the Mission Planning Office***
***Provides Level 1 data and associated metadata to the SVF upon request***
***Receives Level 1 AC or ALI products from the SVF upon request for comparisons ***
***Provides capability to access the following electronically from the MOC:***
*Recorded SOH data made available for early orbit and on contingency basis*
*Selected trending data made available electronically by the MOC *
*Flight Dynamics products*
*Small DCE data files (<125MB) during initial instrument c/o*

***System Description****TRW*

## Functional Description:
Provides ALI validation and verification for the first 60 days
Provides backup storage capability for the MS/PAN Level 0 processed EO-1 data for mission life
Provides ALI scene and calibration requests to the Mission Planning Office during the checkout phase
Provides calibration coefficient updates to the SVF during the checkout phase only
Additional Support:
MIT/LL provides the ALI Level 1 processing software to the SVF who will operate the software throughout the mission
MIT/LL will provide the SVF with support during the checkout phase
Provides capability to access the following electronically from the MOC
S band SOH made avail for early orbit and contingency basis.
Selected trending data made avail by MOC
Flight Dynamics Products
Small DCE files (<125MB) during initial instrument c/o.

***Functional Description:***
*Provides ALI validation and verification for the first 60 days*
*Provides backup storage capability for the MS/PAN Level 0 processed EO-1 data for mission life*
*Provides ALI scene and calibration requests to the Mission Planning Office during the checkout phase*
*Provides calibration coefficient updates to the SVF during the checkout phase only*
***Additional Support:***
*MIT/LL provides the ALI Level 1 processing software to the SVF who will operate the software throughout the mission*
*MIT/LL will provide the SVF with support during the checkout phase*
***Provides capability to access the following electronically from the MOC***
*S band SOH made avail for early orbit and contingency basis.*
*Selected trending data made avail by MOC*
*Flight Dynamics Products*
*Small DCE files (<125MB) during initial instrument c/o.*

***System Description****MIT /**Lincoln Lab*

## Functional Description:
Ingests LZP data provided by the MOC on DLT during first 60 days.
Submits AC scene and calibration requests to the MPO, and provides image tracking database updates following processing of AC Level 0 data.
Receives Level 1 Hyperion or ALI products from the SVF for comparisons
Produces AC Level 1 data and associated metadata during EOC upon request of the SVF (the SVF will assume this functionality after EOC for the duration of the mission)
Additional Support:
The GSFC AC will provide the SVF with the Level 1 processing software after performance assessment of the ACCS
Provides capability to access the following electronically from the MOC:
S band SOH made avail for early orbit and contingency basis.
Selected trending data made avail by MOC
Flight Dynamics Products
Small DCE files (<125MB) during initial instrument c/o

***Functional Description:***
*Ingests LZP data provided by the MOC on DLT during first 60 days.*
*Submits AC scene and calibration requests to the MPO, and provides image tracking database updates following processing of AC Level 0 data.*
*Receives Level 1 Hyperion or ALI products from the SVF for comparisons*
*Produces AC Level 1 data and associated metadata during EOC upon request of the SVF (the SVF will assume this functionality after EOC for the duration of the mission)*
***Additional Support:***
*The GSFC AC will provide the SVF with the Level 1 processing software after performance assessment of the ACCS*
***Provides capability to access the following electronically from the MOC:***
*S band SOH made avail for early orbit and contingency basis.*
*Selected trending data made avail by MOC*
*Flight Dynamics Products*
*Small DCE files (<125MB) during initial instrument c/o*

***System Description****GSFC AC*

## Provides science validation for the EO-1 mission
Provides requests for scenes to the MPO
Requests and receives AC, ALI, or Hyperion, Level 0 or Level 1 products from the SVF

***Provides science validation for the EO-1 mission***
***Provides requests for scenes to the MPO***
***Requests and receives AC, ALI, or Hyperion, Level 0 or Level 1 products from the SVF***

***System Description****Science Validation Team (SVT)*

## System DescriptionStennisSpaceCenter

***Receives and processes Hyperion data orders from commercial applications partners for submission to MPO.***
***Coordinates processing of Hyperion Level 1 products for commercial applications partners ***
*Receives level 0 and level 1 Hyperion products from TRW*
*Provides level 0 and/or level 1 Hyperion products to commercial applications partners*
*Provides the level 0 and level 1 Hyperion data archive for commercial  partners throughout the life of the mission*

***System Description****Stennis**Space**Center*

## Provide the long-term archive of EO-1 level 0 processed data and level 1 processed data after mission completion
Provide public access to EO-1 data after mission completion

***Provide the long-term archive of EO-1 level 0 processed data and level 1 processed data after mission completion***
***Provide public access to EO-1 data after mission completion***

***System Description****EDC **(Funding Not Yet Approved)*

## System Documentation Status

## System Level Issues

***Volume of S-band contingency data use during first 60 days. ***
***EPGN reliability (Landsat problems)***
***Data and metadata formats***
*Not yet reviewed by science NRA team or representatives.  Being reviewed by L7 experts at this time. Maybe insufficient once SVT is in place.*
***Sustaining Engineering Resources for Science Processing ***
***SSC and EDC interfaces not defined at this time.***
***Turnaround time for from image collection on S/C to Level 0, QA assessment (could be more than 16 days during nominal ops)***
***MIT / LL support for SVF proc. Where are majority of images processed***

## Areas of Concern

***Testing and validating system: ***
*Not all requirements will be tested*
*Short schedule, few dedicated opportunities, tied heavily to S/C usage*
*Operational testing just started, individual pieces tested but not integrated and operated together yet*
*DPS readiness, performance  and resources*
*SVF readiness and resources*
***Operations timeframes (can we nominally move plan and process data within a 16 day repeat cycle) - not likely based on current timelines***
***No testing planned with other than nominal (error free) data at this time.***

## Ground System Status

***Ground System Status***

***Dan Mandl***

## Overview of EO-1 Ground System and Data Flow

***Overview of EO-1 Ground System and Data Flow***

## EO-1 Ground Document Tree

## Ground StatusNetworks

***Ground Status****Networks*

***Wallops Ground Station operational (Landsat, Quicksat)***
*Need to integrate AMPEX Tape recorders for X-Band due 9/99*
***Alaska Ground Station operational (Landsat)***
*Need to integrate Data Quality Monitor(DQM) to monitor X-Band downlink statistics due 10/99*
***Svalbard Ground Station operational (Landsat, Quickscat etc.)***
*Need to integrate DQM to monitor X-band downlink statistics due 10/99*
***McMurdo Ground Station operational (Landsat)***
***SAFS needs to be configured for EO-1***
***WOTIS ready***
***MOC connection to closed IOnet due 7/30/99***
*Security Plan approved by Networks Security Officer*
*Firewall connection to FEDS in MOC due 7/30/99*
***Space Network (TDRSS) ready***
*WSC Data Interface Service Capability (WDISC) (telemetry and command I/F) operational (FUSE)*
***C-Band tracking - coordination to get services from Air Force in progress****** ***

## ASIST 7.0 operational
ASIST 7.1 (launch release) in developers testing, due to be released 7/23/99
Capability to format engineering data into HDF format for DPS
Special ASIST release to allow viewing of any page over the internet with authentication of users (SAMMI Sendera) due 8/30/99 (not launch critical)
Front End Data System (FEDS) 6.2 operational
FEDS 7.0 (launch release) due to be released 7/30/99
Capability to do Ground Station interface (SMEX style header over IP)
Ability to select ground station for cross overs

***ASIST 7.0 operational***
***ASIST 7.1 (launch release) in developers testing, due to be released 7/23/99***
*Capability to format engineering data into HDF format for DPS*
***Special ASIST release to allow viewing of any page over the internet with authentication of users (SAMMI Sendera) due 8/30/99 (not launch critical)***
***Front End Data System (FEDS) 6.2 operational***
***FEDS 7.0 (launch release) due to be released 7/30/99***
*Capability to do Ground Station interface (SMEX style header over IP)*
*Ability to select ground station for cross overs*

***Ground Status****Core Ground System*

## DPS 2.0 released 7/15/99
Capability to flow data from each of the instruments through the WARP to the DPS.  Produce DLT tapes with instrument data HDF formatted
DPS release 3.0 due 9/15/99
Integrate hardware de-interleaver being built by Code 564
Delivery of de-interleaver due 8/15/99
Enhance error conditions handling
Integrate engineering data in HDF format into the DLT tapes with the science data
Make any corrections necessary to fix any performance deficiencies discovered in testing during July/August 1999

***DPS 2.0 released 7/15/99***
*Capability to flow data from each of the instruments through the WARP to the DPS.  Produce DLT tapes with instrument data HDF formatted*
***DPS release 3.0 due 9/15/99***
*Integrate hardware de-interleaver being built by Code 564*
*Delivery of de-interleaver due 8/15/99*
*Enhance error conditions handling*
*Integrate engineering data in HDF format into the DLT tapes with the science data*
*Make any corrections necessary to fix any performance deficiencies discovered in testing during July/August 1999*

***Ground Status****Data Processing System (DPS)*

## Ground Status

***Mission Operations Planning and Scheduling System***
*MOPSS 3.1 operational*
*MOPSS 4.0 (launch release) due to be released 8/15/99*
*Process NCEP cloud cover data*
*Fix some discrepancies*

## FDSS 1.0 (STK, AUTOCON-G, ADS) operational
FDSS 2.0 (AUTOCON-G, ADS, RTADS) operational
FDSS 3.0  (FREEFLYER, AUTOCON-G) operational
FDSS 4.0  (STK, ADS, RTADS, MMU, CALMAN, PODS, INTRACK, FRU) operational
FDSS 5.0 (Science Planning Algorithm, AUTOCON-G and CALMAN Updates) (launch release) due to be released 7/30/99
Continuing work
FDSS Autoproducts (non-launch critical) - will automate most of the FDS functions due for release in fall
Procedures for Instrument Detector Alignment/Spacecraft Attitude Correction

***FDSS 1.0 (***_***STK***_***, ***_***AUTOCON-G***_***, ***_***ADS***_***) operational***
***FDSS 2.0 (***_***AUTOCON-G***_***, ***_***ADS***_***, RTADS) operational***
***FDSS 3.0  (FREEFLYER, ***_***AUTOCON-G***_***) operational***
***FDSS 4.0  (***_***STK***_***, ADS, RTADS, ***_***MMU***_***, ***_***CALMAN***_***, PODS, INTRACK, FRU) operational***
***FDSS 5.0 (***_***Science Planning Algorithm***_***, AUTOCON-G and ***_***CALMAN***_*** Updates) (launch release) due to be released 7/30/99***
***Continuing work***
*FDSS Autoproducts (non-launch critical) - will automate most of the FDS functions due for release in fall*
*Procedures for Instrument Detector Alignment/Spacecraft Attitude Correction*

***Ground Status****Flight Dynamics Support System (FDSS)*

## Ground Status

***Spacecraft Emergency Response System (SERS)***
*In process of being configured.  Will be used to beep FOT during Normal Operations phase when certain limits exceeded and no one is in the MOC*

## Figure 5.2..  EO-1 Data Link for Testing, Launch and Early Orbit Configuration as of 6-24-99

**Figure 5.2..  EO-1 Data Link for Testing, Launch and Early Orbit Configuration as of 6-24-99**

- NASA Closed IOnet

**SGS**

**WGS**

**AGS**

**MGS**

**TDRS**

- NASA Open
-   IOnet

**VAFB**

**Firewall**

**GSFC**
**SAFS**

**WOTIS**

**Swales**

**EO-1**
** ****S/C**

**EO-1 MOC**
- (b14 r N285)

**FEDS**

**FEDS**

- MOC LAN

**2 MOPSS/**
**FDS Wkstns**
**(HP/UX)**

**SOTA (**b14 rE259 A,B,C)

**3 ASIST**
**Wkstns**
**(AIX)**

**Planning Area**
- (b14 rE259 D)

**EO-1 Launch Support Area**
- (b14 r N285)

- AMPEX Tape
- Drive

**FEDS**

**ASIST at**
**HOPC**

**ASIST at**
**MIT/LL**

- 256 Kb

- 256 Kb

**FEDS**

**DHDS**

- X-Term

- X-Term

- Note:  There
- will be 12-15
- X-Terminals

**3 ASIST**
**Wkstns**
**(AIX)**

**ASIST**
**(AIX)**

**3 PC’s/**
**X-Term**
**(NT)**

**ASIST**
**Wkstn**
**(AIX)**
**for Sendera**

**2 PC’s**
**SERS Servers**
**NT**

**2 PC’s**
**Mongoose**
**Simulator**

**2 PC’s**
**Sendera **
**Servers (NT)**

**Firewall with user authentication (use for Sendera)**

- To open Internet

## Slide 52

## Ground StatusFacilities & Equipment

***Ground Status****Facilities & Equipment*

***MOC at GSFC in building 14 room N285***
***Special Operations and Test Area (SOTA) used for L&EO and prelaunch testing for subsystem engineers, project personnel other than FOT and instrumenters.  Availability scheduled for 9/1/99***
***5 of 9 ASIST workstations installed, remainder to be completed by 8/30/99***
***1 of 3 FEDS installed, 1 on order and the other being used in I&T***
*FEDS are used both for command and control; and data processing*
***Digital History Data Storage (DHDS) installed***
***AMPEX tape drive unit installed***
*Dedicated 256 Kb line to TRW & ASIST workstation installed, complete*
*Dedicated 256 Kb line to Lincoln Lab due to be complete approximately 7/30/99, ASIST workstation installed*
*1 of 2 MOPSS/FDSS workstation installed, the other one to be brought over after development complete*
*6 of 11 PC/NT installed*
*2 of 3 FDSS PC’s*
*2 of 2 PC’s for Simulator*
*2 of 2 PC’s for SERS*
*0 of 2 PC’s for Sendera (Serves MOC displays over Internet)*
*0 of 2 PC’s for Remote User authentication *

## Mission Readiness Test Status

***T1  Basic Telemetry and Command Test completed 4/99***
***T2  MOPSS-CMS-ASIST-S/C completed 5/99***
*Daily Activity Plan*
*Activities Timeline (modifiable)*
*Support Maneuver Planning*
*Support for Image Taking*
*Support for Calibration Activities*
*Command Loads*
***T3  Hyperion/AC/ALI-WARP-RF GSE-DPS-TRW/LL/ACCD to be completed by July 22(CPT #2)***
*Takes an image or test pattern from instrumentation to ground via WARP to the DPS.  Processed data tranformed to HDF on DLT’s and sent to instrumenters*
***T4  RF Compatibility to be completed by 8/15/99***
***TX Science Processing Testing (end-to-end planning and processing)***

## Mission Readiness Testing Status

***T5  Network I/F tests with MOC almost completed on open IOnet 6/99***
*WOTIS Planning I/F Test*
*Tracking test using COBE*
*Command and Telemetry data flow using IP*
*Ground Network I/F*
*Space Network I/F*
*Test AMPEX tape from Alaska ground station read on our AMPEX tape unit*
*SAFS test not done because not connected to closed side and not configured yet*
*Repeat all of the above tests once connected to Closed IOnet due to be completed by 8/30/99*
***T6  WTR I/F Test to be completed approximately Oct/Nov 99***
***T7 fully integrated end-to-end replaced by Simulation exercises***

## Simulation Status

***M1 Launch & Early Orbit Simulation due to be completed 8/15/99***
***M2  Normal Operations Simulation due to be completed 8/30/99***
***M3  Contingency Operations Simulation to be completed***
***M4  Science Data Flow Sim  9/30/99***
*Exercise the science data handling on the ground*
*This Simulation has just been proposed so details have not yet been agreed upon *
***M5  Launch Dress Reheasal 10/30/99***

## Operations Preparations Status

***Completed first Mission Operations Review 11/5/98***
***Completed Operations Concept 1/6/99***
*Mission Procedures Document Vol 1, Operations Concept on EO-1 web site*
***Completed Delta Mission Operations Review 1/28/99***
*20 RFA’s generated*
*Solutions generated for all RFA’s, target to close all RFA’s by 8/15/99*
***Conducted 4 Operations Working Groups***
*Normal Operations completed 11/5/99*
*Launch & Early Orbit completed 12/4/99*
*Roles & Responsibilities completed 1/5/99*
*Spacecraft contingency operations  completed3/5/99*
*Instrument and Technology operations completed 4/8/99*
*Trending conducted and completed informally 4/30/99*

## Operations Preparation Status

***Mission Procedure Documents Vol 2, Detailed Operations Plan - 1st cut November 1999 with ongoing updates***
*Constraints DB by Pre Ship Review*
*Procedures  11/99*
*Displays  11/99*
*DB Frozen by pre-ship review*
*Launch handbook appendix*
*Staffing allocation between MOC and WTR*
*Completed Mission Sequence for first 8 days*
*Completed Mission Activities for first 8 days*
*In process of completing Script for first 8 days due 8/7/99*
*Develop Mission Sequence for next 52 days of L&EO, Instrument checkout, date to be completed TBD*
*Launch Handbook Appendix (con’t)*
*Develop Mission Activities for next 52 days, date to be completed TBD*
*Develop Mission Script for next 52 days, date to be completed TBD*
***FOR/ORR due to be completed 10/20/99***

## S/C and Instrument Operations

***S/C and Instrument Operations***

***Bruce Trout***

## Normal Ops Command Requirements

*Instrument Data Collection Events – up to 4 / day*
*Instrument Solar Cal - weekly (Hyperion), monthly (ALI, AC)*
*Combined Instrument Lunar Cal - 3 / month (FM, FM +/- 6 days)*
*Orbit Maneuvers to maintain L7 co-fly profile - ~weekly*
*L7 orbit vector Uplink - Daily (in ATC load) *
*Performance of Ground Contacts (2 -3 per day) to allow :*
*Command operations *
*R/T and P/B SOH data retrieval and satellite monitoring*
*Science data downlink via X-Band*
**(Additional contacts for Maneuvers, Cals, and Contingencies)*
**(Additional contacts during L&EO)*
*Performance of Technology Validation Operations*
*ATC load Uplink - daily (5 days / week) *

## DCE Summary 

***DCE Summary ***

## Planned Ground Image Scenarios 

***Combined ‘Paired’ scene - image tied to WRS grid***
***‘******Hyperion’ scene - location tied to lat / long / duration***
***Landsat - 7 stereo image ***
***Will support following  :***
*Differing image duration*
*Various permutations of instruments on*
*Multi DCE per turn on*

## Combined Ground Image Profile

## Lunar Scan Raster Profile

***Lunar Scan Raster Profile***

## Lunar Scan Data Collection Profile

## Instrument Solar Cal Highlights

## Flight Dynamic Operations

***Flight Dynamic Operations***

***Joe Howard***

## Flight Dynamic Operations

***Flight Dynamic Operations***

***Launch and Early Orbit Operations:***
* **Four ascent maneuvers planned based on nominal injection on December 15th*
*Nominal Ascent Maneuver Dates:   Dec 18, Dec 20, Dec 22, Dec 28*
***Co/Fly with LS-7***
*   **LS-7 maneuvers will be once per week on Tuesdays*
*   **EO-1 maneuvers will be once per week on Thursdays*
***Generation of Ops Predicts***

## Cal Slews 
S/W in place to plan Lunar, Solar, and Deep Space Cals
Lunar Cals will be planned for 3 per Month (FM , FM + 6, FM - 6)
Solar Cal Slews will be planned for once / month
Deep Space Slews will be as needed - 3 / mission (ALI)
Momentum Management and Attitude Slew Planning
Latest version of MOPSS contains Momentum Management Utility

*S/W in place to plan Lunar, Solar, and Deep Space Cals*
*Lunar Cals will be planned for 3 per Month (FM , FM + 6, FM - 6)*
*Solar Cal Slews will be planned for once / month*
*Deep Space Slews will be as needed - 3 / mission (ALI)*
***Momentum Management and Attitude Slew Planning***
*Latest version of MOPSS contains Momentum Management Utility*

***Flight Dynamic Operations****(continued)*

## Mission Planning

***Mission Planning***

***Tom Brakke / Bruce Trout***

## MPO Responsibilities

***The MPO shall receive DCE, solar calibration, and lunar calibration requests from the Science Validation Team (SVT), Lincoln Lab, TRW, AC Instrument Data Analysis Team, and SSC (commercial requests).  ***
***The MPO shall approve and submit requests to the MSO.***
***The MPO shall provide scheduling guidelines and priorities to the Mission Science Office.***
***The MPO shall maintain the Image Tracking Database.***

## Slide 72

##  Scene Acquisition Request Process

## MSO Database Outline

***Request page***
*PI information*
*Request ID*
***Master Scene List page ***
*Scene attributes *
*geographical coverage*
*Sensors*
*S/C attributes*
*momentum management*
***Schedule Scenes page***
*Time of requested acquisition*
*Priorities*
*Scheduling, re-scheduling, de-scheduling of scenes*

## Science Planning Timeline

## EO-1 / L7 ‘Daily’ Planning Coordination

## Image Tracking Data Base

*Image Tracking Data Base*

*SVF*

*TRW*

*MOC*

_***Hyperion***_
*Level 0 QA *
*Level 1 proc. *

*Level 0 QA*
*Level 1 status for ALI & AC*

*DPS Status*

*DPS*

*MOPSS 1*

*DCE Sched Status*

*G/S Status*

## Data Processing Architecture and Operations

***Data Processing ******Architecture and Operations***

***Rich Reider / Rusty Whitman***

## Major DPS Operational Requirements

***Process to L0 DLT’s  and distribute, up to four days of DCE’s within two prime working shift’s  during nominal operations period.***
***Process to L0 DLT’s and distribute, upto  to 3 DCE’s in one prime operating shift during initial instrument checkout period.***
***Perform front end processing (F/S, R/S, virtual channel statistics) for each D/L session.  Perform QA assessment with Ground Station DQM file.***
***Process onto DLT’s the following files, MS/PAN HDF, AC HDF, Hyperion HDF and DCE SOH HDF files.***
***Provide capability during initial instrument checkout to process small LZP HDF output files (<125Mbytes) (from S-band contingency path) to instrument checkout teams (ftp pull)***
***Provide 24hr trended instrument SOH parameters via FTP transfer on a daily basis.***
***Perform DCE SOH and ancillary data conversion to files (in HDF format) onto DLT’s.***
***Perform gross level HDF file quality checks before creation and shipment of DLT tapes.***

## Contingency Data Flow Diagram

## Normal Data Flow Diagram

## DPS Architect Diagram

## Nominal Ops Processing Timeline

## Early Orbit Operations Timeline

## Normal DPS Processes Timing

*Assuming:*
*4 DCEs/day   (12 min each / including fill data ) *
*4 days of DCEs per Ampex Tape  *
*Total  ~ 30-40 Gbytes Science Data*
***Ingest Ampex Tape Data******	******~ 4-5 hrs***
***Separate by File ID,  Sort by VC,******	******~ 2 hr***
***Generate Intermediate Files***
***Verify DQM & WARP Statistics******	******~ 1 hr***
***Generate ( ALI, AC, HYP, SOH ) HDF Files******	******~ 3 hrs***
***Quality Check HDF output Files******	******~ 1 hr***
***Create 4 DLT Tapes ( ALI, HYP, SVF, MOC )******	******~ 3 hr (off-shift)***
***Label and Ship DLT Tapes******	******~ 2 hrs***
***Update Image Tracking Catalog******	******~ 1 hr***
***Total Processing Time ******	****** ~ 14 - 17  hrs***

## Contingency DPS Processes Timing

*Assuming:*
*3 DCEs/day   (12 min each / including fill data ) *
*1 day of DCEs per Ampex Tape  *
*Total  ~ 6 Gbytes Science Data*
***Ingest Ampex Tape Data******	******~ 1 hr***
***Separate by File ID,  Sort by VC,******	******~ 1 hr***
***Generate Intermediate Files***
***Verify DQM & WARP Statistics******	******~ 1/2 hr***
***Generate ( ALI, AC, HYP, SOH ) HDF Files******	******~ 1 hr***
***Quality Check HDF output Files******	******~ 1 hr***
***Create 4 DLT Tapes ( ALI, HYP, SVF, MOC )******	******~ 1 hr***
***Label and Ship DLT Tapes******	******~ 1/2 hr***
***Update Image Tracking Catalog******	******~ 1/2 hr***
***	******Total Processing Time******	******~ 6 1/2 hrs***

## S-Band SAFS Processes Timing

*Assuming:*
*(~ 12 min passes ) *
*Approximately 125 Mbytes*
*(Minimal QA Assessment will be performed)*
***Ingest Real-Time Data******	******~ 1/2 hr***
***Station Transfers Data Files to SAFS Post-Pass******	******~ 2 hrs***
***Data Ready Notice (DRN) - via email***
***DPS retrieves Data Files ******	******~ 1/2 hr***
***Data are Available to Users***
***DPS Process to HDF Files******	******~ 1 hr******	***
***Total Processing Time******	******~ 4 hrs***

## DPS Contingency Modes

***Fall back to failure of one DPS processing system is to process is to run data through one DPS.  Adds 3-4  hours of processing time.***
* **Pass 1  I channel data*
* **Pass 2  Q channel data *
***Second fall back position is to run data through software front end processing***
* **this will add 10-20 hrs of processing per AMPEX tape*
***DPS Staffing***
*1 person prime shift during nominal operations supported by FOT backup*

***Robert DeFazio / Richard Luquette / Sally Godfrey***

***EO-1 Flight Dynamics Support Subsystem******Science Products***

## Agenda

***FDSS Functional Requirements for Science Products***
***FDSS Products, Architecture and Data Flow***
***Current Status***
***Issues & Comments***

## EO-1 FDSS Science Products Requirements

***Provide access to EO-1 orbit and attitude products that aid in the planning, calibrating and data processing of EO-1 imaging; ***
***Develop science planning aid algorithms for use by the Mission Science Office and the Mission Operations Planning and Scheduling System;***
***Provide assistance in converting instrument detector misalignments into spacecraft attitude corrections.***

## FDSS Orbit & Attitude Products

***FDSS Orbit & Attitude Products***

## FDSS Orbit & Attitude Products

***FDSS Orbit & Attitude Products***
*(continued)*

## FDSS Product Generation Schedule

***Planned to generate and deliver FDSS orbit & attitude products once per week;***
***Orbit propagation uncertainty was too great for accurate image planning;***
***Current plan is to do FDSS products monday-Wednesday-Friday to reduce uncertainty in image planning;***
***Products of 8-day length done Monday and Wednesday; products of 5-week length and maneuver planning files done Friday; all other products done on request***

## Orbit Prediction Uncertaintyfor EO-1 Type Orbit

- Solar Flux (F10.7):  215  watts/m2/cycles/sec  bandwidth  x 10-22

## EO-1 FDSS Science Planning Algorithm

***FDSS is developing an algorithm that will convert a latitude-longitude designation to a row-path reference on the world reference system***
***This algorithm also computes the spacecraft attitude necessary to point at the desired image***
***The science validation facility will use this algorithm to evaluate imaging requests***
***The Mission Operations Planning and Scheduling System will use this algorithm to schedule a requested image                   ***

## EO-1 Flight Dynamics Support Subsystem

## Current Status of FDSS With Respect To Science Products

***Final software release to provide FDSS science products is on schedule for 7/99 completion***
***Procedures for instrument detector alignment / spacecraft attitude correction are being worked***
***FDSS product sets to be delivered To MIT/LL and TRW have been confirmed and product samples have been successfully transmitted via FTP***

## Unresolved Issues, Concerns & Comments

***No unresolved issues or concerns***
***Comment:   After discussions with the principal                investigators and the Project, it was decided that smoothing of GPS data to improve orbit information (post imaging) is not planned***

## Hyperion Planning and Data Processing

*TRW*

***Carol Segal / Jay Pearlman / Wendy Watson***

## Functional and Performance Requirements (TRW)

***Accept:***
*Pre-processed SWIR and VNIR Level 0 data from GSFC*
*HDF attributes appended *
*GSFC-supplied metadata, e.g., type of collect, scene lat/long, collect assessment*
*GSFC-supplied ancillary data*
***Generate Hyperion Level 1 data sets***
*Radiometrically process instrument data at full resolution*
*Append GSFC-supplied ancillary data in physical units*
*Spacecraft/instrument SOH telemetry*
*Append metadata, e.g.,*
*From TRW:  instrument information, level 1 log file (includes calibration, level 1 processing summary)*
*From GSFC:  spacecraft information, scene correlation, under-flight data*
*Provide Level 1 data with quality assessment within goal of 3 business days turnaround*

## Interface Overview

***Science interfaces***
*Level 0 processing algorithm*
*Hyperion L0/L1 data set transfer*
*AC and ALI L1 data set transfer*
*Metadata*
***Engineering interfaces***
*Raw and trended SOH*
*Real-time SOH during checkout*
*DCE SOH*
*Flight dynamics products*
***Planning interfaces***
*Scene requests*
*DCE schedule and status, scene correlation*
*Scene quality assurance*

*TRW*

## Hyperio-centric GSFC Interfaces

## Early-orbit Checkout Plan

***Draft of Hyperion plan promised July 15***
*Regular Early-orbit planning meetings promote integration*
*Solar/lunar calibration schedule identified (launch date dependent)*
*Lunar cal at full moon (exact phase: TBD), *_*+*_* 6 days*
***Hyperion plan overview***
*Power on for CEA/HEA on Day 6*
*Dark cal, lamp cal, solar cal (cover exercised) on Day 6*
*Lunar cal (?), heated outgassing begin Day 7*
*Heated outgassing duration: 13 days (TBR)*
*VNIR-only DCEs throughout heated outgassing*
*Begin instrument characterization*
*Mixed S-band/X-band downlink*
*Full capability on Day 20*
*Complete instrument characterization*
*Science-related sites*

## Hyperion SOH/AncillaryData Flow

- DCE SOH
- data  in
-  engineering units

- GSFC

- TRW develops
- metadata files
-  and formats
- ancillary data files

- Trended
- SOH data
- accessed by
- TRW as
- needed

- TRW
- Hyperion-centric
- processing
- tasks

- Raw  or GSFC
- processed data

- Trended SOH
- data files
- (engineering
- units)

- Monitor
-  trended and
- DCE SOH data
- via ASIST

- ASIST workstation at
-  GSFC or TRW

- Ancillary SOH data in
- engineering units

- TRW function

- TRW
- trouble-
- shooting

## Hyperion Science Data Flow

## Pertinent Documentation

***ICDs***
*Hyperion ICD (IF1-0228)*
*Hyperion MPT Cryocooler Control Software:  Architecture and Software User’s manual, D27802 (preliminary)*
*TRW - GSFC Data ICD  (June 4, 1999)*
*TRW - SSC Data ICD *
***Operator’s Manual (in preparation)***
*Draft due July 28*
***Early-orbit Checkout Plan (in preparation)***
*Draft distributed on July 16th*

## Data Processing Facility

## Test Plans

***ASIST workstation:  tested with instrument at TRW (July 99)***
***Data processing to be tested through MOC simulations***
*Simulation at GSFC/Data processing at TRW*
*Planning in process*

## Unresolved Issues and Concerns: Near-term

***ASIST disk space is insufficient (disk on order)***
***Metadata:  contents, format, source not finalized***
*Underflight data (e.g., AVIRIS)*
*Landsat 7 scene correlation*
*Spacecraft/other anomalies*
***Data processing issues***
*Require sample DLT tapes covering several days*
*Test Level 0 data transfer procedures from GSFC to TRW*

## Unresolved Issues and Concerns: Long-term

***Interface and simulation testing contents and schedule***
*Use of FDSS products*
*Planning/scheduling interfaces*
*End-to-end data flow/processing test *
***TRW/SSC interface undefined***
* **EDC, SSC metadata requirements definition*
***L&EO plan needs to be integrated/tested/finalized***
***Contingency plans need to be integrated/tested/finalized***
***Interface with Terra?***

## Stennis Space Center Status

***Stennis Space Center Status***

***Vicki Zanoni***

## Stennis Space Center

_***FUNCTIONAL OVERVIEW***_
***Collect and process Hyperion tasking requests for commercial applications partners***
***Coordinate processing of Hyperion Level 1 products for commercial applications partners***
*Receive level 0 and level 1 Hyperion products from TRW*
*Distribute level 0 and/or level 1 Hyperion products to commercial applications partner*
*Provide the level 0 and level 1 Hyperion data archive for commercial  partners throughout the life of the mission*
***Send Hyperion level 0 and level1 data products to EDC for long term archive***
***Approxiametly 200 DCE’s (2000 Hypercubes) are reserved for potential commercial customers***

***Stennis Space Center***

## Stennis Space Center

***Stennis Space Center***

_***MANAGEMENT OVERVIEW***_
***SSC activities are managed by the Commercial Remote Sensing Program Office, Code XA00***
_***MAJOR CHANGES***_
***Hyperion data processing funding issue resolved***
*SSC will fund commercial applications processing*
*Code YS will fund science processing*

## Stennis Space Center

***Stennis Space Center***
*Element Context - Data Flow*
*Science Validation Phase (Launch+2months-Launch+12months)*

## Stennis Space Center

**Commercial**
**Users**

_**SSC**_

- Commercial apps planning

- Hyperion update scene requests within policy guidelines

- Hyperion scene
- requests

- Input into Long Term Plan for Hyperion

_**EO-1 Mission Planning Office**_

- Mission Planning

_**MOPSS**_

- DCE Schedule

- Consolidated plan for instr & technologies

***Stennis Space Center***
*Element Context- Science Planning Flow*
*Science Validation Phase (Launch+2months-Launch+12months)*

## Stennis Space Center

*Data Validation System (DVS) Software Architecture*

- July 8, 1999

## Stennis Space CenterRequired Documentation

***NMP/SSC MOU - Update and get sign-off by July 30***
***TRW to SSC ICD - complete by August 31 ***
***SSC to MPO ICD???  Where do we define format for transmitting/receiving tasking information?***

## Stennis Space Center Schedule

## Science Validation Facility Status

***Science Validation Facility Status***

***Lawrence Ong***

## Tasks

***Advanced Land Imager (ALI) Level 1 Processing***
***Atmospheric Corrector (AC) Level 1 Processing as directed by the AC instrument team***
***ALI calibration and characterization***
***ALI image assessment***
***Data management for the Science Validation Team (SVT)***
***Data distribution to the SVT***

## Mission Science Office

***Mission Science Office***
***Science Validation Facility***
***Computing Assets***

## SVF Nominal Operational Procedures

_**0. Overview**_

- Data Processing

**1.**

**2.**

**3.**

- Tape Archive

- Data Distribution

- Receive data from
- MOC/AC Team/TRW

**4.**

## Slide 124

## 3. Data distribution

## Mission Science Planning Office’s (MP0)

***Scene Request Tracking Database Layout***

## Science Data Tracking Database Layout

** ****Tool for data and data distribution management**
** ****Implemented as an MS Access application**

## Functional Status

## ALIProcessingStatus and Issues

***Jenifer Brinker Evans***

## Lincoln Laboratory’s Role

***Design, integration and test of Advanced Land Imager (ALI)***
***On-orbit functional check and performance assessment***
***Radiometric calibration of mission data during first sixty days***

## On-Orbit Functional CheckMilestones and Tasks

***Spacecraft achieves proper orbit and provides full power***
***Turn on ALICE***
*Thermal control system active*
***Collect housekeeping telemetry during comprehensive test***
*Verify voltages, temperatures, etc.*
***Perform Functional Test***
*Dark current, test pattern, internal calibration lamp data collection*
***Release launch latches***
*Aperture cover & calibration diffuser*
***Exercise mechanisms***
*Variable aperture & aperture cover*
***Perform Functional Test***
*Dark current, test pattern, internal calibration lamp data collection; verify no change *

## Required Data Collection FrequencyPerformance Assessment Period

***Internal calibration***
***Solar calibration***
***Lunar calibration***
***Deep space look***
***Dark offset***
***Nadir earth scenes***
***Off-nadir earth scenes***
***L7 common scenes***

***  ******14 /week***
***  ******1 /week***
***  ******1 /week (skip new moon)***
***  ******3 total ***
***  ******14 /week***
***  ******10 /week***
***  ******4 /week***
***  ******1 /week***

## Performance Assessment

***Performance Assessment***

## Radiometric Calibration Pipeline

## Status

***L&EO:  Functional Check Out & Performance Assessment***
*Defined minimum data and tasks.*
*Defining early site selections.  Complete by end of July.*
***Performance Assessment Software***
*ICD in place*
*Includes spatial, spectral, radiometric, and functional analysis in addition to general instrument performance*
*Pre-launch software complete.  *
***Radiometric Calibration Pipeline***
*ICD in place*
*Preliminary version with final interfaces delivered 26 March 1999*
*Final version with improved cal database will be del. 31 August 1999*
***Other - Supporting spacecraft I&T, CPT, etc.***

## Issues

***Functional check out & performance assessment***
*Further reduced to 60 days total*
*Will have collected a minimum of approximately 21 DCEs a week to analyze*
*Need to update radiometric calibration pipeline database*
*120 days considered minimum necessary.*
***Radiometric Calibration Pipeline***
*Not yet tested on complete GSFC supplied Level 0 data.*
*Level 1R output file not yet tested in SVF.*
***Other***
*Need to define exchange for ftp’d telemetry data*
*No one funded for nominal quality check image assessment of all ALI data in a timely manner.*

## AC Data Processing

***Dennis Reuter / George***

## Functional Overview

***AC Level 0 data products generated by the MOC with algorithm defined by the AC Instrument Team (ACIT)***
***Performance Assessment of AC during EOC***
***Development of the AC Calibration System (ACCS)***
***Generation of AC Level 1R data products***

## Data Flow

## Level 0 Data Processing

***AC L0 algorithm description provided to the MOC***
***AC L0 algorithm function verified using data from AC - WARP I&T***
***MOC produces band interleaved AC data sets***
***Define Format of AC HDF science data sets***
***Transfer of data in HDF format on DLT tape media from the MOC***

## Level 1R+ Data Processing

***Definition of AC L1R data products***
***Evaluation and Selection of calibration data sources***
***Atmospheric modeling and simulations***
***Comparison of results to coincident measurements of other sensors***
***ACCS S/W development***
***Integration and testing of the ACCS with the SVF***

## Present ACIT Activities

***Initial flux calibration and frequency calibration***
***LAC Instrument I&T - data flow tests, optical alignment***
***Planning and design of ACCS***
***Final preparations of ACCS computer facilities***

## EOC Activities

***Data beyond MOC L0 required for assessment of instrument performance***
*ALI and Hyperion L1 data from the SVF*
*Other instrument data and ancillary data (from DLT’s*
***DCE requests submitted to the MPO***
***Scene reports written following DCE***
***Produce L1 data upon request from the SVF***

## Issues

***Ingest of MOC / SVF data products, tape media and electronic transfer***
***Necessary metadata formats.***

## EO-1Archiving andProduct Distributionat EDC

***EO-1******Archiving and******Product Distribution******at EDC***

***John Boyd***

## Role

***Long-term archiving and cataloging***
***Level-1 and Level-0 product distribution:***
*Public*
*U.S.*
*International*
*Education (K-16)*
*Science*
*Commercial (if not served by SSC)*
*Government*

## Functional Description

***Functional Description***

***Permanently archive all AC, ALI, and Hyperion Level-0 and Level-1 data acquired over the life of the mission***
***Archive radiometric (and geometric if applicable) correction algorithms; software; test/calibration data sets; and, NRA and scientific publications***
***Update any archived Level-1 data sets recalibrated during mission life***
***Catalog the archived data sets.  Generate browse images as required (three-band, initially)***
***Provide online access to the catalog.  Allow queries based on cloud-cover, geographic area, and date***
***Provide cross-catalog search capability with L7, MODIS, ASTER, and AVIRIS data sets ***
***Provide online browse display for selected scenes ***

## Functional Description(continued)

***Functional Description****(continued)*

***Accept, validate, and process user requests for one or multiple data products.  Users may request Level-1 and/or  Level-0 Hyperion, ALI, or AC products***
***Generate products (tape copy, with order-specific header) and distribute on hard media or via FTP***
***Invoice the customer, and process payments***
***Handle user technical questions and product quality complaints***
***Maintain the Project web page.  Provide access to general info; format documents; and NRA results***
***Compile user statistics: no. of users; order volume; sensor; product level; problems; other feedback***

## Start-up Premise

***Archiving***
*Begin populating the archive as soon as initial data sets have been calibrated and validated  (L+4 to L+6 ?)*
*Archive all data acquired during the life of the mission*
*Maintain data sets for minimum 20 years after mission*
***Cataloging and Distribution***
*Integrate EO-1 query and browse with existing systems to facilitate cross-inventory search*
*Generate products for all users at cost of reproduction*
*Service NRA/Instrument Team users if helpful to SVF*

## Interfaces

## Proposed Schedule

## Issues

***How to:***
*Provide access to data with minimum duplication of effort by SSC or SVF*
*Simplify product access by L7 and Terra science investigators*
*Allow EDC staff to become knowledgeable with sensor  experts and characteristics of three new-technology instruments before expertise no longer is available*
*Minimize production impacts on SVF science activities*

## Summary/Issues

***Summary/Issues***

***Nick Speciale***

## Action Item Status Chart

## Action Item Status Chart

## Action Item Status Chart

## Metadata Issue

_***Problem Statement***_***:***
*Current HDF meta data may not be sufficient for SVT, requiring last minute changes in science processing and planning system.*
_***Resolution Plan:***_
*Form tiger team (Joy Henegar, Tom Brakke, Bob Defazio, Larry Alexander, Bruce Trout, L7 expert, John Boyd, Vicki Zanoni) to review current metadata formats and propose changes necessary to support SVT and commercial customer requests.  Implementation target date (after EOC)*

## Testing Issue

_***Problem Statement:***_
*Testing and validation of science planning and processing system is behind schedule and heavily tied to Spacecraft testing.*
_***Resolution Plan:***_
*Need to exercise and simulate planning and processing elements on weekly basis using tape data from CPT (all instruments operating in DCE mode)*
*Need to track timelines for processing and understand where efficiencies can be increased.*
*Need to create test tape with likely error scenario and exercise system *
_***Action:***_*  *
*Simulation team to create test simulation for planning and processing*

## DPS Readiness

_***Problem Statement:***_
*Level Zero Data Processing System is still undergoing configuration changes.  Current hardware configuration may not be able to support likely operations data .*
_***Resolution Plan:***_
*Need to exercise DPS and create required data output products as expected during first 60 days*
*Need to put under CM control DPS H/W configuration and work operations scenario around it.  *
*Need to test DPS with data which has likely errors (as seen from L7)*
_***Action:***_*  *
*DPS team should be reporting weekly on progress and resources needed to baseline system and validate its requirements.  Additional resources brought on if current personnel are insufficient. *

## SVF Readiness

_***Problem Statement:***_
*SVF readiness has not been checked yet during testing, need to exercise output of SVF to science users.*
_***Resolution Plan:***_
*Need to exercise SVF and create required data output products as expected during first 60 days and nominal mission period.*
_***Action:***_*  *
*End to end mission simulations should be scheduled weekly with test data to exercise DPS and SVF (also TRW processing capabilities)*

## SVF/MIT Roles During EOC

_***Problem Statement:***_
*There is still confusion as to role of SVF facility during EOC,  MIT/LL will evaluate subset of scenes,  the question is what is dispostion of remaining scenes (who is processing, evaluation etc....) *
_***Resolution Plan:***_
*SVF and MIT/LL need to resolve roles during EOC*
_***Action:***_*  *
*Splinter meeting or telecon to resolve roles issue by end of this week. *

## Sustaining Engineering Plan

_***Problem Statement:***_
*Need to review current level of support and weigh it against probable changes during EOC and nominal operations.*
_***Resolution Plan:***_
*Ken Lehtonen and Nick Speciale meet with Dan Mandl and Steve Ungar to review there expected sustaining engineering budget *
_***Action:***_*  *
*Meeting by end of July*

## S-Band Contingency Data VolumeDuring EOC

_***Problem Statement:***_
*During EOC instrument teams would like more use of S-band contingency mode to quickly turnaround data (less than one shift), however there are severe limitations on ground stations ability to capture and forward this data and complications to operations.*
_***Resolution Plan:***_
*-  Limit S-band contingency mode to initial instrument turn ons and first time operation mode (very select set).  Utilize expedited X-band to Wallops downlink to get data out within 48hrs.  *
_***Action:***_*  *
*FOT to review instrument checkout plans (1st 60 days) and challenge any unnecessary  S-band contingency downlinks (end of July) *

## Data Processing Operations Timeline

_***Problem Statement:***_
*Current timeline for processing to L0 data may exceed (in most cases) the 16 day repeat cyclen during nominal operations, this may cause more DCE’s to be scheduled to ensure targets are captured and additional processing load on DPS (beyond 4DCE’s per day)*
_***Resolution Plan:***_
*Note: EOC turnaround will be less than three days.*
*Work DMR with Ground Stations to ensure tapes shipped to GSFC within three days (use Alaska more often) or look into additional X-band ground station coverage (Sioux Falls???)*

## SSC interface

_***Problem Statement:***_
*SSC interfaces need to be defined (especially SSC since funding decision has been made)*
_***Resolution Plan:***_
*Need to resolve TRW contractual issues and develop Level 1 processing ICD between TRW and SSC,  also update current TRW-GSFC to include Level 1 processing for SVT. *
*End of July draft for SSC ICD,  need to agree to contract wording for commercial level 1 processing.*
_***Action***_*:  Vicki Zanoni, Jay Pearlman, Nick SpecialeWilliam Browne develop contract wording by end of July. *