-
Notifications
You must be signed in to change notification settings - Fork 1
Data
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.
The sum total luminosity (2015 + 2016) is 38.180 fb-1.
Luminosity mask: Cert_13TeV_16Dec2015ReReco_Collisions15_25ns_JSON.txt
Normtag: /afs/cern.ch/user/l/lumipro/public/Normtags/normtag_PHYSICS.json
- Total: 254231–260627, 2.258 fb-1
-
jetht15c: 254231–254914, 0.017 fb-1 -
jetht15d: 256630–260627, 2.241 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.922 fb-1
-
jetht16b: 273158–275376, 5.751 fb-1 -
jetht16c: 275657–276283, 2.573 fb-1 -
jetht16d: 276315–276811, 4.242 fb-1 -
jetht16e: 276831–277420, 4.025 fb-1 -
jetht16f: 277981–278808, 3.105 fb-1 -
jetht16g: 278820–280385, 7.576 fb-1 -
jetht16ha: 281613–284035, 8.435 fb-1 -
jetht16hb: 284036–284044, 0.216 fb-1
In order to use brilcalc, you need to install brilsw and add a line to your $PATH variable. The instructions for this procedure are available on the CMS BRIL Twiki.
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 configuration Twiki page (normtags, uncertainties)
- CMS BRIL Twiki page (installation, tool documentation)