-
Notifications
You must be signed in to change notification settings - Fork 1
Data
Tote Hughes edited this page Jun 15, 2017
·
18 revisions
I found the following (golden JSON) run ranges for each jetht subprocess by querying DAS (by hand). I started writing code to do this for me, but I got lazy. I used brilcalc to get the luminosities.
Luminosity mask: Cert_13TeV_16Dec2015ReReco_Collisions15_25ns_JSON.txt
- Total: 254231–260627, 2.183 fb-1
-
jetht15c: 254231–254914, 0.016 fb-1 -
jetht15d: 256630–260627, 2.166 fb-1
Luminosity mask: Cert_271036-284044_13TeV_23Sep2016ReReco_Collisions16_JSON.txt
Normtag: /afs/cern.ch/user/l/lumipro/public/Normtags/normtag_PHYSICS.json
- Total: 273158–284044, 35.545 fb-1
-
jetht16b: 273158–275376, 5.445 fb-1 -
jetht16c: 275657–276283, 2.396 fb-1 -
jetht16d: 276315–276811, 4.256 fb-1 -
jetht16e: 276831–277420, 4.054 fb-1 -
jetht16f: 277981–278808, 3.105 fb-1 -
jetht16g: 278820–280385, 7.544 fb-1 -
jetht16ha: 281613–284035, 8.529 fb-1 -
jetht16hb: 284036–284044, 0.217 fb-1
The full command to get the 2016 luminosity is
brilcalc lumi --normtag /afs/cern.ch/user/l/lumipro/public/Normtags/normtag_PHYSICS.json -i /afs/cern.ch/cms/CAF/CMSCOMM/COMM_DQM/certification/Collisions16/13TeV/ReReco/Final/Cert_271036-284044_13TeV_23Sep2016ReReco_Collisions16_JSON.txt -u /fb
- Official 2016 documentation was sent to the Luminosity HyperNews.
- CMS BRIL Twiki page