GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 1/31 Overview of End to End Runs Eduardo do Couto e Silva April 1, 2005 ( not it is not a joke, we finally took data!)

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 2/31 Overview of End to End Runs We successfully completed all end to end runs for Tower A The infrastructure for data analysis is in place and working well –All plots in this presentation were obtained from the SVAC reports which are automatically generated at the end of the runs –Please use them and give us feedback Two tower tests will occur in 1 to 2 weeks –We need to look at these data to provide inputs to the test plan

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 3/31 Retrieving end to end runs Go to the Runs databasedatabase To get all runs Query on –Script name: end2end –Completion Status: PASSED –Duration: > 100 –Bear in mind that Americium runs are 1 min long ! Look at Config report and digi and recon reports –Currently we are updating the reports based on the results from these runs –Comments are welcome –Please come to our Friday meetings if you want to participate

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 4/31 Retrieving Runs from the Database Can select only one test ID For all runs fill the fields the red boxes

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 5/31 Results from Database… Data Quality Reports TEST ID Serial Number

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 6/31 Run Numbers (1) There are more runs with ID’s 4/5 and 4/6

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 7/31 Run Numbers (1)

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 8/31 Event Trigger Rate CAL_LO only Am241 VDG 1 kHz 5 kHz 10 kHz 20 kHz 1 kHz Horizonta cosmicsl 4 range Zero Sup OFF 10 KHz 10 kHz VDG Rates agree to expectations

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 9/31 Error Events for Tower A Read TKR from one side only So far we found no packet nor parity errors. Only TEM errors were found VDG

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 10/31 Number of Events for Tower A Am241 CAL_LO only 4 range Z. Sup OFF VDG 2 hour runs VDG

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 11/31 Event Size for Tower A (bytes) Z. Sup OFF 4 range Z. Sup OFF 4 range Z. Sup OFF CAL_LO only VDG Z sup OFF For Cosmic rays expected about 300 bytes, CAL 4 range, TEM diag ON, Z Sup ON 200 bytes, CAL 1 range, TEM diag OFF, Z Sup ON 1700 bytes, CAL 4 range, TEM diag ON, Z Sup OFF VDG Z sup ON

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 12/31 Size of Raw FITS file 2 hour runs VDG Am241 Z. Sup OFF Every file is below 100 Mbytes, for 2 towers we want to raise the limit to 200 Mbytes

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 13/31 Digi File Size (Mbytes) Zero Sup OFF Zero Sup OFF

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 14/31 Recon File Size (GBytes) Digi timed out in pipeline 4 range has a bug in recon (fixed on the next relesease) 4 range has a bug in recon (fixed on the next relesease) Am241 and Some VDG runs Not available prior to this talk Pipeline had a recon limit of 1.8 Gbytes in jobOptions (left over from the times when we did not have ROOT 4) and some jobs failed. We also believe we need a faster turn around on processing of recon files, maybe for 2 tower tests we need to try the special queue deal with SCS

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 15/31 Ratio of Digi/Raw I am sure Heather will have fun looking into these differences….

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 16/31 Ratio of Recon/Digi file Now Heather will have a blast…. It deserves some investigation… Zero Suppression ON Zero Suppression OFF

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 17/31 Baseline Run , ID 1/1 : GEM Triggers TKR ~ DAC 30 CAL_LO ~ 100 MeV (rate agrees with expected rate when only CAL_LO is turned on see ID 3/1) TKR + CAL_LO CAL_HI ~ 1 GeV (what are these events?) TKR + CAL_HI TKR + CAL_LO Can we have a “pure” CAL_HI without a CAL_LO?

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 18/31 CAL_HI Trigger: Run event Didn’t trigger the tracker with 14 clusters associated with a track?!!! CalEnergySum = 25 MeV

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 19/31 CAL_HI Trigger: Run event Triggered CAL_HI with 24 MeV? CalEnergySum = 24 MeV

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 20/31 CAL_HI Trigger: Run event 7602 CalEnergySum = 44 MeV

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 21/31 CAL_HI Trigger: Run event CalEnergySum = 143 MeV

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 22/31 CAL_HI Trigger: Run event Didn’t trigger the tracker with 14 clusters associated with a track?!!! CalEnergySum = 56 MeV

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 23/31 External 1 KHz Run , ID 4/1: GEM Triggers TKR ~ DAC 30 CAL_LO ~ 100 MeV TKR + CAL_LO CAL_HI ~ 1 GeV TKR + CAL_HI TKR + CAL_LO We will modify SVAC reports to have better resolution on plots External triggers (last bit) from pulse generator External + software triggers

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 24/31 Runs with different TKR thresholds Run , ID 1/1, LOW Threshold TKR DAC ~ 30 Run , ID 2/3, NOMINAL threshold TKR DAC ~ 22 Fraction of events with Strip hits but TOT = 0

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 25/31 TKR readout from one side only: Average TOT Only LO/Left side cables are read out Only HI/Right side cables are read out Run , ID 2/6 Run , ID 2/7 Note that the color pattern is remarkably similar for both runs Units of counts 1 count = 200 ns

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 26/31 Lower TKR thresholds : Number of hit planes 0.22% < 6 planes 0.07% < 6 planes Run , ID 1/1, TKR DAC ~ 30 Run , ID 2/3, TKR DAC ~ 22

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 27/31 High Rate Runs Am241 (TKR and CAL are allowed to trigger) Only the pulse generator Is allowed to trigger (1 kHz) Run , ID 4/5 Run , ID 4/6

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 28/31 GEM Time Interval : High Rate Runs Run , ID 4/5 Run , ID 4/6 Run , ID 4/1 Run , ID 4/2 5 kHz (TKR and CAL are allowed to trigger) Only the pulse generator Is allowed to trigger (1 kHz) TKR and the pulse generator are allowed to trigger (1 kHz) TKR, CAL and the pulse generator are allowed to trigger (5 kHz)

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 29/31 VDG Runs Tower boundary Reconstructed XY positions Fraction of events with 0 hits (red means 0 events) Very few events make into the thick layers ~ 80% of events have at least one track Run , ID 9/1 Trigger rate ~ 100 Hz

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 30/31 High Priority “Projects” Demonstrate that the pulse generator works as expected. –Do we have all the configurations we need to understand the behavior at high rates? –Should we lower the CAL LAC threshold (for one column) to load the CAL with data and allow a fair comparison of deadtime? Do files sizes and deadtime make sense for the possible permutations of the main register configurations? –(1/4) CAL range readout, zero suppression (ON/OFF), TEM diagnostics (ON/OFF) Are there differences in distributions that could be ascribed to different timing when reading out only from LO or HI side of TKR cables? –Of course use baseline as a reference Are there idiosyncrasies in the Error events? –Need to explore in electronics and physical space Need to study topologies and rates of different trigger types –As many runs as possible More ideas? –Volunteers?

GLAST LAT Project Apr 1, 2005 E. do Couto e Silva 31/31 Summary This week we all made an spectacular progress ! –Thank you all Today we will change the code in the pipeline (bug fixes) –We will reprocess all runs Depending on your analysis you do not need to wait for the pipeline –Go ahead and adopt a run Please let me know how you want to contribute for the data analysis –We need to plan quickly for the two tower tests that will happen in 1 to 2 weeks