Global Tags for Conditions Data


Contents:

<nop>Introduction

This page is intended for the detailed recording of conditions used in the CMS data processing workflows, and description of some key tools. If you're looking for which global tag should be used to analyse a specific dataset, please refer to the analysis recipe session.

Conditions data for consumption in CMSSW are defined in the Offline Conditions Database, which is read in CMSSW applications via Frontier caching servers.

The set of database tags which together define the offline conditions data are collected together in a Global Tag, which is itself stored in the database. This removes the need for the list of database tags to be defined in separate cffs and therefore decouples the conditions database from the CMSSW release; different Global Tags can be used with a given CMSSW release, with the tag itself specified in the cfg file.

The following file should be included in the cfg for any CMSSW application for which needs to read conditions data:

It is then necessary to specify which global tag is to be used, as follows:

process.GlobalTag.globaltag = 'GlobalTagName'

For example, for a CMSSW job to process simulated dataset produced in the RunIISpring16DR8 80X campaign, you need to :

from Configuration.AlCa.GlobalTag import GlobalTag
process.GlobalTag.globaltag = '80X_mcRun2_asymptotic_2016_miniAODv2_v1'

Note that the global tag to be used should always be explicitly specified.

Browsing the Global Tag content

There are 2 main ways to access the content of a Global Tag:

  • web interface for browsing and monitoring the changes to a Global Tag is available:
  • command line tool: the following script can also be run to examine the contents of a global tag
       cmsenv
       conddb list TAGNAME

How to find out which conditions were used in an existing reconstructed dataset

Tier0 datasets:

You can check the T0Mon page for the runs currently processed at Tier0: T0Mon clicking on the run # will show you the Global-Tag in use.

You can also refer to the table Global Tags for Data Taking in this page.

Other datasets

You can query DBS with:

dbs search --query='find dataset.tag where dataset=/MyFavorite/Dataset/RECO'

For Monte Carlo production, and for skims and reprocessed data, the name of the global tag for conditions is included in the DBS dataset name. For example:

/Zmumu/CSA08_CSA08_S156_v1/GEN-SIM-RECO

In this case, the global tag used is CSA08_S156 which can be found in the table above.

Alternatively, you can search for the global tag in the cfg.py file, e.g.:

process.GlobalTag.globaltag = "80X_mcRun2_asymptotic_2016_miniAODv2_v1"

Analysis recipes

The recommendation of which global tag (together with other ingredients) should be used to analyze a specific dataset is best found in the analysis recipe page maintained by the PdmV team.

Customization of Global Tags

You may want to use an existing global tag with a modification to one or more of the conditions defined within it. For example, when running muon alignment, it is desirable to use the very latest tracker alignment conditions, which may not yet be in a published global tag, or to use a particular misalignment scenario which is not included in an existing MC global tag.

Note that in the following the connect string is untracked so this is only suitable for tests in which full provenance tracking is not important. See the alternative method using es_prefer below for a fully tracked configuration.

The following example shows a configuration in which the tag Early900GeVCollision_7p4cm_STARTUP_mc, read from the production database, is used for the beamspot, replacing whatever beamspot is specified in the global tag:

process.GlobalTag.toGet = cms.VPSet(
  cms.PSet(record = cms.string("BeamSpotObjectsRcd"),
           tag = cms.string("Early900GeVCollision_7p4cm_STARTUP_mc"),
           connect = cms.string("frontier://FrontierProd/CMS_CONDITIONS")
          )
)

The following example shows a configuration in which the tags for <nop>TrackerAlignmentRcd and <nop>TrackerAlignmentErrorRcd are taken from an sqlite file, in place of whatever tags are specified for those records in the global tag:

process.GlobalTag.toGet = cms.VPSet(
  cms.PSet(record = cms.string("TrackerAlignmentRcd"),
           tag = cms.string("Alignments"),
           connect = cms.string("sqlite_file:myAlignments.db")
          ),
  cms.PSet(record = cms.string("TrackerAlignmentErrorRcd"),
           tag = cms.string("AlignmentErrors"),
           connect = cms.string("sqlite_file:myAlignments.db")
          )
)

The following example shows a configuration for which a 100pb scenario for tracker mis-alignment is read from the production database, in place of whatever tags are specified for those records in the global tag:

process.GlobalTag.toGet = cms.VPSet(
  cms.PSet(record = cms.string("TrackerAlignmentRcd"),
           tag = cms.string("Tracker100pbScenario310_mc"),
           connect = cms.string("frontier://FrontierProd/CMS_CONDITIONS)
          ),
  cms.PSet(record = cms.string("TrackerAlignmentErrorRcd"),
           tag = cms.string("Tracker100pbScenarioErrors310_mc"),
           connect = cms.string("frontier://FrontierProd/CMS_CONDITIONS")
          )
)

The set of mis-alignment scenario tags for each release can be found here.


#EsPrefer

Alternative method using es_prefer

An alternative method for global tag customization is to use es_prefer: In this case, an es_source is added to the cfg to define the alternative conditions to be used, followed by an es_prefer statement to indicate that this es_source should take precedence over any other source for that condition object (in particular, the global tag). The advantage of this method is that all parameters are tracked, whereas the connect string is untracked in the above approach. The equivalent of the second example above would be:

from CondCore.CondDB.CondDB_cfi import *
process.CondDB.connect = 'sqlite_file:myAlignments.db"'
process.trackerAlignment = cms.ESSource("PoolDBESSource",CondDB,
                                        toGet = cms.VPSet(cms.PSet(record = cms.string("TrackerAlignmentRcd"),
                                                                   tag = cms.string("Alignments")),
                                                          cms.PSet(record = cms.string("TrackerAlignmentErrorRcd"),
                                                                   tag = cms.string("AlignmentErrors"))
                                                          )
                                        )
process.es_prefer_trackerAlignment = cms.ESPrefer("PoolDBESSource","trackerAlignment")

Special Instructions for using es_prefer with 2XY Releases


More... Close

For 21X and 22X releases there is an es_prefer on the global tag FrontierConditions_GlobalTag_cff.py. For 22X releases it is necessary to use:

process.load("Configuration.StandardSequences.FrontierConditions_CMS.GlobalTag_noesprefer_cff")

in your cfg.py in place of:

process.load("Configuration.StandardSequences.FrontierConditions_CMS.GlobalTag_cff")

For 21X releases, it is necessary to check out Configuration/StandardSequences and edit <nop>FrontierConditions_CMS.GlobalTag_cff to remove the es_prefer.

For both 21X and 22X, depending on the global tag used, you may additionally need to remove lines from <nop>FrontierConditions_CMS.GlobalTag_noesprefer_cff.py (22X) or <nop>FrontierConditions_CMS.GlobalTag_cff.py (21X) to avoid <nop>EventSetup conflicts due to a condition being provided by both the global tag and a fake source. e.g. if you see:

---- EventSetupConflict BEGIN
two EventSetup Sources want to deliver type="DTMtime" label=""
from record DTMtimeRcd. The two providers are
1) type="DTFakeVDriftESProducer" label=""
2) type="PoolDBESSource" label="CMS.GlobalTag"
Please either
  remove one of these Sources
  or find a way of configuring one of them so it does not deliver this data
  or use an es_prefer statement in the configuration to choose one.
---- EventSetupConflict END

it means <nop>DT VDrift conditions are included in the global tag you are using, so you need to remove the fake source from the cff by (in this case) removing the line:

from CalibMuon.DTCalibration.DTFakeVDriftESProducer_cfi import *

from <nop>FrontierConditions_CMS.GlobalTag_noesprefer_cff.py (22X) or <nop>FrontierConditions_CMS.GlobalTag_cff.py (21X). If you change a cff.py file, remember to do scram b python.

Finally, make sure you do not have anywhere in your cfg:

process.prefer("CMS.GlobalTag")


Global Tags keys for RelVal workflows

See GT for release cycle pag

Global Tags used in official data reprocessing / MC productions

Global tag for 2018 MC production. The campaign is RunIISpring18MiniAOD
GT name Validity Comments
100X_upgrade2018_realistic_v10 GT for 10.1.X (X>=2) This campaign has been used to submit miniAOD requests for 2018-POG/DPG production in CMSSW_10_0_2
Global tag for early 2018 MC production. The campaign is RunIISummer18pLHE
GT name Validity Comments
101X_upgrade2018_realistic_v7 GT for 10.1.X (X>=5) GT to be used for the MC production. It contain condition from early 2018 realistic scenario

Global tag for ppRef 5 TeV MC production. The campaign is RunIIpp5Spring18GS and RunIIpp5Spring18wmLHEGS
GT name Validity Comments
94X_mc2017_realistic_forppRef5TeV GT for 94X (X>=0) GT to be used for the ppRef MC production. It contain special BS, ECAL conditions and L1T menu, everything else is same as regular pp

Global Tags for 2017 Nov re-reco (17Nov) for EOY ReReco 2017 reprocessing of 2017B-F (CMSSW_9_4_5)
GT name Validity Comments
94X_dataRun2_ReReco_EOY17_v6 CMSSW_9_4_5_cand1

Production of MiniAODv2 from 94x 2017 data AOD input datasets from EOYReReco2017 (17Nov2017 rereco). The reprocessing for 2017B-F has been injected using the candidate release (under validation) CMSSW_9_4_5_cand1. After validation was succesfull, It was cloned into production release CMSSW_9_4_5.

Global Tags for 2017 Nov re-reco (17Nov) for EOY ReReco 2017 reprocessing of 2017B-F (CMSSW_9_4_0)
GT name Validity Comments
94X_dataRun2_ReReco_EOY17_v2 GT for 94X (X>=0) Validation Campaigns until 2017E This re-reco is meant for the Physics analyses for Winter conferences.

Global Tags for RunIIFall17DRPremix MC production with premixing for Physics Studies with 2017 rereco data
Global Tags for RunIIFall17DRStdmix MC production with standard mixing for Physics Studies with 2017 rereco data
GT name Validity Comments
94X_mc2017_realistic_v12 GT for 9_4_4 or higher Analysis level GTs with updates of Jet probability calibration and Jet energy corrections on the top of 94X_mc2017_realistic_v10 GT
94X_mc2017_realistic_v10 GT for 9_4_0 or higher final GT containing the latest MC conditions for 2017

Global Tags for PhaseIITDRFall17DR MC production for HGCal TDR
GT name Validity Comments
93X_upgrade2023_realistic_v3 GT for 9_3_2 or higher As compared to 93X_upgrade2023_realistic_v2 , an update of Jet Energy Corrections requested here https://hypernews.cern.ch/HyperNews/CMS/get/calibrations/3422.html
93X_upgrade2023_realistic_v2 GT for 9_3_0 or higher realistic conditions for Phase-II upgrade for the HGCal TDR.

Global Tags for PdmVMCcampaignRunIISummer17DRPremix MC Production (V1) for 2017 first data-MC studies with Premixing
GT name Validity Comments
92X_upgrade2017_realistic_v7 GT for 9_2_7 or higher realistic conditions for Phase-I Pixel and Plan1 HCAL along with other sub-detectors.

Global Tags for PdmVMCcampaignRunIISummer17DRStdmix MC Production (V1) for 2017 first data-MC studies with Standard Mixing
GT name Validity Comments
92X_upgrade2017_realistic_v7 GT for 9_2_7 or higher realistic conditions for Phase-I Pixel and Plan1 HCAL along with other sub-detectors.

Global tags for PdmVMCcampaignRunIISummer17wmLHEGS MC Production (V1) for 2017.
GT name Validity Comments
92X_upgrade2017_realistic_v7 GT for 9_2_7 or higher realistic conditions for Phase-I Pixel and Plan1 HCAL along with other sub-detectors.

Global Tags for PdmVMCcampaignPhaseISpring17GS MC Production for for 2017 DPG/POG studies and PF calibration
GT name Validity Comments
90X_upgrade2017_realistic_v20 GT for 9_0_0 PhaseI CMS, with plan1 HE and realistic conditions
90X_upgrade2017_realistic_ExtendedZeroMaterial_EGM_PFCalib GT for 9_0_0 PhaseI CMS, with plan1 HE and realistic conditions - same as 90X_upgrade2017_realistic_v20 adding no-tracker-material, for egamma
  GT for 9_0_0 PhaseI CMS, with plan1 HE and realistic conditions - same as 90X_upgrade2017_realistic_v20 perfect knowledge of ECAL IC's, for egamma

Global Tags for PdmVMCcampaignPhaseIFall16DR MC Production for for early 2017 TSG studies with plan0 phaseI detector
GT name Validity Comments
90X_upgrade2017_realistic_v6_C1 GT for 8_3_0 PhaseI Detector, with plan0 HE

Global Tags for PdmVMCcampaignRunIISummer16DR80Premix MC Production for Moriond 17 (80X)
GT name Validity Comments
80X_mcRun2_asymptotic_2016_TrancheIV_v8 GT for 80X (X>=20) as 80X_mcRun2_asymptotic_2016_TrancheIV_v6 with the following change:
new JEC for reMiniAod 02Feb2017 campaign (based on Summer16 MC)
80X_mcRun2_asymptotic_2016_TrancheIV_v7 GT for 80X (X>=20) as 80X_mcRun2_asymptotic_2016_TrancheIV_v6 with the following change:
addded e/gamma regressions labels as in PR #16968; egamma regressions not to be used as reported here
80X_mcRun2_asymptotic_2016_TrancheIV_v6 GT for 80X (X>=20) as 80X_mcRun2_asymptotic_2016_miniAODv2_v1 with the following change:
- L1T menu (as per HLT post MD2)
- Jet Energy Corrections (version Summer16)
- realistic CSC bad chambers
- Fixed ECAL TPG conditions for 2016 run simulation
- version of MC JEC to version Summer16_25nsV5
- update b-tagging HIP mitigation in jet probability calibration
- reverted RPC noise tag to 2012 values fixed centering in Pixel Barrel of Tracker misaligned scenario
- Beamspot according to new misalignment scenario
- Strip DQM AlCaRecoTriggerBit
- AlCaRecoTriggerBit for EcalTrg AlCaReco
- Tracker Alignment asymptotic sceanrio removing z-shrinkage effect
- EcalChannelStatus (as in Aug 2016)
- RPC noise and efficiency
- SiPixel dynamic inefficiency for 2016 data (high PU)
- Pixel channel status (as in Aug 2016)
- Strip channel status (as in Aug 2016)

Global Tags for 2017 Early re-reco (12Sep) for 12Sep2017 reprocessing of 2017B-C upto Run 300676 (CMSSW_9_2_11)
GT name Validity Comments
92X_dataRun2_2017Repro_v4 GT for 92X (X>=11) Validation Campaigns This re-reco is meant for the data-MC studies with V1 MC. This does not aim for the best conditions but for consistent set of conditions as we had quite inhomogeneous updates in Pixel commissioning period.

Global Tags for 2016 legacy data re-reco for YYApr2017 reprocessing of 2016A-H (CMSSW_8_0_29)

GT name Validity Comments
80X_dataRun2_2016LegacyRepro_v4 GT for 80X (X>=29) as 80X_dataRun2_2016LegacyRepro_v3 with: fix of ECAL ICs to fix the high-eta EM deposits Sign-off talk
80X_dataRun2_2016LegacyRepro_v3 GT for 80X (X>=27) as 80X_dataRun2_2016SeptRepro_v4 with:
- Change in SiPixel Templates, GenError and Lorentz Angle. Sign-off talk
- Change in SiStrip Gain2 calibration, mostly adjustment of IOVs and a new IOV added. Announced here and signed-off talk
- Tracker alignment, APEs and surface deformations updated. signed-off talk
- Update of BeamSpot corresponding to the changes in tracker alignment package. signed-off talk
- Update of muon alignment and APEs. announcement
- Update of DtTrig. Announced here
- Update of whole ECAL package. signed-off talk. Changes includes update of ECAL pedestals, ADCtoGeV, ECAL alpha values, pulse shapes, time calibrations, channel status of both ECAL and ES, ECAL Laser corrections, ECAL and ES Channel quality, ECAL intercalibration and ES intercalibration.
- Update of HCAL gains and response corrections. announced here
- Update of global alignment (GPR)
- Update of L1 caloParam tag and addition of L1 muon param tags. announced here

Global Tags for 2016 data re-reco for 23Sept16 reprocessing of 2016A-G (80X)

GT name Validity Comments
80X_dataRun2_2016SeptRepro_v7 GT for 80X (X>24) as 80X_dataRun2_2016SeptRepro_v5 with:
- new jet energy corrections as announced here for 02Feb2017 reminiAOD (based on Summer16 MC)
80X_dataRun2_2016SeptRepro_v6 GT for 80X (X>20) as 80X_dataRun2_2016SeptRepro_v5 with:
- new labels for e/gamma regressions as in PR #16968 the PR was closed, waiting for update
80X_dataRun2_2016SeptRepro_v5 GT for 80X (X>20) as 80X_dataRun2_2016SeptRepro_v4 with:
- added record for L1TGlobalPrescalesVetoesRcd (L1T global prescales)
80X_dataRun2_2016SeptRepro_v4 GT for 80X (X>20) as 80X_dataRun2_Prompt_v11 with:
- updated beamspot to fix IOV assignment of 2016B-v2
- TrackerSurfaceDeformationRcd fixed to be consistent with TK alignment
- tag for Hcal Response corrections containing the history previous to 2016
- updated AlCaRecoTriggerBits to allow usage of EcalAlCaTrg in all 2016
- ECAL transparency and ADC2GEV
- CSCAlignmentErrorExtended_6x6_offline
- DTAlignmentErrorExtended_6x6_offline
- Pixel templates, Generic errors, LA
- Tracker Alignment, Surface Deformations, APE
- LS-based BeamSpot
- HCAL Response corrections
- ES channel status
- DT TTrig
- IOVs of the SiStrip particle gains
- ECAL channel status
- HCAL channel status
- SiStrip bad channel map
- TrackProbabilityCalibration
- JetEnergy corrections and resolutions

Global Tags for 2016 data re-reco for ICHEP 2016 (80X)

GT name Validity Comments
80X_dataRun2_ICHEP16_repro_v0 GT for 80X (X>10) as 80X_dataRun2_Prompt_v9 with:
- updated pixel templates and generic errors from 2016B
- updated module level tracker alignment and APE from 2016B
- updated EB ES and EE alignment from 2016B
- updated DT CSS and global position record alignments from 2016B
- amended HCAL quality from 2016B
- amended HCAL gains from 2016B
- updated ECAL time calibration and pulse shape from 2016B
- updated ECAL ADC2GeV from 2016B
- refit lumi-based beamspot

Special Global Tags for Run2 MC production with realistic beamspot (80X)

3.8T beamspot

GT name Validity Comments
80X_mcRun2_asymptotic_RealisticBS_25ns_13TeV2016_v1_mc GT for 80X (X>10) Digi-Reco to be run on 71X GEN-SIM-RAW as 80X_mcRun2_asymptotic_v14 with:
- updated luminous region parameters as measured in data after pixel barycenter translation to simulate illumination in 3.8T 2016 data (i.e BeamSpotObjects _Realistic25ns_13TeV2016Collisions_v1_mc)

Global Tags for RunIISpring16DR80 MC Production(80X)
GT name Validity Comments
80X_mcRun2_asymptotic_2016_v3 GT for 80X (X>=3) as 80X_mcRun2_asymptotic_v6 with the following change:
- SiStrip updated channel map (all FEDs are unpacked)
- Pixel dynamic inefficiency, updated including measurement with 2015 data
- ECAL selective readout update as in 2016 DAQ
- ECAL noise and transparency loss (extrapolated from measurements in 2015) for 15/fb
- ES updated noise and pedestals (rom measurements in 2015)
- ES channel map, updated to start of 2016
- muon APE > 0 (derived comparing Ideal with Asymptotic alignment scenarios)
- HCAL updated channel map (removed 2 channels from re-worked HF PMT box)
80X_mcRun2_asymptotic_2016_miniAODv2 GT for 80X (X>=4) as 80X_mcRun2_asymptotic_2016_v3 with the following change:
- JECs for Spring15 MC miniAODv2 production
80X_mcRun2_asymptotic_2016_miniAODv2_v0 GT for 80X (X>=11) as 80X_mcRun2_asymptotic_2016_miniAODv2 with the following change:
updated Jet Energy corrections for HLT
- introducing uGT menu for Stage-II L1T
80X_mcRun2_asymptotic_2016_miniAODv2_v1 GT for 80X (X>=11) as 80X_mcRun2_asymptotic_2016_miniAODv2_v0 with the following change:
- updated offline JEC and JER
- updated uGT menu for Stage-II L1T

Special Global Tags for preparation of CosmicSpring16DR80 Cosmics Run2 MC production in 80X
GT name Validity Comments
80X_mcRun2cosmics_asymptotic_deco_v0 GT for 80X (X>=3) as 80X_mcRun2_asymptotic_2016_v3 with the following changes:
- top-bottom L1T trigger configuration for DT,RCP and CSC.
80X_mcRun2cosmics_asymptotic_peak_v0 GT for 80X (X>=3) as 80X_mcRun2_asymptotic_2016_v3 with the following changes:
- top-bottom L1T trigger configuration for DT,RCP and CSC.
- SiStrip noise for peak mode.

Special Global Tags for preparation of Run2 MC production in 80X
GT name Validity Comments
80X_mcRun2_asymptotic_v5_2016PixDynIneff GT for 80X (X>=0) as 80X_mcRun2_asymptotic_v5 with the following change:
- updated pixel dynamic inefficiency for 2016 digi-reco, based on 2015 data.
80X_mcRun2_asymptotic_2016EcalTune_15fb_v0 GT for 80X (X<=0) as 80X_mcRun2_asymptotic_v1 with the following changes:
- tuning of the thresholds of the zero-suppression (ZS tag) and the selective-readout (TPG tag) to safely run with a PU up to ~ 40-50 - end of 2015
- 15/fb integrated dose equivalent Ecal noise
80X_mcRun2_asymptotic_2016EcalTune_30fb_v0 GT for 80X (X<=0) as 80X_mcRun2_asymptotic_v1 with the following changes:
- tuning of the thresholds of the zero-suppression (ZS tag) and the selective-readout (TPG tag) to safely run with a PU up to ~ 40-50 - end of 2015
- 30/fb integrated dose equivalent Ecal noise

Special Global Tags for Run2 MC production with all channels working (80X)
GT name Validity Comments
80X_mcRun2_asymptotic_2016_AllChannelsGood_v0 GT for 80X (X>4) Digi-Reco to be run on 71X GEN-SIM-RAW as 80X_mcRun2_asymptotic_2016_v3 with:
- all channels working

Global Tags for RunIIFall15DR76 MC campaign (76X)
GT name Validity Comments
76X_mcRun2_asymptotic_v12 GT for 76X (X>=3) RunIIFall15DR76 campaign as 76X_dataRun2_v11 with the following change:
- latest version of JEC for offline (Summer15_25nsV6).
76X_mcRun2_asymptotic_RunIIFall15DR76_v1 GT for 76X (X>=3) RunIIFall15DR76 campaign as 76X_mcRun2_asymptotic_RunIIFall15DR76_v0 with: - updated JEC, adding L2L3 residuals corrections and uncertainties

Global Tags for 2015 EOY Re-reco (76X)
GT name Validity Comments
76X_dataRun2_v15 GT for 76X (X>=3) 2015 End of the Yerar data-reprocessing as 76X_dataRun2_v14 with the following change:
- updated Ecal ADC to GeV calibration with the correct value for B on.
76X_dataRun2_16Dec2015_v0 GT for 76X (X>=3) 2015 End of the Yerar data-reprocessing as 76X_dataRun2_v15 with the following change: - update of Fall15 V1 JEC, adding L2L3 residuals corrections and uncertainties.

Special Global Tags for Run2 MC production with all channels working (74X)
GT name Validity Comments
74X_mcRun2_asymptotic_AllChannelsGood_v0 GT for 74X (X>1) Digi-Reco to be run on 71X GEN-SIM-RAW as MCRUN2_74_V9 with:
- all channels working

Special Global Tags for Run2 MC production with realistic beamspot (74X)

3.8T beamspot

GT name Validity Comments
74X_mcRun2_asymptotic_realisticBS_v1 GT for 74X (X>6) Digi-Reco to be run on 71X GEN-SIM-RAW as MCRUN2_74_V9 with:
- updated luminous region parameters as measured in data after pixel barycenter translation to simulate illumination in 3.8T data with asymptotic alignment:
(i.e BeamSpotObjects _Realistic50ns_13TeVCollisions_Asymptotic_v0_mc)
- added Negative energy filter
- adding 74X DR L1 menu for 25ns
- changed the pixel dead channels map to v27
741_p1_mcRun2_Realistic_50ns_v0 GT for 741_patch1 Digi-Reco to be run on 71X GEN-SIM-RAW as MCRUN2_74_V8 with:
- updated luminous region parameters as measured in data after pixel barycenter translation to simulate illumination in 3.8T data with startup alignment: (i.e. BeamSpotObjects _Realistic50ns_13TeVCollisions_Startup_v0_mc )
- changed the pixel dead channels map to v27

0T beamspot

74X_mcRun2_asymptotic_realisticBS_v0 GT for 74X Digi-Reco to be run on 71X GEN-SIM-RAW as MCRUN2_74_V9 with:
- updated luminous region parameters as measured in data after pixel barycenter translation to simulate illumination in 0T data
(i.e. BeamSpotObjects _Realistic50ns_13TeVCollisions_v5_mc)
- added Negative energy filter
- adding 74X DR L1 menu for 25ns
74X_mcRun2_startup_realisticBS_v0 GT for 74X Digi-Reco to be run on 71X GEN-SIM-RAW as MCRUN2_74_V8 with: :
- updated luminous region parameters as measured in data after pixel barycenter translation simulate illumination in 0T data
(i.e. BeamSpotObjects _Realistic50ns_13TeVCollisions_v5_mc)
- added Negative energy filter
- adding 74X DR L1 menu for 50ns
74X_mcRun2_startup_realistic50ns_v0 GT for 74X Digi-Reco to be run on 71X GEN-SIM-RAW as MCRUN2_74_V8 with:
- updated Tracker Alignment Startup scenario
- updated SiPixel Quality map (v27)
- updated beamspot to simulate pixel barrel illumination in run2015B B=0T data
(i.e. BeamSpotObjects _Realistic50ns_13TeVCollisions_v4_mc), re-fitting with realistic tracker conditions
- added negative energy filter
- adding 74X DR L1 menu for 50ns

Global Tags for Run2 MC Production(74X)
GT name Validity Comments
MCRUN2_74_V9 GT for 74X Digi-Reco to be run on 71X GEN-SIM-RAW 25ns, asymptotic scenario as in RelValGT
MCRUN2_74_V9A GT for 74X Digi-Reco to be run on 71X GEN-SIM-RAW 50ns, asymptotic scenario as in RelValGT
MCRUN2_74_V8 GT for 74X Digi-Reco to be run on 71X GEN-SIM-RAW 50ns, startup scenario as in RelValGT

Global Tags for Data Taking

Global Tags for 2018 data taking

HLT reconstruction Global tags
TAGNAME Validity Description Comments
101X_dataRun2_HLT_v7 for CMSSW_10_1_1 onwards Collisions 2018 first HLT GT for collisions
100X_dataRun2_HLT_v2 for CMSSW_10_0_3 onwards CRUZET 2018 update of 0T templates for SiPixels. Diff
100X_dataRun2_HLT_v1 for CMSSW_10_0_0 onwards MWGRs 2018 first HLT GT for 2018

Express reconstruction Global tags
101X_dataRun2_Express_v8 for CMSSW_10_1_7 onwards Collisions 2018 having a technical update of ECAL timing calibration tag
101X_dataRun2_Express_v7 for CMSSW_10_1_1 onwards Collisions 2018 First Express GT for collisions
100X_dataRun2_Express_v2 for CMSSW_10_0_3 onwards CRUZET 2018 update of 0T templates for SiPixels. Diff
100X_dataRun2_Express_v1 for CMSSW_10_0_0 onwards MWGRs 2018 first Express GT for 2018

Prompt Reconstruction Global Tags
101X_dataRun2_Prompt_v11 for CMSSW_10_1_7 onwards Collisions 2018 Splitting of ECAL timing calibration tag between HLT/Express and Prompt
101X_dataRun2_Prompt_v10 for CMSSW_10_1_6 onwards Collisions 2018 Splitting of ECAL pulse shape tag between HLT/Express and Prompt
101X_dataRun2_Prompt_v9 for CMSSW_10_1_1 onwards Collisions 2018 Stable Prompt GT for collisions 2018
100X_dataRun2_Prompt_v2 for CMSSW_10_0_3 onwards CRUZET 2018 update of 0T templates for SiPixels. Diff
100X_dataRun2_Prompt_v1 for CMSSW_10_0_0 onwards MWGRs 2018 first Prompt GT for 2018

Global Tags for 2017 data taking

HLT reconstruction Global Tags

TAGNAME Validity Description Comments
92X_dataRun2_HLT_v7 for CMSSW_9_2_8 onwards collisions with v2.2 menu 92X_dataRun2_HLT_v5 with
- change the tag for PF calibrations for HLT
- change the tag for PF calibrations at HLT
92X_dataRun2_HLT_v5 for CMSSW_9_2_6 onwards first collisions 92X_dataRun2_HLT_v4 with
- includes CTPPS tags and remove offline PF corrections tags
- includes CTPPS tags and remove offline PF corrections tags which are not used in HLT and DQM
92X_dataRun2_HLT_v4 for CMSSW_9_2_0 onwards first collisions 92X_dataRun2_HLT_v2 with
- updated JEC tags to fix synchronisation and allow to append IOVs
- updated PFCalibration tag to fix synchronisation and allow to append IOVs
90X_dataRun2_HLT_v2 for CMSSW_9_0_2 onwards CRUZET/CRAFT 90X_dataRun2_HLT_v1 with
- in GEM reco geometry tag the IOV has been moved to first run of 2017
- update of L1T CaloParam and addition of L1T MuonParam tags
- technical update of HCAL reco param tag
90X_dataRun2_HLT_v1 for CMSSW_9_0_0_pre5 onwards first test of HLT MWGR1 with phaseI plan1 HCAL detector in raw as 90X_dataRun2_HLT_v1 with
- a run-dependent HCAL reco geometry to serve the phaseI-plan1 for runs >=287446
- the full set of HCAL calibrations which include the upgraded HF and plan1 HE

Express reconstruction Global Tags

TAGNAME Validity Description Comments
92X_dataRun2_Express_v8 for CMSSW_9_2_13 onwards collisions 92X_dataRun2_Express_v7 with
- merge the express and hlt tags for ECAL preshower
92X_dataRun2_Express_v7 for CMSSW_9_2_7 onwards collisions 92X_dataRun2_Express_v6 with
- include CTPPS tags
92X_dataRun2_Express_v6 for CMSSW_9_2_7 onwards collisions 92X_dataRun2_Express_v4 with
- update HAD and EM PF cluster calibration
92X_dataRun2_Express_v4 for CMSSW_9_2_6 onwards collisions 92X_dataRun2_Express_v2 with
- change of pixel local calibration and derived alignment to account for the recalibrarted pixel VCAL
92X_dataRun2_Express_v2 for CMSSW_9_2_0 onwards first collisions 90X_dataRun2_Express_v4 with
- change of pixel mapping tag to fix the phaseI history
- PGeometricDetExtra, PGeometricDet, PTrackerParameters adapted to have the same history
90X_dataRun2_Express_v4 for CMSSW_9_0_2 onwards CRUZET/CRAFT as 90X_dataRun2_Express_v2 with
- In GEM reco geometry tag the IOV has been moved to first run of 2017
- update of L1T CaloParam and addition of L1T MuonParam tags
- technical update of HCAL reco param tag.
90X_dataRun2_Express_v2 for CMSSW_9_0_0_pre5 onwards first test of T0 with phaseI plan1 HCAL detector in raw as 90X_dataRun2_Express_v1 with
- Jet Energy Correction adapted to pA and energy with better accuracy at low pT
- inclusion of GEM geometry, required by the 2017 CMSSW eras
- a run-dependent HCAL reco geometry to serve the phaseI-plan1 for runs >=287446
- the full set of HCAL calibrations which include the upgraded HF and plan1 HE
- the updated Jet Energy corrections
90X_dataRun2_Express_v1 for CMSSW_9_0_0_pre4 onwards First Express GT for 90X to address the replay request by Slava : https://hypernews.cern.ch/HyperNews/CMS/get/tier0-Ops/1564.html Copy of 90X_dataRun2_Express_v0. as 90X_dataRun2_Express_Queue

Prompt reconstruction Global Tags

TAGNAME Validity Description Comments
92X_dataRun2_Prompt_v11 for CMSSW_9_2_13 onwards collisions 92X_dataRun2_Prompt_v10 with
- new prompt tag for ECAL Pedestals with PCL synch. ECAL pedestals PCL is made to populate this tag now. First IOV is 306091.
92X_dataRun2_Prompt_v10 for CMSSW_9_2_13 onwards collisions 92X_dataRun2_Prompt_v9 with
- separate the hlt/express and prompt tags for ECAL preshower.
92X_dataRun2_Prompt_v9 for CMSSW_9_2_11 onwards collisions 92X_dataRun2_Prompt_v8 with
- remove the separation of express and prompt tags for pixel offline and tracker alignment tags. bring back the consistency in beamspot computation
92X_dataRun2_Prompt_v8 for CMSSW_9_2_7 onwards collisions 92X_dataRun2_Prompt_v7 with
- adding CTPPS tags
92X_dataRun2_Prompt_v7 for CMSSW_9_2_7 onwards collisions 92X_dataRun2_Prompt_v7 with
- update HAD and EM PF cluster calibration
92X_dataRun2_Prompt_v6 for CMSSW_9_2_6 onwards collisions 92X_dataRun2_Prompt_v5 with
- change of pixel local calibration and derived alignment to account for the recalibrarted pixel VCAL
92X_dataRun2_Prompt_v5 for CMSSW_9_2_6 onwards collisions 92X_dataRun2_Prompt_v4 with
- temporarily DECOUPLE express and prompt for pixel commissioning , which will be reverted
- pixel genErrors, templates, lorenzAngle . tracker Alignmenet, APE and SURFACES: all these tags are copied from their express versio
92X_dataRun2_Prompt_v4 for CMSSW_9_2_0 onwards first collisions 92X_dataRun2_Prompt_v2 with
- splitting of pixel gain between express and prompt
92X_dataRun2_Prompt_v2 for CMSSW_9_2_0 onwards first collisions 90X_dataRun2_Prompt_v3 with
- change of pixel mapping tag to fix the phaseI history
- PGeometricDetExtra, PGeometricDet, PTrackerParameters adapted to have the same history
90X_dataRun2_Prompt_v3 for CMSSW_9_0_2 onwards CRUZET/CRAFT as 90X_dataRun2_Prompt_v2 with
- In GEM reco geometry tag the IOV has been moved to first run of 2017
- update of L1T CaloParam and addition of L1T MuonParam tags
- technical update of HCAL reco param tag and prompt version of HCAL channel quality, gains and response corrections are added instead of hlt ones.
90X_dataRun2_Prompt_v2 for CMSSW_9_0_0_pre5 onwards first test of T0 with phaseI plan1 HCAL detector in raw as 90X_dataRun2_Prompt_v1 with
- Jet Energy Correction adapted to pA and energy with better accuracy at low pT
- inclusion of GEM geometry, required by the 2017 CMSSW eras
- a run-dependent HCAL reco geometry to serve the phaseI-plan1 for runs >=287446
- the full set of HCAL calibrations which include the upgraded HF and plan1 HE
- the updated Jet Energy corrections
90X_dataRun2_Prompt_v1 for CMSSW_9_0_0_pre4 onwards First prompt GT for 90X to address the replay request by Slava : https://hypernews.cern.ch/HyperNews/CMS/get/tier0-Ops/1564.html. Copy of 90X_dataRun2_Prompt_v0 with infinite snapshot time. as 90X_dataRun2_Prompt_Queue

Global Tags for 2016 data taking


#GR16HEP

HLT reconstruction Global Tags


#GR16H

TAGNAME Validity Description Comments
80X_dataRun2_pA_HLT_v0 for CMSSW_8_0_X X>=22 To be used for 2016 pA operations as 80X_dataRun2_HLT_v12 with
- Jet Energy Correction adapted to pA and energy with better accuracy at low pT
80X_dataRun2_HLT_v12 for CMSSW_8_0_X X>4 To be used for 2016 pre-beam operations as 80X_dataRun2_HLT_v11 with
- new tags for DT and CSC Alignment errors (allow updates via append IOV with HLT synchronization)
80X_dataRun2_HLT_v11 for CMSSW_8_0_X X>4 To be used for 2016 pre-beam operations as 80X_dataRun2_HLT_v10 with
- adding 7 payloads for GBRWrapperRcd for tracking MVA needed by CMSHLT-716
80X_dataRun2_HLT_v10 for CMSSW_8_0_X X>3 To be used for 2016 pre-beam operations as 80X_dataRun2_HLT_v9 with
-updated set of HLT Jet Energy correction (v11)
80X_dataRun2_HLT_v9 for CMSSW_8_0_X X>3 To be used for 2016 pre-beam operations as 80X_dataRun2_HLT_v8 with
- updated set of HLT Jet Energy correction (v10)
80X_dataRun2_HLT_v8 for CMSSW_8_0_X X>2 To be used for 2016 pre-beam operations as 80X_dataRun2_HLT_v7
- better nomenclature for L1TUtmTriggerMenuRcd for stage-2 L1 menu (will receive O2O updates)
80X_dataRun2_HLT_v7 for CMSSW_8_0_X X>2 To be used for 2016 pre-beam operations as 80X_dataRun2_HLT_v6
- adding new Condition Format L1TUtmTriggerMenuRcd for stage-2 L1 menu (will receive O2O updates)
80X_dataRun2_HLT_v6 for CMSSW_8_0_X X>0 To be used for 2016 MWGR-III operations as 80X_dataRun2_HLT_v4
- introducing an IOV in 2016 for Hcal Parameters to include 1x1 HF trigger primitives
80X_dataRun2_HLT_v4 for CMSSW_8_0_X X>0 To be used for 2016 MWGR-II operations as 80X_dataRun2_HLT_v3
- updated Hcal e-maps (unlabeled and full) for unpacking of uTCA FEDs in HBHE
80X_dataRun2_HLT_v3 for CMSSW_8_0_X X>0 To be used for 2016 MWGR-II operations as 80X_dataRun2_HLT_v2
- updated ES intercalibrations and ESEE intercalibrations
- added e-gamma mustache regressions for HLT
- updated HLT JEC energy correction with L2L3 residuals and hadron PF calibration
80X_dataRun2_HLT_v2 for CMSSW_8_0_X X>0 To be used for 2016 MWGR-II operations as 75X_dataRun2_HLT_v7
- added HLT label for B-tagging MVA calibrations
- new egamma regresions for 2016
- added payload for HCalParameterRcd
- added payload for HCalQIETypesRcd
- added label HLT for PFCalibrations
- added payload for PHcalParametersRcd
- technical change on the DTRecoUncertainties tag name to remove fully qualified V1 account name
- technical change on the ESInterCalibConstantsRcd and EcalGainRationsRcd to remove fully qualified V1 account name
- new version for PHcalRcd
- changed CaloTower topology

Express reconstruction Global Tags


#GR16E

TAGNAME Validity Description Comments
80X_dataRun2_Express_v15 for CMSSW_8_0_X X>=20 To be used for 2016 beam operations as 80X_dataRun2_Express_v15 with
- tags for JER and JER SF with content for DATA and with express synchronization
80X_dataRun2_Express_v14 for CMSSW_8_0_X X>=20 To be used for 2016 beam operations as 80X_dataRun2_Express_v13 with
- updated/added JER and JER Data/MC scale factors
80X_dataRun2_Express_v13 for CMSSW_8_0_X X>=19 To be used for 2016 beam operations as 80X_dataRun2_Express_v12 with
- added needed AlCaReco trigger keys for HIP monitoring
80X_dataRun2_Express_v12 for CMSSW_8_0_X X>=14 To be used for 2016 beam operations as 80X_dataRun2_Express_v11 with
- updated DropBoxMetaData (v5.1) to activate SiPixelAli PCL workflow in express/prompt production tag.
80X_dataRun2_Express_v11 for CMSSW_8_0_X X>=14 To be used for 2016 beam operations as 80X_dataRun2_Express_v10 with
- updated SiStrip and Tracking DQM TriggerBits from DB
80X_dataRun2_Express_v10 for CMSSW_8_0_X X>=10 To be used for 2016 beam operations as 80X_dataRun2_Express_v9 with
- correct snapshot time (set to infinity: 9999-12-31 23:59:59,000000)
80X_dataRun2_Express_v9 for CMSSW_8_0_X X>=10 Red led NOT TO USE! WRONG SYNCHRONIZATION Red led as 80X_dataRun2_Express_v8 with
- updated Jet Energy Corrections for 2016C including 2016 data-mc residuals and uncertainties
- added JEC for algortihm AK4PT and AK4Calo
- introduced new Tracker Alignment tag (copy of the existing one) for the purpose of switching on the SiPixelAli PCL.
80X_dataRun2_Express_v8 for CMSSW_8_0_X X>=10 To be used for 2016 beam operations as 80X_dataRun2_Prompt_v7 updating
- updated DropBoxMetadata payload to fix the SiStripGainAfterAbortGap PCL worflow.
80X_dataRun2_Express_v7 for CMSSW_8_0_X X>=8 To be used for 2016 beam operations as 80X_dataRun2_Prompt_v6 updating
- updated DropBoxMetadata payload to fix the SiPixeAli PCL worflow.
80X_dataRun2_Express_v6 for CMSSW_8_0_X X>=5 To be used for 2016 beam operations as 80X_dataRun2_Prompt_v4 updating
- splitting ECAL pedestal tag between HLT and EXPRESS/PROMPT
80X_dataRun2_Express_v4 for CMSSW_8_0_X X>3 To be used for 2016 pre-beam operations as 80X_dataRun2_Express_v3 adding
- better nomenclature for L1TUtmTriggerMenuRcd for stage-2 L1 menu (will receive O2O updates)
- 4 labels for JetResolutionScaleFactorRcd and 10 labels for JetResolutionRcd needed for MET code updates.
80X_dataRun2_Express_v3 for CMSSW_8_0_X X>2 To be used for 2016 pre-beam operations as 80X_dataRun2_Express_v2 adding
- new Condition Format L1TUtmTriggerMenuRcd for stage-2 L1 menu (will receive O2O updates)
80X_dataRun2_Express_v2 for CMSSW_8_0_X X>0 To be used for 2016 MWGR-III operations as 80X_dataRun2_Express_v1
- introducing an IOV in 2016 for Hcal Parameters to include 1x1 HF trigger primitives
80X_dataRun2_Express_v1 for CMSSW_8_0_X X>0 To be used for 2016 MWGR-II operations as 80X_dataRun2_Express_v0
- updated Hcal e-maps (unlabeled and full) for unpacking of uTCA FEDs in HBHE
80X_dataRun2_Express_v0 for CMSSW_8_0_X X>0 To be used for 2016 MWGR-II operations as 75X_dataRun2_Express_v0
- added HLT label for B-tagging MVA calibrations
- new egamma regresions for 2016
- added payload for HCalParameterRcd
- added payload for HCalQIETypesRcd
- added label HLT for PFCalibrations
- added payload for PHcalParametersRcd
- technical change on the DTRecoUncertainties tag name to remove fully qualified V1 account name
- new version for PHcalRcd
- changed CaloTower topology

Prompt reconstruction Global Tags


#GR16P

TAGNAME Validity Description Comments
80X_dataRun2_Prompt_v16 for CMSSW_8_0_X X>=24 Moriond17 recommandation for 02Feb2016 reminiaod as 80X_dataRun2_Prompt_v15 with
- new JEC for reMiniAod 02Feb2017 campaign (based on Summer16 MC)
80X_dataRun2_Prompt_v15 for CMSSW_8_0_X X>=20 To be used for 2016 beam operations as 80X_dataRun2_Prompt_v14 with
- castor local reconstruction tags cloned and separated from the hlt ones
80X_dataRun2_Prompt_v14 for CMSSW_8_0_X X>=20 To be used for 2016 beam operations as 80X_dataRun2_Prompt_v13 with
- tags for JER and JER SF with content for DATA and with express synchronization
80X_dataRun2_Prompt_v13 for CMSSW_8_0_X X>=20 To be used for 2016 beam operations as 80X_dataRun2_Prompt_v12 with
- updated/added JER and JER Data/MC scale factors
80X_dataRun2_Prompt_v12 for CMSSW_8_0_X X>=19 To be used for 2016 beam operations as 80X_dataRun2_Prompt_v11 with
- added needed AlCaReco trigger keys for HIP monitoring
80X_dataRun2_Prompt_v11 for CMSSW_8_0_X X>=14 To be used for 2016 beam operations as 80X_dataRun2_Prompt_v10 with
- amended SiPixelQuality history during post-MD2 Prompt Reco pause (split tag from HLT/Express)
80X_dataRun2_Prompt_v10 for CMSSW_8_0_X X>=14 To be used for 2016 beam operations as 80X_dataRun2_Prompt_v9 with
- updated SiStrip and Tracking DQM TriggerBits from DB
80X_dataRun2_Prompt_v9 for CMSSW_8_0_X X>=10 To be used for 2016 beam operations as 80X_dataRun2_Prompt_v8 with
- updated Jet Energy Corrections for 2016C including 2016 data-mc residuals and uncertainties
- added JEC for algortihm AK4PT and AK4Calo
- introduced new Tracker Alignment tag (copy of the existing one) for the purpose of switching on the SiPixelAli PCL.
80X_dataRun2_Prompt_v8 for CMSSW_8_0_X X>=5 To be used for 2016 beam operations as 80X_dataRun2_Prompt_v7 updating
- splitting ECAL pedestal tag between HLT and EXPRESS/PROMPT
80X_dataRun2_Prompt_v6 for CMSSW_8_0_X X>=5 To be used for 2016 pre-beam operations as 80X_dataRun2_Prompt_v5 updating
- new tags to accommodate DT and CSC Alignment errors (allow updates via append IOV with express synchronization)
- new tag for HBHENegativeEFilter (allows updates via append IOV with express synchronization)
- latest set of HLT JECs (v11)
80X_dataRun2_Prompt_v5 for CMSSW_8_0_X X>3 To be used for 2016 pre-beam operations as 80X_dataRun2_Prompt_v4 with:
- propagation of latest available set of HLT JECs (v10)
80X_dataRun2_Prompt_v4 for CMSSW_8_0_X X>3 To be used for 2016 pre-beam operations as 80X_dataRun2_Prompt_v3 adding
- better nomenclature for L1TUtmTriggerMenuRcd for stage-2 L1 menu (will receive O2O updates)
- 4 labels for JetResolutionScaleFactorRcd and 10 labels for JetResolutionRcd needed for MET code updates.
80X_dataRun2_Prompt_v3 for CMSSW_8_0_X X>2 To be used for 2016 pre-bem operations as 80X_dataRun2_Prompt_v2 adding
- new Condition Format L1TUtmTriggerMenuRcd for stage-2 L1 menu (will receive O2O updates)
80X_dataRun2_Prompt_v2 for CMSSW_8_0_X X>0 To be used for 2016 MWGR-III operations as 80X_dataRun2_Prompt_v1
- introducing an IOV in 2016 for Hcal Parameters to include 1x1 HF trigger primitives
80X_dataRun2_Prompt_v1 for CMSSW_8_0_X X>0 To be used for 2016 MWGR-II operations as 80X_dataRun2_Prompt_v0
- updated Hcal e-maps (unlabeled and full) for unpacking of uTCA FEDs in HBHE
80X_dataRun2_Prompt_v0 for CMSSW_8_0_X X>0 To be used for 2016 MWGR-II operations as 75X_dataRun2_Prompt_v2
- added HLT label for B-tagging MVA calibrations
- new egamma regresions for 2016
- added payload for HCalParameterRcd
- added payload for HCalQIETypesRcd
- added label HLT for PFCalibrations
- added payload for PHcalParametersRcd
- technical change on the DTRecoUncertainties tag name to remove fully qualified V1 account name
- new version for PHcalRcd
- changed CaloTower topology

Global Tags for 2015 data taking


#GR15HEP

HLT reconstruction Global Tags


#GR15H

TAGNAME Validity Description Comments
74X_dataRun2_HLT_ppAt5TeV_v0 for CMSSW_7_4_X X>=6 To be used for pp reference run @ 5.02TeV operations As 74X_dataRun2_HLT_v3 changing:
- replaced AK4Calo HLT JEC for pp reference run at 5 TeV and HI run
74X_dataRun2_HLT_v3 for CMSSW_7_4_X X>=6 To be used for 2015C (25 ns collisions) As 74X_dataRun2_HLT_v2 changing:
- taxonomy changes for the muon APE
- replacing tag names containing fully qualified conddB v1 account
74X_dataRun2_HLT_v2 for CMSSW_7_4_X X>=6 To be used for 2015C (25 ns collisions) As 74X_dataRun2_HLT_v1 changing:
- re-introducing the HLT Tracker backplane corrections tag
74X_dataRun2_HLT_v1 for CMSSW_7_4_X X>=6 To be used for 2015C (25 ns collisions) As GR_H_V58C changing:
- updated ECAL cluster parametric corrections: first IOV is identical to the latest data corrections as in EcalClusterLocalContCorrParameters _jun2012_offline, second IOV, starting after AGR, has corrections set to 0, as in EcalClusterLocalContCorrParameters _invalidate_offline, third IOV, starting in Run2015B, is identical to the latest data corrections as in EcalClusterLocalContCorrParameters _jun2012_offline, validated as of 2015-06-18;
- added record for HB HE negative energy filter.
74X_dataRun2_HLT_v0 for CMSSW_7_4_X X>=0 To be used for 2015C (25 ns collisions) As GR_H_V58C changing:
- updated ECAL cluster parametric corrections: first IOV is identical to the latest data corrections as in EcalClusterLocalContCorrParameters _jun2012_offline, second IOV, starting after AGR, has corrections set to 0, as in EcalClusterLocalContCorrParameters _invalidate_offline, third IOV, starting in Run2015B, is identical to the latest data corrections as in EcalClusterLocalContCorrParameters _jun2012_offline, validated as of 2015-06-18.
GR_H_V58C for CMSSW_7_4_X X>=0 To be used for 2015A+B (50 ns collisions) As GR_H_V58 changing:
- changed ECAL Cluster corrections tag name to contain "hlt"
- adding: label "full" for HcalElectronicsMapRcd

Express reconstruction Global Tags


#GR15E

TAGNAME Validity Description Comments
75X_dataRun2_Express_ppAt5TeV_v0 for CMSSW_7_5_X X>=5 [*] To be used for pp reference run @ 5.02 TeV taking operations as 74X_dataRun2_Express_v3 changing:
-
74X_dataRun2_Express_v3 for CMSSW_7_4_X X>=10 [*] To be used Run2015D (25ns) data taking operations as 74X_dataRun2_Express_v2 changing:
- updating to new Jet Energy corrections
- taxonomy change for the Muon APE (=0 explicit)
- added new GBRForest payloads for the existing TMVA-based taggers.
74X_dataRun2_Express_v2 for CMSSW_7_4_X X>=10 [*] To be used Run2015D (25ns) data taking operations as 74X_dataRun2_Express_v1 changing:
- added e/gamma regression from ECAL multifit
- changes in taxonomy for SiStripBackPlaneCorrection (introducing express tag).
74X_dataRun2_Express_v1 for CMSSW_7_4_X X>=8 [*] To be used Run2015C (25ns) data taking operations as 74X_dataRun2_Express_v0 changing:
- adding Negative Energy Filter tag.
74X_dataRun2_Express_v0 for CMSSW_7_4_X X>=1 [*] To be used Run2015B (50ns) data taking operations as GR_E_V49 changing:
- taxonomy of the EcalClusterLocalContCorrParametersRcd
GR_E_V49 for CMSSW_7_4_X X>=1 To be used for first beam data 2015 As GR_E_V48
- improved Dropbox metadata to fix PCL uploads
- new tag for DT t0 calibration taking into account FEB path corrections
GR_E_V48 for CMSSW_7_4_X X>=1 To be used for first beam data 2015 As GR_E_V47
- adding: label "full" for HcalElectronicsMapRcd

Prompt reconstruction Global Tags


#GR15P

TAGNAME Validity Description Comments
75X_dataRun2_Prompt_v1 for CMSSW_7_5_X X>5 [*] To be used for Heavy Ion data-taking operations as 74X_dataRun2_Prompt_v2
-
75X_dataRun2_Prompt_v4 for CMSSW_7_4_X X>10 [*] To be used Run2015D (25ns) data taking operations as 74X_dataRun2_Prompt_v3
- updating to new Jet Energy corrections
- taxonomy change for the Muon APE (=0 explicit)
- added new GBRForest payloads for the existing TMVA-based taggers
74X_dataRun2_Prompt_v3 for CMSSW_7_4_X X>10 [*] To be used Run2015D (25ns) data taking operations as 74X_dataRun2_Prompt_v2
- introduced prompt version for Strip O2O tags
74X_dataRun2_Prompt_v2 for CMSSW_7_4_X X>10 [*] To be used Run2015D (25ns) data taking operations as 74X_dataRun2_Prompt_v1
- added e/gamma regression from ECAL multifit
- changes in taxonomy for SiStripBackPlaneCorrection (introducing express tag)
- changes in taxonomy for the TrackerAlignment (introducing prompt tag)
74X_dataRun2_Prompt_v1 for CMSSW_7_4_X X>=6 [*] To be used Run2015B/C (50/25ns) data taking operations as 74X_dataRun2_Prompt_v0
- adding Negative Energy Filter tag.
74X_dataRun2_Prompt_v0 for CMSSW_7_4_X X>=1 [*] To be used Run2015B (50ns) data taking operations as GR_P_V56
- changing name of tag for EcalClusterLocalContCorrParameters to decouple it from MC
upgrade tag for DTT0Rcd to FEB corrected one
GR_P_V56 for CMSSW_7_4_X X>=1 To be used for first beam data 2015 As GR_P_V55 with:
- changed ECAL Cluster corrections to parametric (as in run2 MC)
- added all labels for JetCorrectionsRecord (JEC), required for MINIAOD production
GR_P_V55 for CMSSW_7_4_X X>=1 To be used for first beam data 2015 As GR_P_V54 whith:
- new tag for EcalLaserAPDPNRatiosRcd to allow O2O to properly work
- adding: label "full" for HcalElectronicsMapRcd
[*] This Global Tag exists only in the conditions Database v2. This means you should include Configuration.StandardSequences.FrontierConditions_GlobalTag_condDBv2_cff in CMSSW_7_4_X.

Global Tags for Monte Carlo Production

Available global tags for MC production are listed in the tables below. The list of database tags which are included in a given global tag can be viewed by following the links in the tables.

Mis-calibration and mis-alignment scenarios

Global tags for MC production other than those which use IDEAL conditions apply a smearing of alignment and calibration constants defined through certain mis-calibration and mis-alignment scenarios. Details concerning these scenarios can be found here. Additional information about individual tags within the global tags can be found at the links provided here

Special GTs for Upgrade

Documented at the following Twiki

GTs for special MC productions

TAGNAME Validity Description Comments
START53_V19H >=CMSSW_5_3_8_patch3 For special MinBias ECAL production (B field OFF) As START53_V19 with the following updates:
- Magnetic field OFF ECAL [[https://twiki.cern.ch/twiki/bin/viewauth/CMS/EcalMCConditions][conditions]
START53_V19G >=CMSSW_5_3_8_patch3 For special MinBias ECAL production (B field ON) As START53_V19 with the following updates:
- Magnetic field ON ECAL [[https://twiki.cern.ch/twiki/bin/viewauth/CMS/EcalMCConditions][conditions]
START53_V19F >=CMSSW_5_3_8_patch3 For run dependent MC conditions As START53_V19 with the following updates:
- Run-dependent L1 menu conditions and PU mixing configuration for 2012A,B,C,D eras.
START53_V14B >=CMSSW_5_3_8_patch3 For Egamma systematic studies As START53_V14A with the following change:
- “Flat30” geometry tag
START53_V14A >=CMSSW_5_3_8_patch3 For Hgg systematic studies As START53_V14 with the following updates:
- run dependent ECAL conditions taken from START53_V7N

74Y Releases (MC)

74Y Releases


#MC74X The following are valid for 74X releases:

TAGNAME Validity Description Comments
MCRUN2_74_V8A CMSSW >= 7_4_1 As 'run2_mcStartup' GT, but with "worst" case scenario SiPixelQualityFromDbRcd As MCRUN2_74_V8 with the following changes:
- Introduced SiPixelQuality_v23: only Layer 3 is working in BmO Sec 3 (i.e. Pixel Barrel, negative z half barrel, outer shell, sector 3), so the whole layers 1 and 2 are out.
MCRUN2_74_V8B CMSSW >= 7_4_1 As 'run2_mcStartup' GT, but with "best" case scenario SiPixelQualityFromDbRcd As MCRUN2_74_V8 with the following changes:
- Introduced SiPixelQuality_v24: 3 modules of Layer 1 and full Layer 3 work in BmO Sec 3 (i.e. Pixel Barrel, negative z half barrel, outer shell, sector 3), so 1 module in Layer 1 and the whole Layer 2 are out.
MCRUN2_74_V9C CMSSW >= 7_4_1 As 'run2_mcAsymptotic' GT, but with "worst" case scenario SiPixelQualityFromDbRcd As MCRUN2_74_V9 with the following changes:
- Introduced SiPixelQuality_v23: only Layer 3 is working in BmO Sec 3 (i.e. Pixel Barrel, negative z half barrel, outer shell, sector 3), so the whole layers 1 and 2 are out.
MCRUN2_74_V9D CMSSW >= 7_4_1 As 'run2_mcAsymptotic' GT, but with "best" case scenario SiPixelQualityFromDbRcd As MCRUN2_74_V9 with the following changes:
- Introduced SiPixelQuality_v24: 3 modules of Layer 1 and full Layer 3 work in BmO Sec 3 (i.e. Pixel Barrel, negative z half barrel, outer shell, sector 3), so 1 module in Layer 1 and the whole Layer 2 are out.
MCRUN2_74_V6A CMSSW >= 7_4_0 As 'run2_mcStartup' GT, but with "worst" case scenario SiPixelQualityFromDbRcd As MCRUN2_74_V6 with the following changes:
- Introduced SiPixelQuality_v23: only Layer 3 is working in BmO Sec 3 (i.e. Pixel Barrel, negative z half barrel, outer shell, sector 3), so the whole layers 1 and 2 are out.
MCRUN2_74_V6B CMSSW >= 7_4_0 As 'run2_mcStartup' GT, but with "best" case scenario SiPixelQualityFromDbRcd As MCRUN2_74_V6 with the following changes:
- Introduced SiPixelQuality_v24: 3 modules of Layer 1 and full Layer 3 work in BmO Sec 3 (i.e. Pixel Barrel, negative z half barrel, outer shell, sector 3), so 1 module in Layer 1 and the whole Layer 2 are out.
MCRUN2_74_V7C CMSSW >= 7_4_0 As 'run2_mcAsymptotic' GT, but with "worst" case scenario SiPixelQualityFromDbRcd As MCRUN2_74_V7 with the following changes:
- Introduced SiPixelQuality_v23: only Layer 3 is working in BmO Sec 3 (i.e. Pixel Barrel, negative z half barrel, outer shell, sector 3), so the whole layers 1 and 2 are out.
MCRUN2_74_V7D CMSSW >= 7_4_0 As 'run2_mcAsymptotic' GT, but with "best" case scenario SiPixelQualityFromDbRcd As MCRUN2_74_V7 with the following changes:
- Introduced SiPixelQuality_v24: 3 modules of Layer 1 and full Layer 3 work in BmO Sec 3 (i.e. Pixel Barrel, negative z half barrel, outer shell, sector 3), so 1 module in Layer 1 and the whole Layer 2 are out.

More... Close


For Run-I and earlier version of Global tags :

* please refer to : https://twiki.cern.ch/twiki/bin/view/CMSPublic/SWGuideFrontierConditions?rev=609*

NOTES:


#NOTENotProd

[1] Global Tags labelled with (Not for prod. 1]) are not meant for production since some of the records are read from the preparation account and could not be readable forever.


#NOTESnapValid

[2] Global Tags which are 'frozen snapshots' meant for central re-reco should be used with care since the tags are up to date only until the last run interested by that particular re-reco (which is usually indicated in the documentation). Being frozen, by definition, they can not be further updated and the original version should be used instead. For more details please refer to the GT tutorial, looking in particular to slides 6 to 12.

-- GianlucaCerminara - 09-Apr-2010

Topic revision: r623 - 2018-09-12 - SanteriLaurila
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CMSPublic All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback