This page lists some info and useful tips for the SYNTMaker ntuples for those that intend to use them for the SMP searches. These datasets supercedes the ones used for the ICHEP analysis, and holds much more data.

May reprocessed ESDs

The below sections lists some useful info about the SYNT datasets for data and MC from the May reprocessing.

Datasets for data

Runs with an integrated luminosity exceeding 1 inverse nanobarn are processed (MuonswBeam, L1Calo and debugrec_hltacc streams). A skimming was performed, requiring both

  • at least one offline muon (of any type) with $p_T > 10$ GeV
  • that the event passed at least one of the following triggers L1_J15, L1_J30, L1_MU6, L1_MU10, L1_XE15, EF_mu6_MSonly, EF_mu10_MSonly, EF_j40

The skimming efficiencies vary a little with the instantaneous luminosity for the two streams since triggers entering them have had different prescales over time, but typical values are <0.5% and <5% for L1Calo and MuonswBeam, respectively.

The top job options used to process the data is available on CERN AFS ~cohm/public/July2010/jobOptions/jobOptions_data10_7TeV_grid.py and the following little bash script will download them all from the grid (but make sure to write the log to a file and check it for errors!!!):

for DS in \
  group.phys-susy.data10_7TeV.periodC.physics_L1Calo.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100730/ \
  group.phys-susy.data10_7TeV.periodC.physics_MuonswBeam.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100730/ \
  group.phys-susy.data10_7TeV.periodC.debugrec_hltacc.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100730/ \
  group.phys-susy.data10_7TeV.periodD.physics_L1Calo.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100730/ \
  group.phys-susy.data10_7TeV.periodD.physics_MuonswBeam.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100730/ \
  group.phys-susy.data10_7TeV.periodD.debugrec_hltacc.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100730/ \
  group.phys-susy.data10_7TeV.periodE1.physics_JetTauEtmiss.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100814/ \
  group.phys-susy.data10_7TeV.periodE1.physics_Muons.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100814/ \
  group.phys-susy.data10_7TeV.periodE1.debugrec_hltacc.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100814/ \
  group.phys-susy.data10_7TeV.periodE2.physics_JetTauEtmiss.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100814/ \
  group.phys-susy.data10_7TeV.periodE2.physics_Muons.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100814/ \
  group.phys-susy.data10_7TeV.periodE2.debugrec_hltacc.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100814/ \
  group.phys-susy.data10_7TeV.periodE3.physics_JetTauEtmiss.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100814/ \
  group.phys-susy.data10_7TeV.periodE3.physics_Muons.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100814/ \
  group.phys-susy.data10_7TeV.periodE3.debugrec_hltacc.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100814/ \
  group.phys-susy.data10_7TeV.periodE4.physics_JetTauEtmiss.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100814/ \
  group.phys-susy.data10_7TeV.periodE4.physics_Muons.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100814/ \
  group.phys-susy.data10_7TeV.periodE4.debugrec_hltacc.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100814/ \
  group.phys-susy.data10_7TeV.periodE5.debugrec_hltacc.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100824/ \
  group.phys-susy.data10_7TeV.periodE5.physics_Muons.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100824/ \
  group.phys-susy.data10_7TeV.periodE5.physics_JetTauEtmiss.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100824/ \
  group.phys-susy.data10_7TeV.periodE6.physics_JetTauEtmiss.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100824/ \
  group.phys-susy.data10_7TeV.periodE6.debugrec_hltacc.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100824/ \
  group.phys-susy.data10_7TeV.periodE6.physics_Muons.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100824/ \
  group.phys-susy.data10_7TeV.periodE7.physics_JetTauEtmiss.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100824/ \
  group.phys-susy.data10_7TeV.periodE7.physics_Muons.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100824/ \
  group.phys-susy.data10_7TeV.periodE7.debugrec_hltacc.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100824/ \
group.phys-susy.data10_7TeV.periodF2.debugrec_hltacc.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100905/ \
group.phys-susy.data10_7TeV.periodF1.physics_JetTauEtmiss.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100905/ \
group.phys-susy.data10_7TeV.periodF2.physics_Muons.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100905/ \
group.phys-susy.data10_7TeV.periodF1.physics_Muons.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100905/ \
group.phys-susy.data10_7TeV.periodF1.debugrec_hltacc.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100905/ \
group.phys-susy.data10_7TeV.periodF2.physics_JetTauEtmiss.PhysCont.ESD.t0pro04_v01.SYNTr158_SMP_skimmed.100905/

do
   echo "Will now download $DS"
   dq2-get -f "*.root" $DS
done

In all of the run periods listed above, L1_J15 and L1_MU6 were unprescaled, thus they can be used for the analysis. For period E and on, L1_J15 has been prescaled, s we need to move to L1_J30 - UPDATE: late in period E L1_J30 was prescaled as well, so E5-E7 uses L1_J55 for the skimming instead, and, all of period E uses L1_MU10 rather than L1_MU6=. The muon part of the trigger menu recently went through some changes, and I think our best bet here is the =mu6_MSonly chain in the future (seeded by L1_MU0, so this should have a sharper turn-on than L1_MU6).

This script merges the ntuples into one file per run/stream (to improve performance of ROOT-level analysis!):

for d in /tmp/cohm/group.phys-susy.data10_7TeV.*ICHEP2010 # <= change the path to wherever you downloaded the SYNTs!
do
 echo $d
 inputFiles=""
 for f in ${d}/*AANT*root*
 do
   #echo "Processing $f file..."
   inputFiles="${inputFiles} $f"
 done
 #echo "hadd ${d%AANT*}.merged.root $inputFiles"
 hadd ${d%AANT*}.merged.root $inputFiles
done

(I thought differently at first, but hadd seems to work for datasets with up to 1000 files..! If you generalize the script to deal with even more files, feel free to edit the above..)

I have added a python script to the page that can be used to merge +1000 files at a time -- Morten

The GRL used only requires stable beam, DQ flags should be required at ROOT-level. The query used was:

find run 152166+ and events 1000k+ and lhc stablebeams true and lhc beamenergy 3400+

The total size of these datasets is approximately 26 GB.

Notes for me:

  • Job ids 1466-1505 were original jobs submitted to run over the data (possibly some of these were retries)
  • Job ids 1506-1526 were the original jobs submitted to run over the MC samples (signal and MC: 4 R-hadron, 7 QCD, 2 EW, 8 top)

Datasets for MC

  # Signal: two official gluino R-hadron samples + two of my May reprocessing-like low-mass gluino samples
  group.phys-susy.mc09_7TeV.106418.Pythia_R-Hadron1_gluino_300GeV.recon.ESD.e532_s810_s767_r1310.SYNTr158_SMP_skimmed \
  group.phys-susy.mc09_7TeV.106419.Pythia_R-Hadron2_gluino_600GeV.recon.ESD.e540_s815_s767_r1311.SYNTr158_SMP_skimmed \
  group.phys-susy.group10.phys-susy.mc09_7TeV.106415.Pythia_R-Hadron_gluino_100GeV.r1302-like.100614.reco.SYNTr158_SMP_skimmed \
  group.phys-susy.group10.phys-susy.mc09_7TeV.106416.Pythia_R-Hadron_gluino_200GeV.r1302-like.100614.reco.SYNTr158_SMP_skimmed \

  # BG: QCD, EW, ttbar, single top
  group.phys-susy.mc09_7TeV.105009.J0_pythia_jetjet.recon.ESD.e468_s766_s767_r1303.SYNTr158_SMP_skimmed \
  group.phys-susy.mc09_7TeV.105010.J1_pythia_jetjet.recon.ESD.e468_s766_s767_r1303.SYNTr158_SMP_skimmed \
  group.phys-susy.mc09_7TeV.105011.J2_pythia_jetjet.recon.ESD.e468_s766_s767_r1303.SYNTr158_SMP_skimmed \
  group.phys-susy.mc09_7TeV.105012.J3_pythia_jetjet.recon.ESD.e468_s766_s767_r1303.SYNTr158_SMP_skimmed \
  group.phys-susy.mc09_7TeV.105013.J4_pythia_jetjet.recon.ESD.e468_s766_s767_r1303.SYNTr158_SMP_skimmed \
  group.phys-susy.mc09_7TeV.105014.J5_pythia_jetjet.recon.ESD.e468_s766_s767_r1303.SYNTr158_SMP_skimmed \
  group.phys-susy.mc09_7TeV.105015.J6_pythia_jetjet.recon.ESD.e468_s766_s767_r1303.SYNTr158_SMP_skimmed \
  group.phys-susy.mc09_7TeV.106044.PythiaWmunu_no_filter.recon.ESD.e468_s765_s767_r1302.SYNTr158_SMP_skimmed \
  group.phys-susy.mc09_7TeV.106047.PythiaZmumu_no_filter.recon.ESD.e468_s765_s767_r1302.SYNTr158_SMP_skimmed \
  group.phys-susy.mc09_7TeV.105200.T1_McAtNlo_Jimmy.recon.ESD.e510_s765_s767_r1302.SYNTr158_SMP_skimmed \
  group.phys-susy.mc09_7TeV.108346.st_Wt_McAtNlo_Jimmy.recon.ESD.e508_s765_s767_r1302.SYNTr158_SMP_skimmed \
  group.phys-susy.mc09_7TeV.108343.st_schan_enu_McAtNlo_Jimmy.recon.ESD.e534_s765_s767_r1302.SYNTr158_SMP_skimmed \
  group.phys-susy.mc09_7TeV.108340.st_tchan_enu_McAtNlo_Jimmy.recon.ESD.e508_s765_s767_r1302.SYNTr158_SMP_skimmed \
  group.phys-susy.mc09_7TeV.108344.st_schan_munu_McAtNlo_Jimmy.recon.ESD.e534_s765_s767_r1302.SYNTr158_SMP_skimmed \
  group.phys-susy.mc09_7TeV.108341.st_tchan_munu_McAtNlo_Jimmy.recon.ESD.e508_s765_s767_r1302.SYNTr158_SMP_skimmed \
  group.phys-susy.mc09_7TeV.108345.st_schan_taunu_McAtNlo_Jimmy.recon.ESD.e534_s765_s767_r1302.SYNTr158_SMP_skimmed \
  group.phys-susy.mc09_7TeV.108342.st_tchan_taunu_McAtNlo_Jimmy.recon.ESD.e508_s765_s767_r1302.SYNTr158_SMP_skimmed \

The total size for the MC datasets is approximately 6 GB.

I have an excel (yes, it's true..) spreadsheet with the cross sections and expected number of events etc for all these processes - send me an email if you want it.

GRL for DQ requirements at ROOT level

Since the DQ flags can be changed, it's convenient to apply the DQ requirements at ROOT level such that we don't have to re-generate all the SYNTs. I made GRLs for periods C and D, and then merged them. The queries I used were based on what was used by the EtMiss-based SUSY analyses,

Period C: find runs 155228-156682 and ready and lhc stablebeams t and lhc beamenergy 3400+ and dq ATLGL,CP_MU_MMUIDCB,cp_jet_jetb,cp_jet_jetea,cp_jet_jetec,cp_met_metcalo,cp_met_metmuon,trele,bs,lumi,L1CTP,L1CAL,L1MUE,L1MUB LBSUMM#DetStatus-v03-pass1-analysis-2010C g / show lumi

Period D: ==

They're available as part of my analysis code in SVN. I also made a merged one to easily run over all runs with the same analysis code without any problems. It's a bit confusing to run iLumiCalc.exe on the merged GRL, it seems it doesn't add up the two constituent GRLs but processes them individually right after each other. Anyway, here's what I get for them (iLumiCalc.exe -t L1_J15 --lumitag=OflLumi-7TeV-002 -x SMP_search_GRL_DQ_periodD_100728.xml):

Period C: 7948.54 ub^-1 Period D: 287859 ub^-1 => Total: 295800 ub^-1 i.e. ~300 nb^-1

(Using L1_MU6 for the luminosity calculation gives very similar numbers - and remember that the uncertainty is still 11%...)

Outlook

In the future we should make the SYNTs from the DESDM_RPVLL stream, both for data and MC. I would really appreciate if some people who use these ntuples would volunteer to help out with the production and validation, since it's quite time consuming. Let me (Christian) know!

-- ChristianOhm - 27-Jul-2010

Topic attachments
I Attachment History Action Size Date Who Comment
Texttxt Powerhadd.py.txt r2 r1 manage 4.2 K 2010-08-12 - 09:01 UnknownUser Merger for more then 1k files at a time
Edit | Attach | Watch | Print version | History: r9 < r8 < r7 < r6 < r5 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r9 - 2020-08-19 - TWikiAdminUser
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox/SandboxArchive 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