Data Access

Contents

  1. Data Access
    1. Run Query
    2. Good Runs Lists
    3. Interesting Runs
    4. Luminosity Calculation
    5. TAGs
    6. Trouble shooting
    7. Detector Description and Condition

Run Query

http://atlas-runquery.cern.ch/

Good Runs Lists

https://twiki.cern.ch/twiki/bin/view/Atlas/GoodRunsLists

https://twiki.cern.ch/twiki/bin/view/Atlas/GoodRunsListsTutorial

https://twiki.cern.ch/twiki/bin/view/AtlasProtected/GoodRunListsForData

Interesting Runs

https://twiki.cern.ch/twiki/bin/view/AtlasProtected/InterestingRuns2009

Luminosity Calculation

https://twiki.cern.ch/twiki/bin/view/Atlas/CoolLumiCalc

https://twiki.cern.ch/twiki/bin/viewauth/Atlas/CoolLumiCalcTutorial

TAGs

https://twiki.cern.ch/twiki/bin/view/Atlas/CommissioningTag

Trouble shooting

When running over ESDs first, encountered problems with database access, error messages like: 

IOVDbSvc     ERROR Tag COMCOND-ES1CT-003-00 cannot be resolved for folder /LAR/Align

Reason: Database conditions not properly set

Solution: In exeSingleTopDPDMaker.py add somewhere at the beginning (e.g. before sequence initialisations): 

from AthenaCommon.GlobalFlags import GlobalFlags
GlobalFlags.DetGeo.set_atlas()
GlobalFlags.DataSource.set_data()
from IOVDbSvc.CondDB import conddb

Details can be found:

Second error: POOL file GUID requested by COOL is not found in the attached catalogues. Gives messages like: 

T_AthenaPoolCnv                           ERROR poolToObject: caught error: FID "74981861-8AD2-DE11-95BD-001CC466D3D3" is not existing in the catalog ( POOL : "PersistencySvc::UserDatabase::connectForRead" from "PersistencySvc" )
PixelDetectorManager                      ERROR Cannot find AlignableTransformContainer for key /Indet/Align - no misalignment
PixelDetectorManager                      FATAL Unable to apply Inner Detector alignments

Solution: could be resolved by either running on lxplus, where database is up-to-date or by following instructions here:

On lxplus do: 

grep -A 2 74981861-8AD2-DE11-95BD-001CC466D3D3 /afs/cern.ch/atlas/conditions/poolcond/catalogue/poolcond/PoolCat_oflcond.xml

or 

grep -A 2 74981861-8AD2-DE11-95BD-001CC466D3D3 /afs/cern.ch/atlas/conditions/poolcond/catalogue/poolcond/PoolCat_comcond.xml

In this case, as we are looking at data, only the second gives output. Mind the different names for the xml-files for Monte Carlo and real data.

Copying /afs/cern.ch/atlas/conditions/poolcond/catalogue/poolcond/PoolCat_comcond.xml to the share directory of SingleTopDPDMaker fixes the problem.

If it still doesn't work then (was the case for me when processing mc09_900), follow the instructions given here and create a local database: https://twiki.cern.ch/twiki/bin/view/Atlas/AthenaDBAccess#Switching_to_use_local_SQLite_fi 

ln -s /afs/cern.ch/user/a/atlcond/coolrep/sqlite200 sqlite200
ln -s /afs/cern.ch/atlas/project/database/DBREL/packaging/DBRelease/current/geomDB geomDB

Detector Description and Condition

You have to make sure you set the right detector conditions. There have been defined several new conditions, details:

ATLAS: ClemensLange/DataAccess (last edited 2010-01-14 16:19:24 by ClemensLange)