-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HCAL 2017 Phase1 Workflows #15889
HCAL 2017 Phase1 Workflows #15889
Changes from all commits
a4e6c05
bf5f1f2
4eb39a0
0afa935
bfe444b
ff46989
61abaf5
e3418e2
909daed
1046942
256242e
8393d1a
68b20fd
7fadf6c
b1543bb
a14deaa
833fe0e
21e6fec
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
import FWCore.ParameterSet.Config as cms | ||
|
||
from Configuration.Eras.Era_Run2_2017_cff import Run2_2017 | ||
from Configuration.Eras.Modifier_run2_HF_2017_cff import run2_HF_2017 | ||
from Configuration.Eras.Modifier_run2_HCAL_2017_cff import run2_HCAL_2017 | ||
|
||
Run2_2017_HCALdev = cms.ModifierChain(Run2_2017, run2_HF_2017, run2_HCAL_2017) | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
import FWCore.ParameterSet.Config as cms | ||
|
||
from Configuration.Eras.Era_Run2_2017_cff import Run2_2017 | ||
from Configuration.Eras.Modifier_phase1PixelNewFPix_cff import phase1PixelNewFPix | ||
from Configuration.Eras.Modifier_run2_HF_2017_cff import run2_HF_2017 | ||
from Configuration.Eras.Modifier_run2_HCAL_2017_cff import run2_HCAL_2017 | ||
|
||
Run2_2017_new = cms.ModifierChain(Run2_2017, phase1PixelNewFPix, run2_HF_2017, run2_HCAL_2017) | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
import FWCore.ParameterSet.Config as cms | ||
|
||
# This modifier should be used for "common" HCAL 2017 customizations | ||
# Initially, this means the packer and DQM | ||
# subdetector-specific changes for sim, reco, etc. should go in run2_HE_2017 or run2_HF_2017 | ||
|
||
run2_HCAL_2017 = cms.Modifier() | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,6 @@ | ||
import FWCore.ParameterSet.Config as cms | ||
|
||
# This modifier is for HE-specific changes for sim, reco, etc. | ||
|
||
run2_HE_2017 = cms.Modifier() | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
import FWCore.ParameterSet.Config as cms | ||
|
||
# This modifier is for HF-specific changes for sim, reco, etc. | ||
|
||
run2_HF_2017 = cms.Modifier() | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
import FWCore.ParameterSet.Config as cms | ||
|
||
# Ideal geometry, needed for transient ECAL alignement | ||
from Configuration.Geometry.GeometryExtended2017new_cff import * | ||
|
||
|
||
# Reconstruction geometry services | ||
# Tracking Geometry | ||
#bah - well, this is not a cfi! | ||
from Geometry.CommonDetUnit.globalTrackingGeometry_cfi import * | ||
|
||
#Tracker | ||
from RecoTracker.GeometryESProducer.TrackerRecoGeometryESProducer_cfi import * | ||
from Geometry.TrackerNumberingBuilder.trackerTopology_cfi import * | ||
|
||
#Muon | ||
from Geometry.MuonNumbering.muonNumberingInitialization_cfi import * | ||
from RecoMuon.DetLayers.muonDetLayerGeometry_cfi import * | ||
|
||
# Alignment | ||
from Geometry.TrackerGeometryBuilder.idealForDigiTrackerGeometry_cff import * | ||
from Geometry.CSCGeometryBuilder.idealForDigiCscGeometry_cff import * | ||
from Geometry.DTGeometryBuilder.idealForDigiDtGeometry_cff import * | ||
trackerGeometry.applyAlignment = False | ||
|
||
# Calorimeters | ||
from Geometry.CaloEventSetup.CaloTopology_cfi import * | ||
from Geometry.CaloEventSetup.CaloGeometry_cff import * | ||
from Geometry.CaloEventSetup.EcalTrigTowerConstituents_cfi import * | ||
from Geometry.EcalMapping.EcalMapping_cfi import * | ||
from Geometry.EcalMapping.EcalMappingRecord_cfi import * | ||
from Geometry.HcalCommonData.hcalDDDRecConstants_cfi import * | ||
from Geometry.HcalEventSetup.hcalTopologyIdeal_cfi import * |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,11 @@ | ||
import FWCore.ParameterSet.Config as cms | ||
|
||
# | ||
# Geometry master configuration | ||
# | ||
# Ideal geometry, needed for simulation | ||
from Geometry.CMSCommonData.cmsExtendedGeometry2017newXML_cfi import * | ||
from Geometry.TrackerNumberingBuilder.trackerNumberingGeometry_cfi import * | ||
from Geometry.HcalCommonData.hcalParameters_cfi import * | ||
from Geometry.HcalCommonData.hcalDDDSimConstants_cfi import * | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,7 +7,9 @@ | |
upgradeKeys[2017] = [ | ||
'2017', | ||
'2017PU', | ||
'2017NewFPix' | ||
'2017NewFPix', | ||
'2017HCALdev', | ||
'2017AllNew', | ||
] | ||
|
||
upgradeKeys[2023] = [ | ||
|
@@ -66,7 +68,19 @@ | |
'GT' : 'auto:phase1_2017_realistic', | ||
'Era' : 'Run2_2017_NewFPix', | ||
'ScenToRun' : ['GenSimFull','DigiFull','RecoFull','HARVESTFull'], | ||
}, | ||
}, | ||
'2017HCALdev' : { | ||
'Geom' : 'Extended2017dev', | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'll change it back when #15924 is merged |
||
'GT' : 'auto:phase1_2017_hcaldev', | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I presume this will switch pixel geometry (well, everything) to be read from XML. In which pre-release is this PR planned to be integrated? (pre12, pre13; or will the geometry be included in a GT before the pre-release?) I'm wondering a possible interference with #15883 and #15805 (or actually with their validation). There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, this sounds like it could cause great chaos if it gets into pre12. And for pre13/the release, I have the feeling that nothing called 'dev' should be in the then-production workflows. It seems to me that There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Note that #15674 changed There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The 2017dev geometry itself does not need validation, but it can only be used (for DIGI-RECO) with an appropriate global tag having HCAL conditions for all the new channels. As we just got one, it could not have been used in the workflow until now. @ianna doesn't have the latest version of it in the database yet, so I assigned the xml version for now. This shouldn't "interfere" with the new pixel geometry PRs, as those are creating a separate workflow for validation. @davidlange6 requested that I not make yet another separate workflow for HCAL 2017. At some point, all of these geometry changes need to be reconciled into one final 2017 geometry, but I think that should be done after or otherwise outside of this PR. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I had the impression that the goal of pre13 was to "merge" the "2017_NewFPix" workflow introduced in #15805 back to the "2017" workflow. Personally I don't have a problem in keeping it around if needed for other reasons, just all cleanup needs to be done in there (although maybe not much can be done before the "2017" and "2017_NewFPix" get really merged?). For my education, are the additions in There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
This is not strictly correct, the new WFs exist to evaluate the new FPIX individually. There are aso BPIX changes that need validation in the normal 2017 geometry. However, these are not as drastic as the FPIX changes and might be fine to coexist with the HCAL changes. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
It is not just the BPix changes we need to validate with pre12, but also all non-geometry changes between pre11 and pre12 (e.g. turning off VPF30 mitigation), and that is best done with exactly the same geometry as in pre11. Now, trying to be practical (probably along what @slava77 already wrote), as these two parameters are passed to cmsDriver they can be changed at the time of RelVal submission (to be coordinated with PdmV; by the way, if this PR goes in pre12, do you want RelVals with the So my only concern is the effect of the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nominally, undoing a change implemented with an era, should be another era, If I understand correctly, changes made by HCAL eras in this PR will not work on the old 2016 HCAL geometry. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @slava77 - yes, HCal and CaloTower reco geometries produced from a 2017dev scenario differ from the ones produced from a 2017 scenario. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @makortel the changes from the new HCAL geometry, tag, and customizations definitely are not statistically insignificant. You cannot use the new HCAL tag with pre11 GEN-SIM. I first suggested making a separate testing workflow and Era for the HCAL changes, but @davidlange6 did not want me to do this. At this point, he should comment if he would accept this PR with such a (temporary) new workflow and Era before I make those changes. |
||
'Era' : 'Run2_2017_HCALdev', | ||
'ScenToRun' : ['GenSimFull','DigiFull','RecoFull','HARVESTFull'], | ||
}, | ||
'2017AllNew' : { | ||
'Geom' : 'Extended2017new', | ||
'GT' : 'auto:phase1_2017_hcaldev', | ||
'Era' : 'Run2_2017_new', | ||
'ScenToRun' : ['GenSimFull','DigiFull','RecoFull','HARVESTFull'], | ||
}, | ||
} | ||
|
||
upgradeProperties[2017]['2017PU'] = deepcopy(upgradeProperties[2017]['2017']) | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,25 @@ | ||
import FWCore.ParameterSet.Config as cms | ||
|
||
hcalRawData = cms.EDProducer("HcalDigiToRaw", | ||
|
||
hcalRawDataVME = cms.EDProducer("HcalDigiToRaw", | ||
HBHE = cms.untracked.InputTag("simHcalDigis"), | ||
HF = cms.untracked.InputTag("simHcalDigis"), | ||
HO = cms.untracked.InputTag("simHcalDigis"), | ||
ZDC = cms.untracked.InputTag("simHcalUnsuppressedDigis"), | ||
TRIG = cms.untracked.InputTag("simHcalTriggerPrimitiveDigis") | ||
) | ||
|
||
hcalRawData = cms.Sequence(hcalRawDataVME) | ||
|
||
from EventFilter.HcalRawToDigi.hcalDigiToRawuHTR_cfi import hcalDigiToRawuHTR as hcalRawDatauHTR | ||
|
||
_phase1_hcalRawData = hcalRawData.copy() | ||
_phase1_hcalRawData += hcalRawDatauHTR | ||
|
||
from Configuration.StandardSequences.Eras import eras | ||
eras.run2_HCAL_2017.toModify( hcalRawDataVME, | ||
HBHE = cms.untracked.InputTag(""), | ||
HF = cms.untracked.InputTag(""), | ||
TRIG = cms.untracked.InputTag("") | ||
) | ||
eras.run2_HCAL_2017.toReplaceWith(hcalRawData,_phase1_hcalRawData) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some comments may be useful to clarify what's supposed to go in with this era,
as well as what other era has to be enabled at the same time.