New Horizons Mission Operations Preliminary Design Review October 2002

1
Instrument Sequencing Operations
New Horizons Science Operations and
Sequencing JULY 21, 2003 Ann Harch Science
Sequencing Coordinator ann_at_baritone.astro.cornell.
edu [phone]
2
Instrument Sequencing Operations

• ELEMENTS OF SCIENCE SEQUENCING OPERATIONS
• OVERVIEW - FACILITIES, PEOPLE, HERITAGE
• SOFTWARE TOOLS COMMAND MACROS
• SEQUENCE GENERATION PROCESS
• SCHEDULE
• DELIVERABLES
• KNOWLEDGE MANAGEMENT

3
Instrument Sequencing Operations - Overview

• New Horizons Sequencing Operations - Overview
• The primary CENTER for science sequence
  generation will be the Tombaugh Science
  Operations Center at SwRI, Boulder
• TSOC will lead the New Horizons science sequence
  development process and serve as the interface
  between instrument teams and APL for coordination
  and development of science activity command
  sequences and the s/w required to build these
  sequences
• Instrument sequencing is accomplished through an
  effort involving close participation among the
  following three entities
• - TSOC
• - APL Mission Operations
• - Instrument Teams and Mission Science
  Planning Team

4
Instrument Sequencing Operations - Overview

• New Horizons Sequencing Operations - Facilities
  and People
• TOMBAUGH SCIENCE OPERATIONS CENTER (TSOC)
• Alan Stern (New Horizons Principal Investigator)
• John Andrews (TSOC Project Manager)
• Leslie Young (Payload Science Coordinator and NH
  Deputy Project Scientist)
• Ann Harch (Science Sequence Coordinator)
• Debi Rose (Science Sequence Coordinator)
• MISSION OPERATIONS CENTER (APL)
• Alice Bowman (New Horizons Mission Operations
  Manager)
• Mission Operations Personnel (tbd)

5
Instrument Sequencing Operations - Overview

• New Horizons Sequencing Operations - Facilities
  and People
• INSTRUMENT TEAMS
• Instrument Location Science Lead Engineering
  Lead
• LORRI APL Andy Cheng Steve Conard
• RALPH SwRI Alan Stern John Scherrer
• ALICE SwRI Alan Stern John Scherrer
• PEPSSI APL Ralph McNutt Will Devereux
• SWAP SwRI Dave McComas Scott Wiedner
• REX Stanford Len Tyler Ivan Linscott
• SDC CU M. Horyani Gene Holland

6
Instrument Sequencing Operations - Overview

• New Horizons Sequencing Operations - Heritage
• The software system proposed has a high degree of
  heritage from NEAR and CONTOUR.
• We are once again using the JPL SEQGEN suite of
  software programs for sequence building.
• The science planning and sequence development
  process is similar to Voyager and Galileo
  encounter planning.
• Science planning teams define science
  requirements
• TSOC builds the macros and construct sequences
  that are reviewed and validated by instrument
  teams.

7
Instrument Sequencing Operations - Software

• Sequence Generation Software gt Two-step process
• 1) INSTRUMENT SEQUENCE DESIGN SOFTWARE
• Instrument-specific software that assists with
  opportunity analysis and observation design
• ALICE, RALPH, LORRI -
• Will use a visualization package that includes
  STK and other ancillary programs
• PEPSSI, SWAP, SDC - may opt to use SEQGEN
  directly
• 2) SEQADAPT/SEQGEN (and STATESIM)
• Project-maintained s/w used for development of
  command macros and actual sequence build models
  s/c resource usage, does instrument flight rule
  and constraint check
• Required for all instruments
• Graphical representation of instrument and
  engineering activities, DSN contacts, simulation
  of s/c resource use, etc
• May run with individual instrument input, all
  science instruments merged, or with engineering
  activities merged

8
Instrument Sequencing Operations - Software

• Sequence Generation Software - Modeling
  Constraint Checking
• 1) INSTRUMENT SEQUENCE DESIGN SOFTWARE
• Can verify that sequence will not put instrument
  or s/c health safety at risk
• Must address the question of whether the activity
  makes sense from a science point of view (SEQGEN
  will not do this)
• Will the commanded s/c pointing and instrument
  commanding produce the desired and expected
  results?
• In some cases, this software can also perform
  engineering validation on final sequence products
• 2) SEQADAPT/SEQGEN (and STATESIM)
• Will evaluate sequence to verify that it will not
  harm the spacecraft or instruments
• Will model common-use resources (SSR usage, s/c
  commanding rates, pointing control, power,
  propellant, etc.)

9
Instrument Sequencing Operations - Software

• Instrument Sequence Design S/W - Remote Sensing
  Visualization Tool
• SOC and others have evaluated the need for a
  visualization tool
• required for Pluto/Charon Encounter and Rehearsal
  Sequences
• desired for Jupiter flyby, not needed for
  Commissioning
• Will take advantage of existing software
  developed by New Horizons GC engineers for
  visualization of s/c pointing, modeling of GC.
• Reads predict planetary and s/c ephemeris files
• Evaluates commanded s/c pointing
• Will read in an image timing file to plot
  footprints on target body
• This s/w baselines STK and ancillary programs
  from APL
• Remote sensing instruments will use this tool
  primarily for development of the Pluto/Charon
  sequences.
• User interface will allow iterative design of
  observations, result is a validated sequence in
  standard SEQGEN sasf format

10
Instrument Sequence Operations - Software

• SEQGEN Software
• Multi-mission SEQGEN is a suite of software
  programs developed at JPL to assist with command
  load generation
• APL/MOC will adapt software for New Horizons
• TSOC will eventually have a mirror system to that
  available in the MOC
• TSOC will have access to the two front-end
  programs
• SEQADAPT
• This software package allows user to create the
  RE-USABLE command macros (stringing together of
  instrument and spacecraft commands, assigning
  relative timing)
• These macros (called CASs and Fragments) will
  be tested on the brass board for variety of
  parameters over ranges available and put into
  libraries for use during sequencing operations.
• SEQGEN
• Allows user to schedule CASs on timeline (front
  end of load creation)
• Input is a text file (sasf) that includes
  multiple Requests (scheduled CASs)
• Output includes the modified sasf, command
  expansions, etc

11
Instrument Sequencing Operations - Software

• What is a FRAGMENT?
• A Fragment is a structured grouping of
  instrument and/or spacecraft commands
• Order and number of commands generally fixed (can
  program loopers, or conditional commanding)
• May contain parameters that supply values for
  command arguments, timing offsets between
  commands, or other variables
• May combine spacecraft and instrument commands
  within a single Fragment
• Fragments are created in SEQADAPT
• Fragments utilize EPOCH command database supplied
  by instrument teams
• Fragments can be built to implicitly prevent
  violation of spacecraft health and safety (will
  check argument range limits, timing limitations,
  etc)
• A Fragment cannot be scheduled directly into the
  timeline

12
Instrument Sequencing Operations - Software
Example of CONTOUR Imager/Spectrometer Power On
Fragment CRISP(CRISP_POWER_ON,\CRISP\,
PARAMETERS, STAT_INT_SEC(
TYPE,UNSIGNED_DECIMAL,
RANGE,\0...255\, DEFAULT,\2\
), SPC_COOL( TYPE,BOOLEAN,
DEFAULT,\FALSE\ ), end,
STEPS, note(1,
SCHEDULED_TIME,\000000\,FROM_ACTIVITY_START,
TEXT,\"Description Power on and boot
CRISP"\ ), note(2,
SCHEDULED_TIME,\000000\,FROM_ACTIVITY_START,
TEXT,\"Duration tbd"\ ),
note(3, SCHEDULED_TIME,\000000\,FRO
M_ACTIVITY_START, TEXT,\"Shared
Status FALSE"\ ), command(4,
SCHEDULED_TIME,\000000\,FROM_ACTIVITY_ST
ART, MACRO_START("CDH","CRISP_TURN_ON"
,0,-1) ),
command(5, SCHEDULED_TIME,\000001\,F
ROM_ACTIVITY_START,
CRS_TRK_OPHTR_PWR("ON") ),
command(6, SCHEDULED_TIME,\000002\,F
ROM_ACTIVITY_START,
CRS_TPU_ROM_BOOT("EXECUTE") ),
command(7, SCHEDULED_TIME,\000003\,F
ROM_ACTIVITY_START,
CRS_ROM_BOOT("EXECUTE") ),
command(8, SCHEDULED_TIME,\000004\,F
ROM_ACTIVITY_START,
CRS_PWR_PRI("ON","ALL","EXECUTE") ),
command(9, SCHEDULED_TIME,\000005
\,FROM_ACTIVITY_START,
CRS_FLT_PWR("ON","EXECUTE") ),
command(10, SCHEDULED_TIME,\000006\,
FROM_ACTIVITY_START,
CRS_IMG_PWR("ON","EXECUTE") ),
13
Instrument Sequencing Operations - Software
Example of CONTOUR Imager/Spectrometer Power On
Fragment (cont) command(11,
SCHEDULED_TIME,\000007\,FROM_ACTIVITY_START,
INCLUSION_CONDITION,\SPC_COOL\,
CRS_SPC_PWR("ON","EXECUTE") ),
command(12, SCHEDULED_TIME,\000008\,
FROM_ACTIVITY_START,
CRS_TPU_MIR_PWR("ON","EXECUTE") ),
command(13, SCHEDULED_TIME,\000009\
,FROM_ACTIVITY_START,
CRS_STAT_INT(STAT_INT_SEC,"EXECUTE") ),
command(14, SCHEDULED_TIME,\000
010\,FROM_PREVIOUS_START,
MACRO_END( ), end ) end
ACTIVITY_TYPE CRISP_POWER_ON
14
Instrument Sequencing Operations - Software

• WHAT IS A CAS? - Canned Activity Sequence
• A CAS is a structured grouping of Fragments
  created in SEQADAPT
• A CAS may not call individual commands
• May contain a single Fragment or may be a
  concatenation of multiple instrument and/or
  spacecraft (pointing or other) Fragments
• May pass parameters through to the Fragments it
  calls
• May define additional parameters that define
  timing offsets between Fragments or other
  conditions
• CASs are scheduled in SEQGEN to create command
  sequences
• A SEQGEN user schedules a CAS by assigning a
  scheduling time, and supplying values for all
  parameters
• Additional modeling within SEQGEN is used to
  evaluate instrument flight rules, model s/c
  resource usage, identify conflicts among
  instruments

15
Instrument Sequencing Operations - Software
Example of CONTOUR Imager/Spectrometer Power On
CAS CRISP(CAS_CRISP_POWER_ON,\CRISP\,
PARAMETERS, STAT_INT_SEC(
TYPE,UNSIGNED_DECIMAL,
RANGE,\0...255\, DEFAULT,\1\
), SPC_COOL( TYPE,BOOLEAN,
DEFAULT,\FALSE\ ), end,
STEPS, activity(1,
SCHEDULED_TIME,\000000\,FROM_ACTIVITY_START,
CRISP(CRISP_POWER_ON,STAT_INT_SEC,SPC_COO
L) ), end ) end ACTIVITY_TYPE
CAS_CRISP_POWER_ON
16
Instrument Sequencing Operations - Process

• Science Sequence Generation - PROCESS OVERVIEW
• Science teams define high-level activity desires
  and objectives (Science Activity Planning)
• After approval by PI, science coordinators and
  MOps work together to schedule activities
• MOps delivers ops initial files to TSOC and
  instrument teams
• TSOC science coordinators, working closely with
  instrument teams, create scheduling requests for
  science activities using standard SEQGEN request
  file (approved CAS and Fragment blocks)
• Final merge of all science instrument files and
  constraint check in SEQGEN occurs at TSOC
• Instrument engineers review, validate sequences
  at instrument institutions
• Science coordinator delivers a set of files that
  is conflict free and will not violate health and
  safety of s/c or any instrument.

17
Instrument Sequencing Operations - Process
Science Activity Plan Development - Process
within science team to design a set of integrated
inputs for a particular event such as the
commissioning, or a flyby - Lay out timing,
high-level data volume, describe conditions,
requirements, constraints - Involves interactions
among science people led by Young/Weaver/Stern
to understand science goals - involves
interaction with project engineering and
sequencing experts to assure that the designs
are reasonable and doable Science Activity Plan
(Skeleton and Final) - Document including
timelines and text, with enough description
about each observation that sequencing can be
attempted
18
Instrument Sequencing Operations - Process
Science Sequence Generation Matrix
19
Instrument Sequencing Operations - Process
TSOC - SwRI (PI, PSC, SSCs)
Instrument Leads - Home Inst science (s) engr (e)
Mission Operations - APL (Bowman, et al)

• Resolve high-level resource conflicts, create
  science activity plan
• Work high-level scheduling issues with MOC and
  instrument teams

Develop engineering housekeeping schedules,
iterate with SOC
high-level science obs plans
individual instrument observation and
calibration desires
Create high-level observation and calibration
desires, requirements (s/e)
initial s/c ops sched.
science activity plan
intermediate s/c ops schedules

• Evaluate encounter sequence designs for science
  content (s)
• Evaluate calibration designs (e)

plots, files, analyses

• Design detailed observations using op analysis
  s/w

• Revise ops schedules
• Prepare SEQGEN initials

detailed science activity plan
review comments
detailed science activity plan
more plots, SEQGEN output files, analyses

• Evaluate encounter sequence designs for science
  content (s)
• Evaluate calibration designs (e)
• Review command sequences (s/e)

• Implement designs in SEQGEN
• SEQGEN merge
• Conflict resolution
• Iterate with instrument teams

final s/c ops schedules, SEQGEN initial files
review comments

• MOps merges engineering and science SEQGEN files

integrated conflict-free instrument SEQGEN sasf
files
sequence products for review, identification of
problems that need to be fixed

• Final Engineering Review (e)

instrument health and safety problems
Make files available to instrument engineers
final merged spacecraft and science review files
available (SEQGEN, Statesim)
sequence clean and safe - approved
final science approval
Final approvals to MOps
Mops creates LOAD
to spacecraft
20
Instrument Sequencing Operations - Schedule
Schedule of Activities - through 2007 2/03 -
7/04 Skeleton Science Activity Plans for
Commissioning, Jupiter and Pluto/Charon
Encounters 8/03 - 6/05 Command macro
development (CAS/Frag) 11/04 - 9/05 Mission
Simulations 1/05 - 3/05 Final Science
Activity Plan for Commissioning 3/05 - 8/05
Instrument Commissioning Sequence Build 2/06 -
7/06 Instrument Commissioning 3/05 - 6/05
Final Science Activity Plan for Jupiter 6/05 -
12/06 Jupiter Encounter Sequence Build 2/07
Jupiter Encounter
21
Instrument Sequencing Ops - Deliverables
Sequencing Deliverables - From TSOC to
Instrument Teams 3/04 Draft
Skeleton SAP for Commissioning 3/04
Draft Skeleton SAP for Pluto/Charon Flyby 3/04
Draft Skeleton SAP for Jupiter Flyby
5/04 - 8/05 Instrument command macros out for
review 8/04 - 8/05 Mission Simulation
Sequences out for review 5/05 - 7/06
Commissioning Sequences out for review
8/05 - 9/06 Jupiter Flyby Sequences out for
review
22
Instrument Sequencing Ops - Deliverables
Sequencing Deliverables - From Instrument Teams
to TSOC 8/03 - 6/05 Commissioning and
encounter operating procedures (includes
STOL activation and
checkout sequences for post-launch) 2/04 - 4/04
Instrument command tlm databases 5/04
Review of Draft Skeleton SAP for
Commissioning 5/04 Review of Draft
Skeleton SAP for Pluto/Charon 5/04
Review of Draft Skeleton SAP for Jupiter 5/04
- 8/05 Review of instrument command macros
developed by TSOC 8/04 - 8/05 Review of
Mission Simulation sequences developed by
TSOC 5/05 - 7/06 Review and validation of
Commissioning Sequences 8/05 - 9/06 Review and
validation of Jupiter Flyby Sequences
23
Instrument Sequencing Ops - Deliverables
Sequencing Deliverables - From TSOC to
MOps 5/04 - 8/05 Instrument command macros
for validation 8/04 - 8/05 Instrument
Request Files for Mission Simulations (2-5)
10/04 - 6/05 Instrument STOL Commissioning
Checkout Sequences 4/05 -
4/06 Instrument Request Files for
Commissioning 6/06 - 7/06
Instrument Request Files for Jupiter Flyby and
Rehearsals Sequencing Deliverables - From MOps
to TSOC 3/04 SEQADAPT/SEQGEN
available 10/04 - 6/05 MOps Initial Files for
Mission Sims 11/04 - 7/05 Review products for
Mission Sims 3/05 - 12/05 MOps Initial Files for
Commissioning 5/05 - 6/06 Review products for
Commissioning 6/05 - 7/06 MOps Initial
Files for Jupiter Flyby and Rehearsals
7/05 - 8/06 Review products for Jupiter Flyby
24
Instrument Sequencing Operations - Schedule
2003
CDR
Mission Ops Review
Science Commanding Estimate
Science Slewing Fuel Estimate
TSOC to work with instrument teams to decide what
sequence generation or validation s/w is
required, define development schedule
TSOC Uplink Users Manual
CAS/Frag Conceptual Design
LORRI
TSOC
ALICE
PEPSSI
APL
Pluto/Charon Flyby - Skeleton Science Activity
Plan (SAP) Development
Commissioning - Skeleton SAP Dev
Jupiter Flyby - Skeleton S A P Development
25
Instrument Sequencing Operations - Schedule
2004
Instrument Procedures/Users Manuals (SRDs)
Mission Sim Plan
Mission Simulations
Initial instrument cmd tlm database workbooks
due to TSOC
Revised instr. cmdtlm database wrkbks to
TSOC/APL, ingestion into SEQADAPT,
SEQADAPT/SEQGEN available for science sequencing
MSIM I
TSOC Uplink Users Manual
CAS/Frag Conceptual Design
SEQADAPT - generate CAS/Frag and validate
SEQGEN - build individual instrument sequences
and coordinated events
RALPH
TSOC
LORRI
LORRI
RALPH
RALPH
TSOC - Harch/Rose
SDC
ALICE
ALICE
SDC
TSOC - Harch/Rose
SDC
TSOC
APL - tbd
SWAP
PEPSSI/SWAP/REX
PEPSSI/SWAP/REX
REX
APL
SEQGEN - MSIM 2
Draft Pluto/Charon Skeleton SAP
Pluto/Charon Skeleton SAP
TSOC
Pluto/Charon Flyby - Skeleton SAP Development
Commissioning Skeleton SAP
Draft Commissioning Skeleton SAP
Commissioning - Skeleton S A P Development
Jupiter Skeleton SAP
Draft Jupiter Skeleton SAP
Jupiter - Skeleton SAP Development
26
Instrument Sequencing Operations - Schedule
2005
Mission Simulations (continued)
MSIM 4
U/L Users Manual
MSIM 2
MSIM 3b
MSIM 3
TSOC Uplink Users Manual
SEQADAPT - generate CAS/Frag and validate
MSIM 2
SEQGEN - MSIM 4
SEQGEN - MSIM 3
SEQGEN -Instrument Commissioning
Draft Commissioning Final SAP
Commissioning Final SAP
Commissioning - Final S A P
Jupiter Final SAP
Draft Jupiter Final SAP
Jupiter Encounter - Final S A P
Initial SEQGEN - Jupiter Encounter and Rehearsal
27
Instrument Sequencing Operations - Schedule
2006
Post-Launch Checkouts and and Cals
Post-Launch Cals
Jupiter Rehearsal
SEQGEN -Instrument Commissioning
Launch
SEQGEN - Jupiter rehearsal
SEQGEN - Jupiter Flyby
28
Instrument Sequencing Operations - Schedule
2007
Jupiter Flyby (TBR)
29
Instrument Sequencing Operations - Knowledge

• Knowledge Management
• Science Sequencers User Manual
• Overview as well as detailed description of
  Sequence Build Process
• Detailed description of commanding macros needed
  for instr. ops
• Tutorials on using GC for instrument pointing,
  and about required spacecraft commanding for
  instrument operations
• Tutorials on science instrument use including
  operating rules and constraints
• Examples of designs for various sequence
• Operational notes following execution of
  sequences notes about anomalies, problems,
  special situations
• All sequence files are ASCII
• Cross-training of Mission Ops and TSOC science
  coordinators