LAT Test Configurations

1
GLAST LAT System Engineering
System Checkout Test Test Objectives
Plans Rich Baun, Eduardo do Couto e Silva, Pat
Hascal rbaun_at_slac.stanford.edu [phone]
2
LAT Level Test Purpose/Goals

• Phase 1 - System Checkout Test Purpose/Goals
• Put the instrument in a config where all Towers,
  ACD, FSW, and EM/Flight DAQ hardware can be
  tested
• Risk Reduction
• Show readiness for Phase 2
• Phase 2 Run for the Record Purpose/Goals (not
  discussed today)
• Requirements sell-off
• Instrument performance and health through
  environments
• Direct sell-off of requirements
• Data collection and calibration for Science
  requirements analysis sell-off
• Copper path checks
• Function validation
• Integrated Instrument operations demonstration
• Instrument On-Orbit operations preparation

3
Phase 1 Test Cases

• System Checkout Test Case Sequence
• LAT Initialization/Power On LAT001
• Sequence in development with FSW
• LAT Configuration File Test LAT091
• Subset of Run for the Record Test
• Proposal Load, invoke, and verify one
  configuration
• LAT Charge Injection Functional LAT101
• Subset of Run for the Record Test
• Three simple LCI tests, one for each detector
  subsystem
• LICOS results compared to LATTE 4 results
• LAT Event Handling LAT221
• Muon Run only
• Use SVAC B2 (flight settings) and ACD not in VETO
  Mode
• Details in development
• LAT Power Off LAT011

4
System Checkout Planning Issues

• Issues
• The level of test case detail needs to be
  established
• What info does IT need from Systems to
  adequately define a test
• Test cases details must be defined
• Configuration test, what is validated and how
• During LCI and Muon run, what is the
  configuration of all detectors
• Definition and use of LAT Configuration needed
• What files/file contents constitute a LAT
  Configuration
• Will FSW defaults work for LAT Level Test?
• IT may have to tailor the Pipeline to display
  results and config
• LDF Data formats need to be defined
• Will affect Pipeline development and Offline
  analysis
• Analysis tools for all tests need to be defined
• Environment, tools, and success criteria

5
Run for the Record Planning Issues

• Issues
• Lack of time between System Checkout and Run for
  the Record
• Must prioritize and work both activities in
  parallel
• Test case definitions may change as requirement
  verification flowdown continues
• Could cause changes to scripts currently in
  development
• Requires close coordination with IT

6
Plan Forward

• Small working group meetings with IT this week
  beyond to
• Agree to appropriate level of detail in test case
  definitions
• Define the contents of each test case in detail
• LAT091 Determine configuration to load (SVAC B2
  ACD?)
• LAT101 Finalize LCI test cases to be run
• Muon Runs Work with SVAC and IT to identify
  test details
• ECD 30 Sept
• Analysis tools, success criteria, and data
  formats
• Online, Offline, and Systems meet this week
• ID what tools are needed, appropriate success
  criteria, and data formats for each test case
• Work in parallel with above activity to define
  LAT Level tests
• Prioritize test cases and one by one work out the
  details
• IT, Subsystem, and FSW support needed
• Systems to identify test case updates to IT
  weekly