TileCal Commissioning: offline software and analysis

ATLAS Releases

Release 10.5.0 of ATLAS software should be used for the reconstruction of commissioning data. Previous releases work as well but not all jobOptions files are available in those releases.

Instead of reading calibration constants from ASCII files, it is possible now to load them from COOL. This option is disabled by default because some modifications are required on top of release 10.3.0 to work with COOL database (see below). Current working setup with all modifications applied can be always found in /afs/cern.ch/user/t/tilebeam/online/conditions

Detector Description

We are using full ATLAS Detector Description for simulation and reconstruction of the commissioning data. The easiest way to initialize GeoModel with TileCal only is to include TileGeoModel/TileGeoModel_jobOptions.py in your jobOptions. If you are including TileTBRec/TileTBGeoModel_jobOptions.py wrong geometry will be initialized.


will be updated soon

Calibration constants

CIS calibration constants can be calculated inside Athena snd stored in POOL file (see UsingTileCalibAlgs). After that the POOL file can be registered in COOL database with TileC tool. For the moment we are using pcata007 as the database server and will migrate to coolpro soon. Reading of these constants back is possible with current release (10.5.0), one can activate reading from COOL by adding two lines in jobOptions:
tileUseCOOL = True
include( "TileCOOL_jobOptions.py" )
For the moment only calibration constants for CTB2004 are stored in COOL. Once we have CIS data for cosmics setup, we'll put constants in the database. Remember that Cesium calibration constants are not available for Cosmics runs, so GeV scale for TileCells can not be set and energy in TileCell objects will be the same as in TileRawChannels, namely pCb (factor 0.5 - 2 from GeV).


If you know how to run Athena and how to edit jobOptions file, all you need to know is the name of jobOptions file, it is TileTBRec/jobOptions_TileMobi.py. There are a lot of comments in this jobOptions file. It's enough to provide proper input file name and you'll have ROOT ntuple as output. If something is not clear, read detailed instructions at TileMobiDAQReconstruction page.

Ntuple created with jobOptions_TileMobi.py is identical to the TileCal testbeam ntuple which we had in the past. The only difference is in the naming of the drawers: at the testbeam we had A0, A1, A2, C0, C1, C2, E0, E1, E2 and in commissioning ntuples we should have A13, A14, A45 A46, C13, C14, C45, C46. And if arrays in ntuple are ordered according to channel number instead of PMT number (convenient for CIS analysis), name of the arrays will contain hex fragment ID ( e.g. 100, 101, 102, 200, 201, 202) as it was before.

Event Filter Monitoring

TileMonitoring package in Athena contains several algorithms which can be used at the Event Filter to create monitoring histograms. Instructions how to setup this package are given at separate page.


List of runs taken in the pit as well as list of available ntuples is given at TileMobiDAQAnalysis page

Major updates:
-- SanyaSolodkov - 15 Jun 2005

Edit | Attach | Watch | Print version | History: r8 < r7 < r6 < r5 < r4 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r5 - 2005-10-04 - SanyaSolodkov
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Atlas All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback