GLAST LAT ProjectFace to Face Managers Meeting 04/14/04 4.1.9 - Integration and Test 1 GLAST Large...
-
Upload
darrell-simpson -
Category
Documents
-
view
212 -
download
0
Transcript of GLAST LAT ProjectFace to Face Managers Meeting 04/14/04 4.1.9 - Integration and Test 1 GLAST Large...
GLAST LAT Project Face to Face Managers Meeting 04/14/04
4.1.9 - Integration and Test 1
GLAST Large Area Telescope: GLAST Large Area Telescope: I & T Input to Face to Face Managers
Meeting, April 14th, 2004
Elliott BloomSU-SLAC
Subsystem Manager
Gamma-ray Large Gamma-ray Large Area Space Area Space TelescopeTelescope
GLAST LAT Project Face to Face Managers Meeting 04/14/04
4.1.9 - Integration and Test 2
IFCT Role in Functional Tests (Larry W.)IFCT Role in Functional Tests (Larry W.)
• IFCT is responsible for helping to design/define and implement I&T functional tests on the subsystem and LAT level (see Pat’s presentation) with major input to LAT-MD-02730.
• The test scripts used in the functional testing will actually be implemented by the I&T online department with guidance from LAT-MD-02730 and IFCT. The test scripts will be placed under configuration control by I&T online.
• The test procedures will be owned and configuration controlled by IFCT.
• All I&T testing of flight hardware will be performed by IFCT department electrical technicians and engineers who have been trained in their use.
• IFCT will need major assistance from the subsystems in helping to interpret the results of the tests (pass/fail with report). Particularly, in the case of fail (see SVAC role slide 4).
GLAST LAT Project Face to Face Managers Meeting 04/14/04
4.1.9 - Integration and Test 3
• ACD– 2,200 hours for checkout/testing/support. (1 man year)
• Calorimeter– 1.5 FTE's (not continuously?) and travel expenses for
Calorimeter I&T Support.• DAQ
– 700 hours for hardware I&T support. (4 man months)• Flight Software
– 1,800 hours for software I&T support. (10 man months)• Mechanical
– ??• SAS
– ??• Tracker
– 2 FTEs (Subsystem scientists) (3 man years)– Hiro Tajima, Johann Cohen-Tanugi (SLAC) (3 man years)
Subsystem Support of I&T after DeliverySubsystem Support of I&T after DeliveryFrom 7/04 – 1/06 ?
GLAST LAT Project Face to Face Managers Meeting 04/14/04
4.1.9 - Integration and Test 4
SVAC LAT Build Data Analysis Role (Eduardo)SVAC LAT Build Data Analysis Role (Eduardo)
• There are two SVAC data analysis efforts that support the LAT build and test and both use the same test data – Analysis of “Pass/Fail” test data of the flight hardware relative
to an established baseline (See previous manpower chart slide 3).
– Determine hardware baseline and calibrations
– Results due with hours or, at most, a day (TBR)
– I&T, SAS and Subsystems effort, e.g., CPT test offline.
– Analyses of data from the flight instrument in various stages of completion, which assume a well understood baseline and calibrations (LAT wide collaboration effort).
– Uncover subtle hardware problems
– Apply SAS reconstruction algorithms to real data
– Results due in 2 to 3 weeks after data taking (TBR).
GLAST LAT Project Face to Face Managers Meeting 04/14/04
4.1.9 - Integration and Test 5
I&T/SVAC Department Meetings (Eduardo)I&T/SVAC Department Meetings (Eduardo)• Date : Weekly (Friday)• Location : SLAC , Group C conference Room, B84• Goal : Prepare for data analysis of pass and fail tests and instrument data analysis.
(Working meeting, those interested in contributing are welcome.)
– PASS/FAIL tests– Review plots from subsystems to evaluate if changes are necessary for tests
at the integrated level. – Scheduled a meeting on April 30 between I&T (SVAC and Online), SAS and
ISOC to discuss monitoring of parameters during integrated tests and details of implementation and present SVAC tool to monitor offline calibrations.
– SAS recon analysis may not be required at this level but we may use SAS code for digitized data (TBR)
– I&T driven effort
– Instrument test Analysis – LAT Collaboration effort. See next slides
– Infrastructure necessary – SAS Data pipeline (OPUS) , MC and GlastRealease– Data analysis code to estimate run time needed during data taking– Offline Report generation – We were given no requirements so far– Tool to compare offline results - We were given no requirements so far.
GLAST LAT Project Face to Face Managers Meeting 04/14/04
4.1.9 - Integration and Test 6
SVAC Instrument Analysis Workshop 1SVAC Instrument Analysis Workshop 1
• Date : June 7 (Monday) and 8 (Tuesday), 2004
• Location : SLAC , June 7 (ROB C&D) , June 8 (TBD)
• Goal : Prepare for data analysis during LAT build and testing.
– Produce MC datasets with two-towers in a grid at different configurations to
– Validate geometry implementation
– Create datasets for data analysis
– Recommend data set sizes based on MC studies
– Define and assign tasks to participants to
– Evaluate if there are modifications necessary to the reconstruction
– Evaluate if there are modifications necessary to the analysis (merit) ntuple
– Create reference plots for different configurations
– Define infrastructure necessary for
– Data pipeline (OPUS)
– Report generation
– Comparison of results
GLAST LAT Project Face to Face Managers Meeting 04/14/04
4.1.9 - Integration and Test 7
Instrument Analysis Workshop 2Instrument Analysis Workshop 2
• Date : Early July 2004 (TBD, depends on IRR) • Location : SLAC • Goal : Evaluate MC results and implement changes needed for
data analysis of LAT data obtained during various stages of the build and testing.
– Evaluate results and regenerate MC datasets if necessary– Suggest modifications for data analysis tests with real data and flight
hardware– Work with I&T to evaluate if the data set sizing is
– adequate to understand the instrument – and if collection times fit the LAT build and test schedule.
– Define what analyses will be done during the build sequence. – The plan is to have data taking with 1,2,4,6,8,10,12,14,16 towers and 16
towers with ACD.
– Define infrastructure needed for full LAT analysis
GLAST LAT Project Face to Face Managers Meeting 04/14/04
4.1.9 - Integration and Test 8
Interdependencies: subsystems, LAT office and/or project office.
• Completion of LAT-MD-02730 “LAT Performance and Operations Test Plan”
• Input on specific processes/procedures for integration (subsystems).
• EGSE deliveries from Electronics (see following chart).
• Tracker Mechanical mock-up and 5 tray mini-tracker tower parts from Tracker.
GLAST LAT Project Face to Face Managers Meeting 04/14/04
4.1.9 - Integration and Test 9
I&T Overview to Start of IntegrationI&T Overview to Start of Integration
Training & Procedure Verification
6/18/04
Integration Procedures
Mechanical and Electrical6/18/04
Integration Readiness
Review7/8/04
I&T Mockup4/1/04
LATTE v.3.04/1/04
I&T PlanLAT-MD-01376
5/1/04
I&T Functional Test Scripts
6/1/04
MGSE Development
Plan v.25/15/04
Drawings5/1/04
Fabrication6/14/04
Proof Testing7/21/04
Receive Flight
Hardware Start
Integration
* Final though two tower CPT, releases to support integration procedure development
LATTE v.3.n V &V5/8/04 – 7/8/04
Bldg 33 Cert6/18/04
Particle Test Equipment
6/18/04
Training & Script Verification
6/1/04 – 7/1//04
Survey Plan5/1/04 draft (done)
5/31/04 final
RequirementsLAT-MD-02730
6/10/04 *
Electronics Test-Bed
5/04
Subsystem Scripts5/1/04
EGSE Hwr Deliveries
6/1/04
Electronics Test-Bed
5/04
GLAST LAT Project Face to Face Managers Meeting 04/14/04
4.1.9 - Integration and Test 10
Electrical Ground Support Equipment (EGSE) / Online FlowElectrical Ground Support Equipment (EGSE) / Online Flow
Integration Readiness
Review7/8/04
LATTE v.3.0 with GASU
support4/1/04
I&T Functional Test Scripts
6/1/04
Training6/18/04
Peer Review6/18/04
LATTE v.3.n V &V5/8/04 – 7/8/04
Event Pre-scaling5/8/04
Security – Configuration
Control 5/8/04
LATTE v.3.n release5/8/04
Script / Software Configuration
Control7/8/04
Electronic Logbook / Mate-
Demate Log6/1/04
Electronics Test-Bed
5/04
Subsystem Scripts5/1/04
EGSE Hwr Deliveries
(Electronics)6/1/04
Power Up Sequence
5/8/04
Hardware Monitoring
5/8/04
GLAST LAT Project Face to Face Managers Meeting 04/14/04
4.1.9 - Integration and Test 11
Science Verification, Analysis, and Calibration (SVAC) - RoadmapScience Verification, Analysis, and Calibration (SVAC) - Roadmap
Integration Readiness
Review7/8/04
SVAC Database and Calibration trending(March - July)
SVAC Acceptance and Test of SAS Algorithms (May - July)
1 & 2 Tower Geometry
(April – May)
SAS Calibration Algorithms(May)
SAS Database(May)
SAS Pipeline Infrastructure(March - April)
MC Datasets 1 & 2 tower
(May)SAS Geometry Review(April)
SVAC Data Pipeline(May-June)
EM 1 data analysis(March - May)
EM 2 data analysis(April - June)
SVAC Workshops(June-July)
Instrument Test Analysis(March – July)
GLAST LAT Project Face to Face Managers Meeting 04/14/04
4.1.9 - Integration and Test 12
Critical issues I want discussedCritical issues I want discussed
• Finalization of LAT test requirements• EGSE definition document needs to be completed.• EGSE delivery plan. Is current schedule still OK?• Time table for finalization of TKR-Grid interface and installation
sequence.• Tracker support for I&T mechanical model( delivery dates) .
– Flight cable design– Spare trays– 5th live tray