TWiki
>
AtlasArchive Web
>
AtlasCalorimeter
>
TileCommissioningAnalysisPre2009
(revision 2) (raw view)
Edit
Attach
PDF
<!-- 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>TileCal Commissioning: offline software and analysis %TOC% %STARTINCLUDE% ---+ATLAS Releases Release 10.3.0 of ATLAS software should be used for the reconstruction of commissioning data. Previous releases (e.g. 10.0.4) 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 <!-- 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. 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. ---+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 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 not yet possible with current release (10.3.0). Some modifications are required in two core packages, namely *Database/IOVDbSvc* and *Control/IOVSvc* and also in *TileCalorimeter/TileConditions* package. Modified packages are available in *~tilebeam/online/condtions* (not yet in CVS). After those modifications are made, one can activate reading from COOL by adding two lines in jobOptions: <br> *tileUseCOOL = True* <br> *include( "TileCOOL_jobOptions.py" )* <br> 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). ---+Reconstruction <!--Add the main topic here. i.e. create some new headings as follows:!--> [[TileMobiDAQAnalysis][Reconstruction of data taken with Tile MobiDAQ]] ---+Analysis <!--Add the main topic here. i.e. create some new headings as follows:!--> 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. <!-- 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 %STOPINCLUDE%
Edit
|
Attach
|
Watch
|
P
rint version
|
H
istory
:
r8
|
r4
<
r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
Raw edit
|
More topic actions...
Topic revision: r2 - 2005-06-17
-
SanyaSolodkov
Log In
AtlasArchive
AtlasArchive Web
Create New Topic
Index
Search
Changes
Notifications
Statistics
Preferences
Public webs
Public webs
ABATBEA
ACPP
ADCgroup
AEGIS
AfricaMap
AgileInfrastructure
ALICE
AliceEbyE
AliceSPD
AliceSSD
AliceTOF
AliFemto
ALPHA
Altair
ArdaGrid
ASACUSA
AthenaFCalTBAna
Atlas
AtlasLBNL
AXIALPET
CAE
CALICE
CDS
CENF
CERNSearch
CLIC
Cloud
CloudServices
CMS
Controls
CTA
CvmFS
DB
DefaultWeb
DESgroup
DPHEP
DM-LHC
DSSGroup
EGEE
EgeePtf
ELFms
EMI
ETICS
FIOgroup
FlukaTeam
Frontier
Gaudi
GeneratorServices
GuidesInfo
HardwareLabs
HCC
HEPIX
ILCBDSColl
ILCTPC
IMWG
Inspire
IPv6
IT
ItCommTeam
ITCoord
ITdeptTechForum
ITDRP
ITGT
ITSDC
LAr
LCG
LCGAAWorkbook
Leade
LHCAccess
LHCAtHome
LHCb
LHCgas
LHCONE
LHCOPN
LinuxSupport
Main
Medipix
Messaging
MPGD
NA49
NA61
NA62
NTOF
Openlab
PDBService
Persistency
PESgroup
Plugins
PSAccess
PSBUpgrade
R2Eproject
RCTF
RD42
RFCond12
RFLowLevel
ROXIE
Sandbox
SocialActivities
SPI
SRMDev
SSM
Student
SuperComputing
Support
SwfCatalogue
TMVA
TOTEM
TWiki
UNOSAT
Virtualization
VOBox
WITCH
XTCA
Cern Search
TWiki Search
Google Search
Atlas
All webs
Copyright &© 2008-2022 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