|
3 | 3 | ## Software setup |
4 | 4 |
|
5 | 5 | ``` |
6 | | -cmsrel CMSSW_10_6_8_patch1 |
7 | | -cd CMSSW_10_6_8_patch1/src |
| 6 | +cmsrel CMSSW_10_6_12 |
| 7 | +cd CMSSW_10_6_12/src |
8 | 8 | cmsenv |
9 | 9 |
|
| 10 | +for bash |
| 11 | +export CMSSW_GIT_REFERENCE=/cvmfs/cms.cern.ch/cmssw.git.daily |
| 12 | +
|
| 13 | +for tcsh |
10 | 14 | setenv CMSSW_GIT_REFERENCE /cvmfs/cms.cern.ch/cmssw.git.daily |
| 15 | +
|
11 | 16 | git cms-init |
12 | 17 |
|
13 | | -git clone -b 10_6_X_v1.05 --depth 1 https://github.com/cms-btv-pog/RecoBTag-PerformanceMeasurements.git RecoBTag/PerformanceMeasurements |
| 18 | +git clone -b 10_6_X_v2.01 --depth 1 https://github.com/cms-btv-pog/RecoBTag-PerformanceMeasurements.git RecoBTag/PerformanceMeasurements |
14 | 19 |
|
15 | 20 | scram b -j8 |
16 | 21 |
|
17 | 22 | ``` |
18 | 23 |
|
19 | 24 | The ntuplizer can be run and configured through ```RecoBTag/PerformanceMeasurements/test/runBTagAnalyzer_cfg.py```. |
20 | 25 |
|
21 | | -NOTE1: due to the structure of the preliminary JECs, there are 6 different "defaults" sets; |
| 26 | +NOTE1: due to the structure of the preliminary JECs, there are 5 different "defaults" sets; |
22 | 27 |
|
23 | | -> **_MC_**: ```defaults=2017_UltraLegacy```<br/> |
24 | | -> **_Run2017B_**: ```defaults=2017_UltraLegacy_DataRunB```<br/> |
25 | | -> **_Run2017C_**: ```defaults=2017_UltraLegacy_DataRunC```<br/> |
26 | | -> **_Run2017D_**: ```defaults=2017_UltraLegacy_DataRunD```<br/> |
27 | | -> **_Run2017E_**: ```defaults=2017_UltraLegacy_DataRunE```<br/> |
28 | | -> **_Run2017F_**: ```defaults=2017_UltraLegacy_DataRunF``` |
| 28 | +> **_MC_**: ```defaults=2018_UltraLegacy```<br/> |
| 29 | +> **_Run2018A_**: ```defaults=2018_UltraLegacy_DataRunA```<br/> |
| 30 | +> **_Run2018B_**: ```defaults=2018_UltraLegacy_DataRunB```<br/> |
| 31 | +> **_Run2018C_**: ```defaults=2018_UltraLegacy_DataRunC```<br/> |
| 32 | +> **_Run2018D_**: ```defaults=2018_UltraLegacy_DataRunD``` |
29 | 33 |
|
30 | 34 | This means in your crab configuration file, you will have to check which file you are running on, and pick the correct default set accordingly. As an example, one might do something like: |
31 | 35 |
|
32 | 36 | ``` |
33 | 37 | ... |
34 | | -config.Data.inputDataset = /BTagMu/Run2017D-09Aug2019_UL2017-v1/MINIAOD |
35 | | -if "Run2017B" in config.Data.inputDataset: |
36 | | - config.JobType.pyCfgParams = [defaults=2017_UltraLegacy_DataRunB ,...] |
37 | | -elif "Run2017C" in config.Data.inputDataset: |
38 | | - config.JobType.pyCfgParams = [defaults=2017_UltraLegacy_DataRunC ,...] |
39 | | -elif "Run2017D" in config.Data.inputDataset: |
40 | | - config.JobType.pyCfgParams = [defaults=2017_UltraLegacy_DataRunD ,...] |
41 | | -elif "Run2017E" in config.Data.inputDataset: |
42 | | - config.JobType.pyCfgParams = [defaults=2017_UltraLegacy_DataRunE ,...] |
43 | | -elif "Run2017F" in config.Data.inputDataset: |
44 | | - config.JobType.pyCfgParams = [defaults=2017_UltraLegacy_DataRunF ,...] |
| 38 | +config.Data.inputDataset = /BTagMu/Run2018A-12Nov2019_UL2018-v1/MINIAOD |
| 39 | +if "Run2018A" in config.Data.inputDataset: |
| 40 | + config.JobType.pyCfgParams = [defaults=2018_UltraLegacy_DataRunA ,...] |
| 41 | +elif "Run2018B" in config.Data.inputDataset: |
| 42 | + config.JobType.pyCfgParams = [defaults=2018_UltraLegacy_DataRunB ,...] |
| 43 | +elif "Run2018C" in config.Data.inputDataset: |
| 44 | + config.JobType.pyCfgParams = [defaults=2018_UltraLegacy_DataRunC ,...] |
| 45 | +elif "Run2018D" in config.Data.inputDataset: |
| 46 | + config.JobType.pyCfgParams = [defaults=2018_UltraLegacy_DataRunD ,...] |
45 | 47 | else: |
46 | | - config.JobType.pyCfgParams = [defaults=2017_UltraLegacy ,...] |
| 48 | + config.JobType.pyCfgParams = [defaults=2018_UltraLegacy ,...] |
47 | 49 | ... |
48 | 50 | ``` |
49 | 51 |
|
|
0 commit comments