1. GLAST LAT Project 1 Tracker “mini-tower” Full Size Calorimeter module Face to Face IDT meeting March 20, 2002 Convener: E. do Couto e Silva Engineering Model/Prototypes schedule including its use for GSE testing Outline Objectives Hardware Software Important Dates

2. GLAST LAT Project 2 Objectives I General –Dress rehearsal of CU and LAT activities –Understand and exercise interfaces across subsystems to facilitate I&T coordination during CU and LAT activities –Surface issues that may affect our schedule during CU and LAT activities Team building –Must have involvement of non–US collaborators to develop enough strength for CU and LAT activities Test and procedures –Handling (minimal) –Transportation (minimal) –Functional testing (rely on subsytems, I&T will provide support) Mechanical and Electrical –Subsystem level tests (not necessarily I&T issues)

3. GLAST LAT Project 3 Objectives II Data analysis –Reconstruct low energy photons from Van der Graaf –Measure energy spectrum and resolution (?) Calibration –Test TKR low level calibration procedures –Test CAL high and low level calibration procedures –Test DAQ calibration procedures –Verify ACD response to low energy photons ? EGSE –Test Hardware/software/scripts/GUI –First pass at FITS format (raw data only) –Test SCL database

4. GLAST LAT Project 4 Objectives III SAS Software (EM will test some of the SAS tools) –New geometry scheme (via XML) –GEANT4 –TKR and CAL calibration algorithms –SAS calibration database –Data Manager and infrastructure for MC generation IOC –I&T EGSE and SVAC products will be used to prototype operations tools

5. GLAST LAT Project 5 Engineering Model (EM) hardware Engineering Model (EM) hardware ACD –No hardware has been planned so far. Shall we try to get some tiles ? TKR –4 trays fully instrumented (silicon and electronics) and tested (3 with no converter, 1 with thick converter). Maybe an additional bottom tray not instrumented ? CAL –Fully instrumented ? EGSE –Single TEM with “pseudo GLT” (no Event builder) If ACD then needs an Event Builder. How complicate does that become ? Cosmic Ray Telescope –Do we need a telescope for external triggering or is self-triggering sufficient ?

6. GLAST LAT Project 6 Engineering Model (EM) software Engineering Model (EM) software SAS –MC Simulation What is the strategy for comparing GEANT4 and GISMO ? Which MC distributions do we validate ? First test of the new geometry scheme –RECON Any new algorithms ? Does the small number of planes become a burden ? –SAS Calibration Database. First test of the database concept EGSE/Online –EGSE Test Interface (API) –Data Formats Raw Data in FITS format, RECON in ROOT –Scripts (data taking, functionality, monitoring and calibration) Will most scripts be produced by subsytems ?

7. GLAST LAT Project 7 Engineering Model (EM) software Engineering Model (EM) software I&T/SVAC –Data analysis Are the current C++ analysis classes and ntuple adequate ? Do we need any script/macro/ beyond what SAS normally deliver ? –Database. First test of prototype database (http://www-glast.slac.stanford.edu/LAT/INT/SVAC/Database/svac_prototype_database.htm) First test of SVAC/SAS interface IOC –Prototype of Operation Tools concept. Who will define and develop the web page, procedures, automated reports, electronic log book, etc…? Does that help IOC CDR ?

8. GLAST LAT Project 8 Proposed Dates for the EM effort EM data taking (~60 days) - Jan 27, 03 – Mar 25, 03 Hardware –TKR EM to SLAC – Dec 02 (stays at SLAC) –CAL EM to SLAC – Jan 03 (returns to CAL subsystem) –I&T ready by Dec 02 (depends on I&T schedule) –SAS ready by Dec 02 (planning for summer 02) –EGSE ready by Apr 02 (since subsytems need them) Software –EGSE scripts – Sep 02 (depends on I&T schedule) –SAS - MC simulation – Jun 02 (planning for summer 02) –SAS - New RECON – Jun 02 (planning for summer 02) –SAS - calibration database – Oct 02 (current planning) –I&T - SVAC database – Nov 02 (depends on I&T schedule) –IOC - ops tools – Nov 02 (depends on I&T schedule)

9. GLAST LAT Project 9 “Calibration” On orbit calibration Science Requirement Document On-board calibration Ground monitoring On-board monitoring Ground calibration I&T SVAC Plan Ground monitoring Ground calibration 443-SRD-00010 S. Ritz note – see next slides LAT-MD-00446 Systems Engineering, can you please check flow down of requirements from L2 to L4 ?

10. GLAST LAT Project 10 Low Level Calibration Charge injection Map of Hot and dead strips TKR Data using SAS software Number of Hot and dead strips TKR Monitoring Calibration Map of Hot and dead strips TKR histograms On board Ground On board Ground

11. GLAST LAT Project 11 High Level Calibration “simple” track finding Alignment Data using SAS software Residuals? Monitoring Calibration Alignment histograms On board ?Ground On board Ground

12. GLAST LAT Project 12 Needs Revision and feedback The baseline is that we collect calibration data during normal event data taking. Do we need one or more special modes ? –Tracker alignment may require ~ 10000 tracks per tower –ACD efficiencies may be better calibrated when tracks are matched to pulse heights –CNO mode ~ 10 Hz (?) of GCR for CAL calibrations –Electronic calibrations (charge injection) may need a special node ? What can be done on board and what is calibrated on the ground ? What is the frequency of calibrations ?

13. GLAST LAT Project 13 On orbit calibration 1 ( from S. Ritz) Reviewed by I&T Committee Meeting June 1, 2001 Present: Tony, Martin, Scott Williams, Scott Sawyer, Eduardo, Hartmut, Bob Hartman, Steve, Tune Also sent to: Dave Thompson, Dave Bertsch, Seth Digel, Peter Michelson

14. GLAST LAT Project 14 Reviewed by I&T Committee Meeting June 1, 2001 Present: Tony, Martin, Scott Williams, Scott Sawyer, Eduardo, Hartmut, Bob Hartman, Steve, Tune Also sent to: Dave Thompson, Dave Bertsch, Seth Digel, Peter Michelson On orbit calibration 2 ( from S. Ritz)

15. GLAST LAT Project 15 From LAT-MD-00446 Needs revision from subsystems and systems engineering I&T SVAC Plan on orbit

16. GLAST LAT Project 16 From LAT-MD-00446 Needs revision from subsystems and systems engineering I&T SVAC Plan Pre launch

17. GLAST LAT Project 17 ACD On orbit calibration LAT-MD-00446 Needs revision from subsystems and systems engineering I&T SVAC Plan To revise data volume metadata data taking time required bandwidth calibration strategy (on board, ground)

18. GLAST LAT Project 18 CAL on orbit calibration LAT-MD-00446 I&T SVAC Plan

19. GLAST LAT Project 19 Tracker calibrations are dominated by alignment, which is performed once a month (TBR) on the ground using telemetry data. We expect only tray alignment calibrations will done at least once after launch. The baseline (TBR) alignment (layer) requires 10000 tracks (TBR) crossing most of the layers of each tracker tower. The exact number is TBD and depends on the criteria used to select the event sample with larger number of straight tracks (proton-like). For all sixteen towers we will require 16 10 5 charged tracks and if we expect a maximum of three hits per layer with 2 byte/hit we obtain 2.7 10 5 Kbits. Statistics are generous to allow sufficient tracks to align at the ladder and SSD level (once a year - TBR). The planning for operations shall include four dedicated runs for alignment at the tower level for positions at sun minimum and maximum and entering and leaving the SAA once every 2 months (TBR). The time over threshold can use the same 10000 tracks/tower designed for the alignment but extra information needs to be send to the ground. If we assume 2 TOT values/layer of 1 byte each we obtain 4.5 10 4 Kbits. TKR on orbit calibration LAT-MD-00446 I&T SVAC Plan