Data Analysis from I&T: lessons learned

1. Data Analysis from I&T: lessons learned Eduardo do Couto e Silva March 20, 2006 Pisa Workshop – Beam Test 2006

2. I&T Determination of operational settings Calibrations Timing Instrument characterization Debugging Performance Trending MC comparisons Beam Test MC tuning Performance particle type and beam energies Verification of Calibrations and timing Data Analysis Activities

3. What can we use from I&T? • LAT Hardware Operational settings • Verify that calibration and timing have not changed • May require tuning at higher energy beam • No significant deviations expected from temperature changes • Trigger may have different focus • I&T (mostly internal) • Recently: multiple trigger engines • Beam Test (mostly external) • Infrastructure is useful (to be tailored for the BT) • Offline data analysis stream (ntuples, docs, code) • Ntuple documentation should have priority • Runs database and pipeline for data processing • Need to modify current runs log to add new queries • See previous Beam Test log too !

4. Data Analysis Coordination • Expect about 1-2 months to ramp up people for data analysis • build familiarity with goals and tools • develop documentation • Need to identify tasks at all levels of difficulty and everyone can contribute • Validation of infrastructure and debugging • Easy to get help from Collaboration but • takes at least 1 person to daily monitor activities and steer people prior to beam test • Needs coordination with IA Group • Beam Test Goals (PSF, energy resolution, etc.) • better to identify leads • Needs coordination with C&A group

5. BT: Three Areas of Data Analysis Activities • Ancillary Detectors: • In the previous BT at SLAC (1999/2000) the data was used blindly, no insight and/or flexibility on cuts for PID and photon tagging • CU: Verification of Calibrations and timing and trigger properties • Most likely a smaller group with strong knowledge of hardware and software • Unrealistic to expect the general user to be able to help here • Needs coverage (enough people) at early stages of tests: CR at CERN and beginning of PS and SPS activities • Check for common mode noise • CU: MC tuning and performance for different particle type and beam energies • Verify statistics needed for data taking for most of the configurations • Study beam backgrounds from experimental set-ups and simulations of beam properties • Validate MC geometry • Perform main beam test goals (PSF, energy measurements…) • Development of tools/analysis for • operations in a beam • Cross check predictions for statistics and background • Monitor instrument performance • MC tuning

6. BT Data Analysis Phases • Collaboration needs to be engaged at all phases looking at data and debugging ntuples • Testing at Pisa • Develop custom reports for detector data and debug BT ntuple • Performance and calibration of CU • Testing with Cosmic Rays at CERN • Refine BT ntuple • Final testing on strategy to verifying calibrations and timing • PS/SPS simulations • Evaluate statistics needed for data taking (# triggers and # of photons) • Which precision? • Develop new variables into BT ntuple • Use the C&A meeting to help in the process of defining the main measurements we want to make • PS/SPS data analysis • Worry about detector specific variables • ACD recon • Leads shall organize the group to get the final measurement done

7. Proposal for Working Group • Expectation for this meeting • Develop a list of tasks to support the 4 phases mentioned in the previous slide • tentative timeline • Focus on development of infrastructure • Online/offline analysis plots to diagnose detectors and beam • evaluation of duration of data taking required (overlaps with Simulation working group)