Upgrade Geometry Scenarios

Contacts

• Conveners: Ianna Osborne (FNAL)
• Hypernews forum: https://hypernews.cern.ch/HyperNews/CMS/get/geometry.html

2023 geometry scenarios

Functional workflow means, that a job runs without crashes on cmsDriver produced configuration with --geometry option. Everything is in 62X_SLHC IB or in a queue unless mentioned otherwise.

Extended2023

"Baseline" geometry scenario. Full SIM-DIGI-RECO workflow is functional. Replacement for Phase 1 Hcal will be done as soon as one of the Phase II calorimeters is ready. There is no space for ME0 with current Hcal.

• 2019 detector
• BE5D tracker
• GE1/1
• GE2/1
• RE3/1 and RE4/1 (extended to 2.4, 192 strips)

Extended2023Pixel

This scenario is the same as Extended2023 + Extended Pixel.

• 2019 detector
• BE5D tracker
• ExtendedPixel
• HCAL Phase 1 (4 eta coverage)
• GE1/1
• GE2/1
• RE3/1 and RE4/1 (extended to 2.4, 192 strips)

Extended2023TTI

Note: no ME0

• 2019 detector
• HCAL Phase 0
• BE5D tracker
• ExtendedPixel
• GE1/1
• GE2/1
• RE3/1 and RE4/1 (extended to 2.4, 192 strips)

Extended2023Muon

• 2019 detector
• EE (reduced)
• HCAL Phase 2 (3 eta coverage)
• BE5D tracker
• ExtendedPixel
• ME0
• GE1/1
• GE2/1
• RE3/1 and RE4/1 (extended to 2.4, 192 strips)

Extended2023Muon4Eta

• 2019 detector
• EE (reduced)
• HCAL Phase 2 (4 eta coverage)
• BE5D tracker
• ExtendedPixel
• ME0
• GE1/1
• GE2/1
• RE3/1 and RE4/1 (extended to 2.4, 192 strips)

Extended2023HGCal

• 2019 detector
• BE5D tracker
• ExtendedPixel
• HGCal (no ES, EE nor HE)
• GE1/1
• GE2/1
• RE3/1 and RE4/1 (extended to 2.4, 192 strips)

Extended2023HGCalMuon

Note: no HGCal_GEM and ME0 is in its place.

• 2019 detector
• BE5D tracker
• ExtendedPixel
• HGCal (no ES nor EE nor HE) concept geometry without HE_GEM (3 eta coverage)
• ME0
• GE1/1
• GE2/1
• RE3/1 and RE4/1 (extended to 2.4, 192 strips)

Extended2023HGCalMuon4Eta

Note: no HGCal_GEM and ME0 is in its place.

• 2019 detector
• BE5D tracker
• ExtendedPixel
• HGCal (no ES nor EE nor HE) concept geometry without HE_GEM (4 eta coverage)
• ME0
• GE1/1
• GE2/1
• RE3/1 and RE4/1 (extended to 2.4, 192 strips)

Extended2023SHCal

• 2019 detector
• BE5D tracker
• ExtendedPixel
• Shashlik extended to 3 Eta coverage
• Phase II HE (no ES nor EE ) extended to 3 Eta coverage
• ME0
• GE1/1
• GE2/1
• RE3/1 and RE4/1 (extended to 2.4, 192 strips)

Extended2023SHCal4Eta

• 2019 detector
• BE5D tracker
• Extended pixel (up to eta 4)
• Shashlik extended to 4 Eta coverage
• Phase II HE (no ES nor EE ) extended to 4 Eta coverage
• ME0
• GE1/1
• GE2/1
• RE3/1 and RE4/1 (extended to 2.4, 192 strips)

ExtendedGeometry2023SHCalNoTaper

• 2019 detector
• BE5D tracker
• ExtendedPixel
• Shashlik no taper geometry extended to 3 Eta coverage
• Phase II HE (no ES nor EE ) extended to 3 Eta coverage
• ME0
• GE1/1
• GE2/1
• RE3/1 and RE4/1 (extended to 2.4, 192 strips)

ExtendedGeometry2023SHCalNoTaper4Eta

• 2019 detector
• BE5D tracker
• Extended pixel (up to eta 4)
• Shashlik no taper geometry extended to 4 Eta coverage
• Phase II HE (no ES nor EE ) extended to 4 Eta coverage
• ME0
• GE1/1
• GE2/1
• RE3/1 and RE4/1 (extended to 2.4, 192 strips)

Extended2023CFCal

• 2019 detector
• BE5D tracker
• CFCal
• ME0 (?)
• GE1/1
• GE2/1
• RE3/1 and RE4/1 (extended to 2.4, 192 strips)

Extended2023CFCal4Eta

• 2019 detector
• BE5D tracker
• Extended pixel (up to eta 4)
• CFCal - 4 Eta coverage
• ME0 (?)
• GE1/1
• GE2/1
• RE3/1 and RE4/1 (extended to 2.4, 192 strips)

ExtendedPhase2TkBE5DPixel10D

• 2019 detector
• BE5D tracker
• Extended pixel (up to eta 4)

TODO:

• Extended2023 with new description of RE2/1, RE3/1 and RE4/1 (all extended to 2.4), without GE2/1, but with GE1/1

Status of runTheMatrix workflows

Known failures

12200, 14200 & 14400 (Extended2023HGCalMuon, Extended2023HGCal & Extended2023HGCalMuon4Eta) in step 3:

cmsRun: <build area>/src/RecoEgamma/EgammaIsolationAlgos/src/EgammaRecHitIsolation.cc:64: EgammaRecHitIsolation::EgammaRecHitIsolation(double, double, double, double, double, edm::ESHandle<CaloGeometry>, CaloRecHitMetaCollectionV*, const EcalSeverityLevelAlgo*, DetId::Detector): Assertion `subdet_[1]!=__null' failed.

12600 (Extended2023SHCal4Eta) in step 2:

%MSG-e HGCalGeom:  MixingModule:mix 23-May-2014 14:13:26 CEST Run: 1 Event: 1
ShashlikGeometry::getGeometry-> inconsistent geometry structure 1008759920(32874->1006686810) inside: (EK iz -  fiber 0, RO 0, ix 210, iy 90)(1006686810->32874) given: (EK iz +  fiber 0, RO 0, ix 116, iy 112)(1008759920) ref (EK iz -  fiber 0, RO 0, ix 210, iy 90)
%MSG
cmsRun: <build area>/src/SimCalorimetry/EcalSimAlgos/src/EcalHitResponse.cc:283: double EcalHitResponse::timeOfFlight(const DetId&) const: Assertion `0 != cellGeometry' failed.

13200 & 13400 (Extended2023CFCal & Extended2023CFCal4Eta) in step 2:

----- Begin Fatal Exception 04-Apr-2014 20:57:50 CEST-----------------------
An exception of category 'NoRecordFromDependentRecord' occurred while
   [0] Processing run: 1
   [1] Running path 'digitisation_step'
   [2] Calling beginRun for module MixingModule/'mix'
   [3] Using EventSetup component CaloGeometryBuilder/'' to make data CaloGeometry/'' in record CaloGeometryRecord
   [4] Using EventSetup component HcalHardcodeGeometryEP/'' to make data CaloSubdetectorGeometry/'HCAL' in record HcalGeometryRecord
   [5] Using EventSetup component HcalRecNumberingInitialization/'' to make data HcalDDDRecConstants/'' in record HcalRecNumberingRecord
Exception Message:
No "HcalSimNumberingRecord" record found in the dependent record "HcalRecNumberingRecord".
 Please add an ESSource or ESProducer that delivers the "HcalSimNumberingRecord" record.
----- End Fatal Exception -------------------------------------------------

-- IannaOsborne - 08 Jan 2014