TileCommissioningAnalysisPre2009 < AtlasArchive

AtlasArchive Web>AtlasCalorimeter>TileCommissioningAnalysisPre2009 (2009-05-29, JoseManeira) (raw view)
%CERTIFY%
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic!
If you have any comments/complaints about this template, then please email me:
edward.moyse@cern.ch
--> 


<!-- By default the title is the WikiWord used to create this topic !-->
<!-- if you want to modify it to something more meaningful, just replace %TOPIC% below with i.e "My Topic"!-->
---+!!<nop>Atlas.TileCal Commissioning: offline software and analysis 
%TOC%
%STARTINCLUDE%

---+ATLAS Releases
As of October 1st 2006 Release 12.0.3 + some extra tags should be used for the reconstruction of commissioning data. Working setup with all aditional packages can be found in */afs/cern.ch/uset/t/tilebeam/commissioning/reco-12.0.3*. See Atlas.TileStandaloneReconstruction page for more information about releases and packages to use.

---+Detector Description
<!-- Add an introduction here, describing the purpose of this topic. !--> 
We are using full ATLAS Detector Description for simulation and reconstruction of the commissioning data.
!Atlas.GeoModel tag ATLAS-DC3-02 is good enough, but any newer tag can be used.
 
---+Simulation
<!-- Add an introduction here, describing the purpose of this topic. !--> 
will be updated soon

---+Calibration constants
<!--Add the main topic here. i.e. create some new headings as follows:!-->
CIS calibration constants can be calculated inside Athena snd stored in POOL file (see Atlas.UsingTileCalibAlgs). After that the POOL file can be registered in COOL database with Atlas.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 (12.0.X), one can activate reading from COOL by adding two lines in jobOptions: <br>
*tileUseCOOL = True* <br>
*include( "TileCOOL_jobOptions.py" )* <br>
The latest COOL database setup with all calibration constants can be always found in */afs/cern.ch/user/t/tilebeam/online/conditions*.
For the moment only very few calibration constants are stored in COOL. Once we have CIS data for all modules, 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 !Atlas.TileCell objects will be the same as in !TileRawChannels, namely !pCb (factor 0.5 - 2 from !GeV).

When reading from COOL database is switched off, default CIS calibration is applied (which is 1023/800 ADC counts/pCb for low gain and 1023/12.5 ADC counts/pCb for high gain). Those defaults for any channel in any drawer can be overwriten in simple ASCII file. The name of this ASCII file is *Tile2006.fit* for CIS calibration constants for fit method and it should be placed in the directory where Athena is running. Example of this file is available in share directory of !TileCalorimeter/Atlas.TileConditions package. Another important file is *Tile2006.las* which contains LED time corrections for all the modules in the pit.
This file is also available from !Atlas.TileConditions package. For all drawers which are not listed in the file time correction is equal to zero. 

---+Reconstruction
<!--Add the main topic here. i.e. create some new headings as follows:!-->
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 *jobOptions_TileMobiComm.py* and *jobOptions_TileMobiCosmic.py* from *TileCalorimeter/TileExample/TileRecEx* package. The first one is tuned for calibration runs like CIS, Ped, LED, !MonoCIS. The second one is used for reconstruction of cosmic data. There are a lot of comments in these !jobOptions files. It's enough to provide run number and run type at the command line and you'll have ROOT ntuple and/or monitoring histograms as output. If something is not clear, read detailed instructions at
Atlas.TileStandaloneReconstruction page.

Ntuple created with *jobOptions_TileMobiCosmic.py* is identical to the !Atlas.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 
<!--Add the main topic here. i.e. create some new headings as follows:!-->
!TileMonitoring package in Athena contains several algorithms which can be used at the Event Filter to create monitoring histograms. The same package has special algorithms to create Level 1 commissioning histograms
Instructions how to setup this package are given at [[Atlas.TileMonitoringAthena][separate page]].

---+Analysis
<!--Add the main topic here. i.e. create some new headings as follows:!-->

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


<!-- MAJOR UPDATES
For significant updates to the topic, consider adding your 'signature' (beneath this editing box) !-->
-----
*Major updates*:%BR%
<!--Future editors should add their signatures beneath yours!-->
-- Main.SanyaSolodkov - 15 Jun 2005
-- Main.SanyaSolodkov - 25 Oct 2006


%STOPINCLUDE%
<!--Please add the name of someone who is responsible for this page so that they can be contacted if the contents need updating! The creator's name will be added by default using the REVINFO function, but this can be replaced if appropriate.-->
%RESPONSIBLE% %REVINFO{"$wikiusername" rev="1.1"}% 
%BR%
<!--Once this page has been reviewed, please add the name and the date e.g. Main.StephenHaywood - 31 Oct 2006 -->
%REVIEW%
Topic revision: r8 - 2009-05-29 - JoseManeira
AtlasArchive
Public webs
- Cern Search
- TWiki Search
- Google Search
Atlas All webs
Copyright &© 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