RealDataLRSM

The purpose of this page is to trace all the problems with processing real data samples locally and on GRID and post here possible solutions to the observed issues. All processing is done with the use of LRSM MakerD3PD*

OTX selection

Event selection based on dead OTX regions removal could be done with the use of the following C++ code

/afs/cern.ch/atlas/groups/EGamma/OQMaps/checkOQ.C
/afs/cern.ch/atlas/groups/EGamma/OQMaps/checkOQ.h

900GeV MinBias

r988_p62 tag (the newer tag 1093_p56 does not contain LB info in metadata)

Run query command:

f r 141541+ and ptag data09_900GeV and st physics_MinBias and lhc beamenergy 449-451 and dq lar g and dq tile g and dq pix g and dq sct g and dq mdt g and mag s and mag t/ sh r

minbias_900GeV.xml

Full dataset name Number of events IL (ub^-1) delivered IL (ub^-1) MBTS_1 IL (ub^-1) MBTS_2 IL (ub^-1) MBTS_1_1
data09_900GeV.00142383.physics_MinBias.merge.AOD 72962 1.08986 1.0685 1.07725 1.07597
data09_900GeV.00142195.physics_MinBias.merge.AOD 59793 1.088247 1.07946 1.079508 1.079625
data09_900GeV.00142193.physics_MinBias.merge.AOD 119687 2.15643 2.1556 2.1557 2.15588
data09_900GeV.00142191.physics_MinBias.merge.AOD 80524 1.370385 1.36980 1.369843 1.36982
data09_900GeV.00142174.physics_MinBias.merge.AOD 18377 0.285204 0.27205 0.272013 0.271952

Total number of datasets: 5
Total number of events: 351343
Total integral luminosity (L1_MBTS_1): 5.94541 ub^-1
Total integral luminosity (L1_MBTS_2): 5.954314 ub^-1
Total integral luminosity (L1_MBTS_1_1): 5.953247 ub^-1

Full dataset name Number of events Cross section (mb) Integrated luminosity (ub^-1)
mc09_900GeV.105001.pythia_minbias.merge.AOD.e500_s738_s746_r1103_r1113/ 4998836 34.4 145.4
mc09_900GeV.105003.pythia_sdiff.merge.AOD.e466_s738_s746_r1103_r1113/ 4999961 11.7 428.2
mc09_900GeV.105004.pythia_ddiff.merge.AOD.e466_s738_s746_r1103_r1113/ 4799925 6.4 754.4

2TeV MinBias

Full dataset name Number of events IL (ub^-1) delivered IL (ub^-1) MBTS_1 IL (ub^-1) MBTS_2 IL (ub^-1) MBTS_1_1
data09_2TeV.00142402.physics_MinBias.merge.AOD 38578 0.454832 0.45045 0.450475 0.450421
data09_2TeV.00142308.physics_MinBias.merge.AOD    

Full dataset name Number of events Cross section (mb) Integrated luminosity (ub^-1)
mc09_2TeV.105001.pythia_minbias.merge.AOD.e499_s739_s746_r1112_r1113/ 999953 ?  
mc09_2TeV.105003.pythia_sdiff.merge.AOD.e499_s739_s746_r1112_r1113/ 999991 ?  
mc09_2TeV.105004.pythia_ddiff.merge.AOD.e499_s739_s746_r1112_r1113/ 799987 ?  

7TeV MinBias

Integral luminosity was calculated using online information, this is available with LumiBlockComps-00-00-92, some info here.

iLumiCalc.exe -t L1_MBTS_1 -x MyLBCollection.xml --online --lumichannel=0

For April(?)-May reprocessing please use the following version of LumiBlockComps package:

LumiBlockComps-00-01-08

Yellow+ DQ flags

Created on 2010-04-26. Using online integrated luminosity.

f r 152000+ and ptag data10_7TeV and lhc beamenergy 3450-3550 and lhc stablebeams true and dq lar y+ and dq tile y+ and dq pix y+ and dq sct y+ and dq mdt y+ and mag s and mag t

MyLBCollection_7TeV_yellow_stable.xml

Full dataset name Number of events IL (ub^-1) delivered IL (ub^-1) MBTS_1 IL (ub^-1) MBTS_2 IL (ub^-1) MBTS_1_1
data10_7TeV.00153200.physics_MinBias.merge.AOD.r1239_p140/ 531268 6.9455 6.9416 6.9416 0.0694
data10_7TeV.00153159.physics_MinBias.merge.AOD.r1239_p140/ 803520 10.1365 10.1223 10.1224 0.1012
data10_7TeV.00153136.physics_MinBias.merge.AOD.r1239_p140/ 47768 0.6081 0.6078 0.6078 0.0061
data10_7TeV.00153134.physics_MinBias.merge.AOD.r1239_p134/ 92397 1.2032 1.1998 1.1997 1.1997
data10_7TeV.00153030.physics_MinBias.merge.AOD.r1239_p134/ 1480567 20.1024 20.0891 20.0891 20.0889
data10_7TeV.00152994.physics_MinBias.merge.AOD.r1239_p134/ 381808 4.8135 4.8093 4.8093 4.8093
data10_7TeV.00152933.physics_MinBias.merge.AOD.r1239_p140/ 1474758 18.4077 18.3928 18.3928 18.3928
data10_7TeV.00152221.physics_MinBias.merge.AOD.r1239_p140/ 1442202 19.20353 19.18991 19.18998 19.19028
data10_7TeV.00152214.physics_MinBias.merge.AOD.r1239_p140/ 246662 2.96813 2.96598 2.96597 2.96595
data10_7TeV.00152166.physics_MinBias.merge.AOD.r1239_p140/ 514612 6.64534 6.64141 6.64145 6.64137

Total integral luminosity (L1_MBTS_1): 90.96 ub^-1
Total integral luminosity (L1_MBTS_2): 90.9601 ub^-1
Total integral luminosity (L1_MBTS_1_1): 73.465 ub^-1

Green DQ flags

Created on 2010-04-26. Using online integrated luminosity.

f r 152000+ and ptag data10_7TeV and lhc beamenergy 3450-3550 and lhc stablebeams true and dq lar g and dq tile g and dq pix g and dq sct g and dq mdt g and mag s and mag t

MyLBCollection_7TeV_green_stable.xml

Full dataset name Number of events IL (ub^-1) delivered IL (ub^-1) MBTS_1 IL (ub^-1) MBTS_2 IL (ub^-1) MBTS_1_1
data10_7TeV.00153200.physics_MinBias.merge.AOD.f249_m455   6.9455 6.9416 6.9416 0.069404
data10_7TeV.00153159.physics_MinBias.merge.AOD.f249_m455   10.136497 10.122319 10.122332 0.10116097
data10_7TeV.00153136.physics_MinBias.merge.AOD.f249_m455   0.608103 0.607781 0.607768 0.00608103

 
Total integral luminosity (L1_MBTS_1): 17.6717 ub^-1
Total integral luminosity (L1_MBTS_2): 17.6717 ub^-1
Total integral luminosity (L1_MBTS_1_1): 0.176646 ub^-1

MC

Full dataset name Number of events Cross section (mb) Integrated luminosity (ub^-1)
mc09_7TeV.105001.pythia_minbias.merge.AOD.e517_s787_s767_r1250_r1260/ 9990688 48.5 206.0
mc09_7TeV.105003.pythia_sdiff.merge.AOD.e514_s764_s767_r1204_r1210/ 4999479 13.7 364.9
mc09_7TeV.105004.pythia_ddiff.merge.AOD.e514_s764_s767_r1204_r1210/ 4998991 9.17 545.1

Please notice that signal and other background 7TeV MC samples are documented elsewhere

jobOptions


Common problems

Running in 15.6.1 and 15.6.4.1.

General problem #1:

when trying to run "checkTrigConfig.py -d" over this dataset the script fails to analyse some of the trigger chains with the following output:

Traceback (most recent call last):
  File "/afs/cern.ch/atlas/software/releases/15.6.4/AtlasTrigger/15.6.4/InstallArea/share/bin/checkTriggerConfig.py", line 41, in <module>
    trigconf.printFileSummary(options.chainsdetail)
  File "/afs/cern.ch/atlas/software/releases/15.6.4/AtlasTrigger/15.6.4/InstallArea/python/TrigConfigSvc/TriggerConfigARA.py", line 187, in printFileSummary
    self.printfnc(chaindetails)
  File "/afs/cern.ch/atlas/software/releases/15.6.4/AtlasTrigger/15.6.4/InstallArea/python/TrigConfigSvc/TriggerConfigARA.py", line 125, in printfnc
    fc = self.printFullChain(ef.chain_name())
  File "/afs/cern.ch/atlas/software/releases/15.6.4/AtlasTrigger/15.6.4/InstallArea/python/TrigConfigSvc/TriggerConfigARA.py", line 128, in printFullChain
    fc = self.getFullChain(name)
  File "/afs/cern.ch/atlas/software/releases/15.6.4/AtlasTrigger/15.6.4/InstallArea/python/TrigConfigSvc/TriggerConfigARA.py", line 252, in getFullChain
    raise RuntimeError, "L1 item %s as seed of %s not configured" % (l1name,l2name)
RuntimeError: L1 item L1_2FJ18, L1_2FJ3, L1_2J10, L1_2J10_win6, L1_2J15, L1_2J5, L1_3J10, L1_FJ18, L1_FJ18_EMPTY, L1_FJ3, L1_FJ3_BGRP1, L1_FJ3_EMPTY, L1_J10, L1_J10_EMPTY, L1_J10_win6, L1_J10_win6_EMPTY, L1_J15, L1_J15_EMPTY, L1_J15_LV, L1_J15_MV, L1_J15_NL, L1_J30, L1_J30_EMPTY, L1_J5, L1_J55, L1_J55_EMPTY, L1_J5_BGRP1, L1_J5_BGRP1_BPTX, L1_J5_EMPTY, L1_J75, L1_J75_EMPTY, L1_JE120, L1_JE120_EMPTY, L1_JE280, L1_JE280_EMPTY, L1_MU0_J5, L1_MU6_J5 as seed of L2_SeededStreamerL1CaloJet not configured

Solution(private):

cmt co -r TrigConfigSvc-00-03-40 Trigger/TrigConfiguration/TrigConfigSvc

General problem #2:

Something is wrong with:

HLT chain EF_cost_monitor
HLT chain EF_cost_monitor_rejAll

After fixing the bug with checkTrigConfig.py, running it one more time on the dataset gives us no info for these HLT chains, though checkTrigger.py does:

1022  LVL2   L2_cost_monitor                      0         0              0
1050  LVL2   L2_cost_monitor_rejAll            0         0              0
1022    EF   EF_cost_monitor                       0         0              0
1050    EF   EF_cost_monitor_rejAll             0         0              0

Solution:

An easy solution for this is not to print the full HLT chain info for all triggers in our Makers. This particular cost_monitor chain belongs to complicated calibration stream which we never are going to use. According to experts, there is no other way to ignore such errors even with the latest release available at that time.

Problem 15.6.1/1:

MagFieldAthenaSvc   ERROR Failed to initialise field from COOL
IOVSvcTool          ERROR Problems calling MagFieldAthenaSvc[0xf02f744]+25
IOVSvcTool          ERROR Problems preloading IOVRanges
IncidentSvc         ERROR Standard std::exception is caught 
IncidentSvc         ERROR IOVSvcTool::preLoadProxies

Solution(recipe found here):

cmt co -r BFieldData-01-06-08 MagneticField/BFieldData

-- KirillSkovpen - 07-Mar-2010

Topic attachments
I Attachment History Action Size Date Who Comment
XMLxml MyLBCollection_7TeV_green_stable.xml r1 manage 1.8 K 2010-05-05 - 12:54 KirillSkovpen Good Run List for 7TeV green DQ
XMLxml MyLBCollection_7TeV_yellow_stable.xml r1 manage 4.0 K 2010-05-05 - 12:55 KirillSkovpen Good Run List for 7TeV yellow+ DQ
XMLxml minbias_2TeV.xml r1 manage 2.4 K 2010-04-02 - 19:43 KirillSkovpen Good Run List for 2TeV
XMLxml minbias_900GeV.xml r1 manage 8.6 K 2010-04-02 - 19:43 KirillSkovpen Good Run List for 900GeV
Edit | Attach | Watch | Print version | History: r38 < r37 < r36 < r35 < r34 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r38 - 2010-06-09 - KirillSkovpen
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 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