Global Tags for Conditions Data

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:

• from Configuration.AlCa.GlobalTag import GlobalTag

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:
  • https://cms-conddb.cern.ch/cmsDbBrowser
• 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

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 TrackerAlignmentRcd and 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.

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

Show... Hide

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

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

---- 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

from CalibMuon.DTCalibration.DTFakeVDriftESProducer_cfi import *

process.prefer("CMS.GlobalTag")

Global Tags keys for RelVal workflows

See GT for release cycle page

Global Tags used in official data reprocessing / MC productions

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
90X_upgrade2017_realistic_PerfectEcalIc_EGM_PFCalib	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 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)

Global Tags for large gun sample (72X)

Global Tags for Run2 TSG studies (72X)

Run2 MC production (71X)

PHYS14 exercise (72X)

Notes:

• PHYS14_25_V1 has all the tags stored in the CondDBv2 production account, while the HCAL OOT PU corrections are still in development DB for CondDBv1. Given that 720 is reading the new Conditions, this Global Tag is ok for production. As soon as the tags are migrated to old production accounts, we will anyhow create a new Global Tag.
• The RPC L1T in 2015 will not have any special configuration for 50 ns w.r.t 25 ns, anyway it will be HSCP-oriented: hence, for Run2 simulations, there is no more difference between the two bunch crossing scenarios.
• Unfortunately, there are no existing SIM geometry tags containing only the TECR7 bug-fix for Run2 in 62X, in order to match the one used by the GEN-SIM production (6.2.12.patch1), so we cannot include in this Global Tag -for sake of consistency- the "bug-fixed" SIM geometry (even if not consumed).

2013 re-reco for pp and pA (53X)

DATA.MC validation exercise (71X)

CSA14 exercise

miniAOD production

GT name	Comments
PLS170_V7AN2	GT for 25ns (asymptotic alignment and calibration scenario) 2nd production, as PLS170_V7AN1 + updated JEC
PLS170_V6AN2	GT for 50ns (more pessimistic alignment and calibration scenario) 2nd production, as PLS170_V6AN1 + updated JEC
PLS170_V7AN1	GT for 25ns (asymptotic alignment and calibration scenario), as POSTLS170_V7 + updated JEC
PLS170_V6AN1	GT for 50ns (more pessimistic alignment and calibration scenario), as POSTLS170_V6 + updated JEC
GR_70_V2_AN1	GT for data in 70X, as GR_R_70_V2 + updated JEC

Collisions

Cosmics (70X)

Cosmics (72X)

ReReco of 2012D in CMSSW_7_0_0

8 TeV MC Production in CMSSW_7_0_0 (special ECAL request)

13 TeV DR in CMSSW_7_0_0 (special ECAL request)

8 TeV MC Production in CMSSW_5_3_X (special ECAL request)

7TeV Heavy Ion MC "Legacy" reprocessing

2011 Heavy Ion data "Legacy" reprocessing

GT name	Comments
FT_R_53_LV9	GT for 53X peripheral PbPb data reprocessing using pp reconstruction, as GR_R_53_LV6 with: - updated centrality tag - new JEC as requested here
GR_R_53_LV6	GT for 53X data re-RECO, as FT_R_53_LV5 (legacy pp re-reco) with - compatibility tags - updated Tracker alignment - updated BeamSpot - Castor conditions - HCAL ZS tags
GR_R_53_LV6A	reference GT (44X conditions ported into 53X), as GR_P_V27A with - compatibility tags for 53X
GR_P_V27A	reference GT for 44X release (used for 2011 HI reprocessing in 44X, same as in prompt)

7TeV MC "Legacy" reprocessing in CMSSW_5_3_X

NOTE : The newly derived 2011 JEC have been included in the analysis GTs. b-tagging SF are under evaluation and will be included afterwards.

2011AB Legacy re-reco (CMSSW_5_3_11)

NOTE : The newly derived 2011 JEC have been included in the analysis GTs.

Winter13 2012 A, B, C, D datasets re-reco with CMSSW_5_3_7_patch6

NOTE : The new 2013 JEC (Summer13_V4) have been included in the data GT (FT_53_V21_AN6) and in the MC GTs (START53_V26 & START53_V27). The BTag scale factors are included in the MC GTs.

2012ABCD datasets re-reco + prompt (CMSSW = [5_3_3_patch1 ; 5_3_8_patch2])

Please see section "Summary of Global Tags used in official data re-recos or MC productions" for the latest recommendations.

Mixing prompt and re-reco dataset as recommended here. The GTs provided here for the analysis are only compatible with 5_3_3_patch1 <= CMSSW < 5_3_8_patch3. The upper release limit is due to Castor saturations compatibility issues.

NOTE1: for all the details concerning how to combine these datasets, please refer to the official PdmV page

NOTE2: the GT suffix "AN4" indicates that the new 2012 b-tag SF have been included in the data GT, with respect to the previous version ("AN3")

NOTE3: the correspondent MC GTs including the new 2012 b-tag SF are also indicated and have to be "paired" with the corresponding datasets Prompt + Reco (here the suffix "PR"), to be consistent with the dataset used to derive them.

Special Pixel re-reco(16Jan), please refer here how to combine correctly the JSON!

2012 B, C, D: multijet parked dataset (CMSSW_5_3_6)

2012 C v1: data re-reco (CMSSW_5_3_2_patch4)

2012 A and B: data re-reco (CMSSW_5_3_2_patch4 and CMSSW_5_3_3_patch1)

2012: post-ICHEP data re-reco ( CMSSW_5_2_5_patch3 and CMSSW_5_2_5_ecalpatch1 ) for H->gg and H->ZZ

2012: pre-ICHEP data re-reco with CMSSW_5_2_5_patch3 and CMSSW_5_2_5_ecalpatch1 for H->gammagamma

2012: special data re-reco with CMSSW_5_2_5_ecalpatch1 to recover corrupted ECAL data

2011 data re-reco with 44X

2011 data re-reco with 42X

2012 MC production

2011 MC production

Global Tags for Data Taking

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_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_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

HLT reconstruction Global Tags

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

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	NOT TO USE! WRONG SYNCHRONIZATION	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

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

HLT reconstruction Global Tags

Express reconstruction Global Tags

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

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 pre-2015 data exercise

HLT reconstruction Global Tags

Express reconstruction Global Tags

Prompt reconstruction Global Tags

Global Tags for 2012 data taking

Disclaimer for analysis of prompt reconstruction data

The global tags listed just below have been used to reconstruct data at T0 and they do not include all the features needed for the analysis.
Starting with 2012C, for the analysis of the prompt reco data collected using GR_P_VXX at T0 we advise to use the analysis global tag called GR_P_VXX_ANZZ. More details can be found in the section Analysis GT for prompt reco data.
We encourage you to switch to the re-recoed data with the appropriate analysis GT listed in section Summary of Global Tags used in official data re-recos as soon as they are available.

For analysis of prompt reco data collected in 2011, 2012A and 2012B eras.

Show... Hide

Prompt reconstruction Global Tags

TAGNAME	Validity	Description	Comments
GR_P_V43D	>5_3_8_patch3	Used for prompt-reco in GRIN	As GR_P_V43 with the following updates: castor saturation added.
GR_P_V43C	>=610_pre8X (Not for prod.[1])	To be used for prompt data processing @ Tier0.	As GR_P_V43B with the following updates: - best ECAL conditions for 2011: local cluster corrections - Updated ECAL cluster corrections.
GR_P_V43B	>=61X_pre8X (Not for prod.[1])	To be used for prompt data processing @ Tier0.	As GR_P_V43 with the following updates: - first version of HB alignment - first version of HE alignment - first version of HF alignment - first version of HO alignment.
GR_P_V43	>=533X	To be used for prompt data processing @ Tier0.	As GR_P_V42B with the following updates: - AK5 PF JECs added
GR_P_V42B	>=533	To be used for prompt data processing @ Tier0.	As GR_P_V42 with the following updates: - Updated jet energy corrections to the ones used by the HLT since mid-Run2012C. - Separated the AK5Calo corrections used at HLT from those used at RECO.
GR_P_V42	>=533	To be used for prompt data processing @ Tier0.	As GR_P_V41 with the following updates: - To use the same tracker alignment tag for express and prompt - updated CSC bad chambers.
GR_P_V41	>=533	To be used for prompt data processing @ Tier0.	As GR_P_V40 with the following updates: - possibility to mask ECAL samples added.
GR_P_V40	53X, <533	To be used for prompt data processing @ Tier0.	As GR_P_V38 with the following updates: - Decoupling pixel templates from HLT - Fix for ECAL LocalContCorrParameters.
GR_P_V39B	52X	To be used for HLT conditions validation.	As GR_P_V39 with the following updates (to stay parallel to GR_P_V42): - To use the same tracker alignment tag for express and prompt - updated CSC bad chambers.
GR_P_V39	52X	To be used for prompt data processing @ Tier0.	As GR_P_V37 with the following updates: - Decoupling pixel templates from HLT.
GR_P_V38	53X,<533	To be used for prompt data processing @ Tier0.	As GR_P_V37 with the following updates: moving to 53X: - new PF cluster corrections - updated ECAL local containment corrections - new supercluster energy correction.
GR_P_V37	52X	To be used for prompt data processing @ Tier0.	As GR_P_V36 with the following updates: - Decoupling the ESChannelStatusRcd from hlt/express to allow masking channels in prompt independently.
GR_P_V36	52X	To be used for prompt data processing @ Tier0.	As GR_P_V35 with the following updates: - Decoupled hlt and express preshower intercalibration tag.
GR_P_V35	52X	To be used for prompt data processing @ Tier0.	As GR_P_V32 with the following updates: - Updated HcalRecoParams for prompt reco fixing HF TS for runs 195265 and 195266.
GR_P_V33	53X - broken	To be used for prompt data processing @ Tier0.	As GR_P_V32 with the following updates: - Moving to 53X: - PF Cluster Corrections in EcalBarrel - PF Cluster Corrections in EcalEndcap - PF Photon Energy Corrections in EcalBarrel - PF Photon Energy Corrections in EcalEndcap for High R9 Photons - PF Photon Energy Corrections in EcalEndcap for Low R9 Photons - PF Photon Energy Resolution Studies using BDTG
GR_P_V32	52X	To be used for prompt data processing @ Tier0.	As GR_P_V29 with the following updates: - new format for DT readout mapping - DT t0 migration.
GR_P_V30	50X	To be used for prompt data processing @ Tier0.	As GR_P_V28 with the following updates: - new format for DT readout mapping.
GR_P_V29	52X (Not for prod.[1])	To be used for prompt data processing @ Tier0.	As GR_P_V28 with the following updates: - DT t0 migration - New payload containing parameters for the HF in HcalHitReconstructor.
GR_P_V28	50X	To be used for prompt data processing @ Tier0.	As GR_P_V27A with the following updates: - Moving to 50X: - New geometry from44X account - strips DCS, v6 - new DTCCBconfig - new DTKeyedConfig - AlcaReco for muon DQM added - ES missing energy calib added - photon regression added - new ECAL cluster corrections - new CSC gas gain corrections - dE/dx as in offline - new Hcal MC param added - new format for Hcal reco param as in 50X - change in name of Ecal channel status tag

Express reconstruction Global Tags

HLT reconstruction Global Tags

Special HLT reconstruction Global Tags

Global Tags for 2011 data taking

Show... Hide

Global tags for 2010 data taking with 3XY

Show... Hide

   process.GlobalTag.connect   = 'frontier://FrontierProd/CMS_COND_31X_GLOBALTAG'
   process.GlobalTag.pfnPrefix = cms.untracked.string('frontier://FrontierProd/')

Global tags for 2009 (and earlier) cosmic data taking with 3XY

Show... Hide

Global tags for prompt reco data analysis (starting with 2012)

Global tags for Winter13 rereco data analysis (starting with 2012)

Please see section "Summary of Global Tags used in official data re-recos or MC productions" for the latest recommendations.

The following global tags should be used for the analysis of Winter13 rereco data. Including parked datasets re-recoed during the Winter13 campaign.

Global tags for Multijet parked data analysis

Global tags for collision data reprocessing

Global tags for collision data reprocessing (71Y)

Global tags for collision data reprocessing (70Y)

Global tags for collision data reprocessing (62X)

TAGNAME	Validity	Description	Comments
GR_R_62_V1	62X >= 620	Not for production.	As PRE_62_V8 with the following updates: - Latest alignments and calibrations taken from FT_R_53_V21 - Updated JEC (Fall12) - Accounts migrated to production DB - Requested on HN
PRE_62_V8	53X >= 538_patch3	Not for production.	As GR_R_61_V5 with the following updates: - Updated geometry payloads - HCAL alignment (transparent, no alignment) - New ECAL cluster energy corrections - New GBRForest payloads for track selections.

Global tags for collision data reprocessing (61X)

Global tags for collision data reprocessing (60X)

Global tags for collision data reprocessing (53X)

TAGNAME	Validity	Description	Comments
GR_R_53_V21A	53X>=538_patch3	To be used for data reprocessing.	As GR_R_53_V21 with the following updates: - castor saturation added.
FT_R_53_V21	53X>=533	To be used for internal cross checks. (Snapshot not valid for runs > 211541 [= 2013-02-08])[2]	As GR_R_53_V21 with the following updates: - reading from frozen snapshot of DB accounts.
GR_R_53_V21	>=533X	To be used for data reprocessing.	As GR_R_53_V20 with the following updates: - Updated HCAL corrections and gains for 2012D reprocessing.
FT_R_53_V20	53X>=533	To be used for reprocessing of 2012D in 53X. (Snapshot not valid for runs > 211541 [= 2013-02-07])[2]	As GR_R_53_V20 with the following updates: - reading from frozen snapshot of DB accounts.
GR_R_53_V20	>=533X	To be used for data reprocessing.	As GR_R_53_V19 with the following updates: - Updated ECAL ADCToGeV covering full 2012 - Updated ECAL Laser corr. covering full 2012 - Fixed bug to Pixel template method - Updated ECAL Intercalibrations covering full 2012.
FT_R_53_V18	53X	For 2012A+B+C data reprocessing in 53X. (Snapshot not valid for runs > 210041 [= 2013-01-15])[2]	As GR_R_53_V18 with the following updates: - reading from frozen snapshot of DB accounts.
GR_R_53_V19	>=533X	To be used for data reprocessing.	As GR_R_53_V18 with the following updates: - Updated AlCaReco Trigger bits.
FT_P_V42D	53X>=533	To be used for MultiJetParked reprocessing. (Snapshot not valid for runs > 210041 [= 2013-01-15])[2]	As GR_P_V42 with the following updates: - reading from frozen snapshot of DB accounts.
GR_R_53_V18	>=533X	To be used for data reprocessing.	As GR_R_53_V17 with the following updates: - Updated ECAL scale corrections fixing a 1% offset. See this posting https://hypernews.cern.ch/HyperNews/CMS/get/calibrations/1309.html.
GR_R_53_V17	>=533X	To be used for data reprocessing.	As GR_R_53_V16F with the following updates: - updated Fall12 JECs - Updated tracker bad channels.
FT_P_V42	>=533X	To be used for parked multijet data reprocessing. (Snapshot not valid for runs > 207947 [= 2012-11-27])[2]	As GR_P_V42 with the following updates: - reading from frozen snapshot of DB accounts.
GR_R_53_V16	>=533X	To be used for data reprocessing.	As GR_R_53_V15 with the following updates: - extended ECAL laser tag (also fixing problem in 2012C data).
FT_P_V42C	>=533X	To be used for parked multijet data reprocessing. (Snapshot not valid for runs > 206495 [= 2012-11-05])[2]	As GR_P_V42C with the following updates: - reading from frozen snapshot of DB accounts.
GR_P_V42C	>=533X	To be used for parked multijet dataset reprocessing.	As GR_P_V42 with the following updates: - extended ECAL laser tag (also fixing problem in 2012C data).
GR_R_53_V15	>=533X	To be used for data reprocessing.	As GR_R_53_V14 with the following updates: - Updated jet energy corrections to the ones used by the HLT since mid-Run2012C. - Separated the AK5Calo corrections used at HLT from those used at RECO.
GR_R_53_V14	>=533X	To be used for data reprocessing.	As GR_R_53_V13 with the following updates: - another bug fix for ECAL laser APD/PN tag
GR_R_53_V13	>=533X	To be used for data reprocessing.	As GR_R_53_V12 with the following updates: - updated JECs for JPT (Aug 2012).
GR_R_53_V12	>=533X	To be used for data reprocessing.	As GR_R_53_V11 with the following updates: - bug fix for ECAL laser APD/PN tag.
GR_R_53_V11	>=533	To be used for data reprocessing.	As GR_R_53_V9 with the following updates: - updated ECAL laser tag (also covering 2010 and 2011) - fix for a problem in DT timing - updated APV gains - updated CSC bad chambers - fix for a problem in DT drift velocity.
FT_R_53_V10A	>=533X	To be used for data reprocessing. (Snapshot not valid for runs > 201060 [= 2012-08-17])[2]. To be used with release >= 5_3_3	As FT_R_53_V10 with the following updates: - Reading the EcalSampleMaskRcd from the FT_R_53_V6C.
FT_R_53_V10	53X	To be used for data reprocessing. (Snapshot not valid for runs > 201060 [= 2012-08-17])[2]	As GR_R_53_V10 with the following updates: - reading from frozen snapshot of DB accounts.
GR_R_53_V10	53X	To be used for data reprocessing.	As GR_R_53_V8 with the following updates: - updated ECAL laser tag (also covering 2010 and 2011) - fix for a problem in DT timing - updated APV gains - updated CSC bad chambers - fix for a problem in DT drift velocity.
GR_R_53_V9	>=533X	To be used for data reprocessing.	As GR_R_53_V8 with the following updates: -possibility to mask ECAL samples added.
GR_R_53_V8	53X	To be used for data reprocessing.	As GR_R_53_V7 with the following updates: - Decoupling the pixel templates tag from HLT/express/prompt.
GR_R_53_V7	53X	To be used for data reprocessing.	As GR_R_53_V6 with the following updates: - New btag and mistag Data/MC scale factors.
FT_R_53_V6C	52X	To be used for data reprocessing. (Snapshot not valid for runs > 198895 [= 2012-07-13])[2]	As GR_R_53_V6C with the following updates: - reading from frozen snapshot of DB accounts.
FT_R_53_V6	52X	To be used for data reprocessing. (Snapshot not valid for runs > 198895 [= 2012-07-13])[2]	As GR_R_53_V6 with the following updates: - reading from frozen snapshot of DB accounts.
GR_R_53_V6C	53X	To be used for data reprocessing of the low PU run. Special ECAL patch release required.	As GR_R_53_V6 with the following updates: - ECAL fix for low PU run.
GR_R_53_V6	53X	To be used for data reprocessing.	As GR_R_53_V5 with the following updates: - Fix for ECAL LocalContCorrParameters.
GR_R_53_V5	53X	To be used for data reprocessing.	As GR_R_53_V2D with the following updates: - new 2012 data JECs. - beamspot updated for full run range
GR_R_53_V4	>=533X	To be used for data reprocessing.	As GR_R_53_V3 with the following updates: - possibility to mask ECAL samples added.
GR_R_53_V3	53X	To be used for data reprocessing.	As GR_R_53_V2 with the following updates: - new 2012 data JECs.
GR_R_53_V2	53X	To be used for data reprocessing.	As GR_R_53_V1 with the following updates: - updated ECAL laser APD/PN - updated ES intercalibrations - new supercluster energy correction - new Ecal laser alphas.
GR_R_53_V1	53X	To be used for data reprocessing.	As GR_R_52_V7 with the following updates: - new PF cluster regression - updated ECAL local containment corrections.

Global tags for collision data reprocessing (52X)

TAGNAME	Validity	Description	Comments
GR_R_52_V10	52X	To be used for data reprocessing.	As GR_R_52_V9D with the following updates: - updated JECs for JPT (Aug 2012).
GR_R_52_V9D	52X	To be used for data reprocessing.	As GR_R_52_V9 with the following updates: - New btag and mistag Data/MC scale factors.
GR_R_52_V9B	52X	This GT is broken. Do not use it.	As GR_R_52_V9 with the following updates: - New btag and mistag Data/MC scale factors.
GR_R_52_V9	52X	To be used for data reprocessing.	As GR_R_52_V8 with the following updates: - new 2012 data JECs.
FT_R_52_V8E	52X	To be used for data reprocessing. (Snapshot not valid for runs > 197610 [= 2012-06-28])[2]	As GR_R_52_V8E with the following updates: - reading from frozen snapshot of DB accounts.
FT_R_52_V8D	52X	To be used for data reprocessing. (Snapshot not valid for runs > 197610 [= 2012-06-28])[2]	As GR_R_52_V8D with the following updates: - reading from frozen snapshot of DB accounts.
GR_R_52_V8E	52X	To be used for data reprocessing.	As GR_R_52_V8C with the following updates: - fix for problem with strips noise - strips bad channels recomputed for the new SiStripNoise_GR10_v2_offline.
GR_R_52_V8D	52X	To be used for data reprocessing.	As GR_R_52_V8B with the following updates: - fix for problem with strips noise - strips bad channels recomputed for the new SiStripNoise_GR10_v2_offline.
GR_R_52_V8C	52X	To be used for data reprocessing.	As GR_R_52_V8 with the following updates: - possibility to mask ECAL samples added - new ECAL intercalibrations.
GR_R_52_V8B	52X	To be used for data reprocessing.	As GR_R_52_V8 with the following updates: - new ECAL intercalibrations.
FT_R_52_V8A	52X	To be used for data reprocessing. (Snapshot not valid for runs > 195535 [= 2012-06-04].)[2]	As FT_R_52_V8 with the following updates: - reading from frozen snapshot of DB accounts. - Includes EcalSampleMask_offline to fix the problem with 100/pb of low PU. - Requires special release (CMSSW_5_2_5_ecalpatch1).
FT_R_52_V8	52X	To be used for data reprocessing. (Snapshot not valid for runs > 195535 [= 2012-06-04])[2]	As GR_R_52_V8 with the following updates: - reading from frozen snapshot of DB accounts.
GR_R_52_V8	52X	To be used for data reprocessing.	As GR_R_52_V7 with the following updates: - updated ECAL laser APD/PN - updated ES intercalibrations - new Ecal laser alphas.
GR_R_52_V7E	52X	To be used for data reprocessing.	As GR_R_52_V7C with the following updates: - New btag and mistag Data/MC scale factors.
GR_R_52_V7D	52X	This GT is broken. Do not use it.	As GR_R_52_V7C with the following updates: - New btag and mistag Data/MC scale factors.
GR_R_52_V7C	52X	To be used for data reprocessing.	As GR_R_52_V7 with the following updates: - new 2012 data JECs.
GR_R_52_V7	52X	To be used for data reprocessing.	As GR_R_52_V6 with the following updates: - Updated HcalRespCorrs to cover 2010 data.
GR_R_52_V6	52X	To be used for data reprocessing.	As GR_R_52_V5 with the following updates: - Updated HCAL calibrations as presented here https://indico.cern.ch/conferenceDisplay.py?confId=169549.
GR_R_52_V5	52X	To be used for data reprocessing.	As GR_R_52_V4 with the following updates: - Summer 2011 alignment (GR10_v5_offline) updated with 3 more IOVs covering pixel movements up to run 176549 (GR10_v6_offline) - Backports kinks and bows to 2010 geometry - Updated beamspot for the new alignment in the tag TrackerAlignment_GR10_v7_offline - DT t0 migration.
GR_R_52_V4	52X (Not for prod.[1])	To be used for data reprocessing.	As GR_R_52_V3 with the following updates: - new format for DT readout mapping - back to old SR tag - new strips bad channel tag, ok also for 2010.
GR_R_52_V3	52X (Not for prod.[1])	To be used for data reprocessing.	As GR_R_52_V2 with the following updates: - ECAL Selective Readout for 2012 - DT t0 migration.
GR_R_52_V2	52X	To be used for data reprocessing.	As GR_R_52_V1 with the following updates: - new Jecs for JPT - new track based muon alignment.
GR_R_52_V1	52X	To be used for data reprocessing.	As GR_R_50_V11 with the following updates: inclusion of new HF payload

Global tags for collision data reprocessing (50X)

Global tags for collision data reprocessing (44X)

Global tags for collision data reprocessing (43X)

Show... Hide

Global tags for collision data reprocessing (42X)