1
Calice TB Review DESY 15/6/06
D.R. Ward
David Ward
Post mortem on May’06 DESY running.
What’s still needed for DESY analysis?
What’s needed for CERN data taking?
Software
2
Calice TB Review DESY 15/6/06
D.R. Ward
Reminder - dataflow (agreed 16 Feb 05)
Mokka
LCIO
Calibration,
Alignment
Raw
Data
LCIO
(for analysis)
LCIO
Raw hits
(transient)
True
Energy
Decoding
Anti-Calibration
digitization
SimCalHits
Filtering
Raw LCIO
(blocks of integers?)
Mapping
Database
3
Calice TB Review DESY 15/6/06
D.R. Ward
DESY running May’06
ECAL electron data recorded 1-6 GeV at 4 beam positions, anglesfrom 0 to 45o
Elog is a useful resource to find info about data taken etc. (but slowto start up).
Data were converted to “raw LCIO” routinely. All stored at DESYdCache and accessible via Grid tools.
Detailed trigger information in separate data stream – not yet integrated– this needs fixing before we go to CERN. “Being tackled this week”(RP).
Monte Carlo issues:
Stagger of slab positions was changed in 2006. This has just (thisweek) been fixed in Mokka (new model TBDesy0506).
New layout of upstream detectors – F.Salvatore working with G.Musatto implement these in Mokka.
Need for track reconstruction for MC.
Digitization for ECAL MC. Procedure agreed at Montreal, but still needsto be implemented. Run as a Marlin pre-processor to reconstructionjob.
4
Calice TB Review DESY 15/6/06
D.R. Ward
Near-online monitoring (G.Mavromanolakis)
5
Calice TB Review DESY 15/6/06
D.R. Ward
DESY running May’06
“Reconstruction job” was run on all the usefuldata. Code mainly from Götz. This performedthe following steps:
ECAL mapping applied – hit indices and positions tomatch Mokka system.
Pedestal calculation and subtraction.
Zero suppression (S/N>5)
Trigger information is stored in event header, to flagpedestal, calibration, beam data etc. Peds and calibdata still included in the output stream.
No gain correction – no cosmic calibration dataavailable. LCIO CalorimeterHits are in ADC counts.
No Drift Chamber reconstruction. Raw data arecopied.
6
Calice TB Review DESY 15/6/06
D.R. Ward
Quick look at reconstructed files
Apply naïve 50ADC=1MIP gain correction for all channels.
Look at 1 GeV electrons at normal incidence.
This seems to be typical. Much less clean than 2005. Proportion of junkincreases with energy.
Single e
Double beam
Junk
•Significant work clearlyneeded to understand thebeam for 2006; to findgood cuts to clean up data
•Just as a first look, to seewhether reconstructed filesmake sense at all, I madea cut 100-250 MIP andcompared with single e MCfrom 2005.
7
Calice TB Review DESY 15/6/06
D.R. Ward
MC/data
8
Calice TB Review DESY 15/6/06
D.R. Ward
MC/data
As well as low energy “junk” events, it looks like genuine beamevents are commonly accompanied by junk as well. Needs carefulstudy. The data are going to be trickier to analyse than in 2005.
But otherwise, the data seem to make reasonable sense.
Main issues –
How to calibrate the detector? Wait for cosmics/muons at CERN? Tryto use electron data?
Need to sort out calibration and tracking in the drift chambers.
9
Calice TB Review DESY 15/6/06
D.R. Ward
CERN running
Data conversion and reconstruction job: plan is to transfer data toDESY and run jobs there. Possibly transfer Ntuples and/orreconstructed files back to CERN as needed. Relies on goodnetwork connection. Roman looking at the technicalities. We couldneed a fallback if this is slow/unreliable?
Changes to native DAQ format; integration of beam line detectors?Will necessitate updates to the data converter (RP). Could be asignificant amount of work. May not be available on day one. Needsliaison between Paul/Roman.
I’m less well informed about the preparedness of the AHCAL/TCMTsoftware.
Understanding the beam line is a significant task.
Ensure we have recorded all the information we need while running.
Need to simulate the beam properties realistically in Mokka.
Need code to reconstruct tracks, PID using Čerenkovs.
10
Calice TB Review DESY 15/6/06
D.R. Ward
Recommendations from Oct’05 TB Review
Monte Carlo: The detector groups should still considerwhether the information stored by MARLIN is sufficientfor their needs. I’ve heard no feedback. It seemsprobably adequate for the ECAL. A complete simulationof the beam line material in Mokka is greatly needed (foreach beam line we patronise). Under control for DESY.Need to support other Monte Carlo models (Geant3,Fluka etc).
Data analysis framework: Need to assess theadequacy of the present LCIO data. Consider addingtrigger summary information to event header. Done.Relevant slow controls info (temperatures, drift chamberpositions, detector angle etc) to event or database. Stillneeds doing? Make processors to read the dataavailable and get people using the code. Partiallyavailable.
11
Calice TB Review DESY 15/6/06
D.R. Ward
Recommendations from Oct’05 TB Review
Database: Need to populate the database with ECAL calibrationand configuration data; make tools to use this information available.Largely OK, I think.
Data storage: All members of Calice need to be informed howthey can access to these data, using either their DESY account orthe Grid-ftp tools. Number of Grid users increasing, but still small.Make available simple Grid jobs for data conversion, Monte Carloand Marlin-based analysis. These do exist. Need to think aboutdata storage options when running at CERN. Assuming, at present,that we use DESY.
Code sharing: Authors of code are still strongly encouraged to storetheir work at the CVS repository recently established at DESY-Zeuthen. Still valid.
Documentation: Documentation still needs to be improved. Asimple introduction “Calice Data analysis for Pedestrians” may help.Little progress.
General concern – over-reliance on a small number of experts,especially Götz and Roman. Shortage of people looking at data.