1. June 2004 ATLAS WeekAlexander Solodkov1 testbeam 2004 offline reconstruction

2. June 2004 ATLAS WeekAlexander Solodkov2 Testbeam reconstruction in Athena  Testbeam-related software is concentrated in 3 packages TileByteStream – unpacking of raw data TileRecUtils – signal reconstruction (flat filter, opt filter, fit method) TileTBRec – top level algorithms like TileTBNtuple, TIleTBDump, TileTBStat and jobOptions to run TileCal standalone testbeam reconstruction  Flat filter and fit method were debugged and are used now by default in reconstruction Ntuple contains results “Ene” and “EFit”, similar to last year ntuple, but name of the “drawer” is A0,A1,A2, C0,C1,C2 instead of P0,P1,P2, N0,N1,N2  New opt filter method from Valencia is being tested now Results of opt filter will also go to ntuple soon

3. June 2004 ATLAS WeekAlexander Solodkov3 How it works  One should setup CMT for release 8.2.x and run Athena: ~tilebeam/scripts/get_run athena.py TileTBRec/jobOptions_TileTB.py Standard ntuple (ROOT-based) is created athena.py TileTBRec/jobOptions_TileTBDump.py first 10 events are dumped on the screen very useful to understand what is inside raw data file and why ntuple has crazy values Hbook ntuple can be created instead of ROOT Take jobOptions_TileTB.py and uncomment few lines It is not possible to change record length for hbook ntuple, i.e. file size is limited to 256 Mb (64k of 4k records)

4. June 2004 ATLAS WeekAlexander Solodkov4 Calibration constants  For the moment we are reading constants from external ASCII files  File name prefix for all calibration files is specified in jobOptions Tile2003 for last year Tile2004 for this year  Those files are taken from share directory of TileConditions package and contain only default calibration constants (one and the same value for all channels)  We foresee migration to Conditions DB soon Will read real constants from DB Will use Interval of Validity Service Some jobOptions and calib algorithms will change

5. June 2004 ATLAS WeekAlexander Solodkov5 Combined reconstruction  As soon as we start taking data in combined mode, we’ll run “combined testbeam reconstruction” in Athena  First step of combined reconstruction is to read raw data and to create calibrated objects (e.g. TileCell or LArCell) – energy deposited in every cell, calibrated at EM scale  Results of reconstruction are stored in a POOL file Ntuple with some limited info can be created “by product” for debug purposes  Second step – read POOL file and do final reconstruction, e.g. cluster finding or hadronic calibration All tools and algorithms available in Athena can be used for reconstruction Results of reconstruction are saved as a set of final histograms and ntuples with reconstructed objects

6. June 2004 ATLAS WeekAlexander Solodkov6 Combined reconstruction (cont)  JobOptions for combined reconstruction are being prepared by Maria Costa and Michela Biglietti  Production tools are being tested by Vincent Giangiobbe and Mirea Dosil For the moment they are testing it with jobOptions_TileTB, i.e. they produce our standalone ntuple They will run combined reconstruction jobs as soon as we have data (after 2 nd of July)  Try to run Athena with some jobOptions now, to be ready to analyze new data!