Skip to content
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

Configurable hardcode conditions for HCAL #13861

Merged
merged 9 commits into from Apr 13, 2016

Conversation

kpedro88
Copy link
Contributor

This PR modifies HcalHardcodeConditions and HcalDbHardcode to make basic parameters configurable using Python. This change is intended to aid reconstruction development for the 2017 HF and HE upgrades, respectively: dual anode readout with QIE10 and SiPMs with QIE11 and increased depth segmentation.

NB: Nothing should change in existing workflows, because the hardcode conditions are only used for development.

Elements of this PR:

  1. New class HcalHardcodeParameters (modeled after HcalSimParameters), currently contains pedestal, pedestal width, gain, gain width, QIE type, QIE offsets (range 0-3), QIE slopes (range 0-3)
  2. HcalDbHardcode now a class (instead of a namespace)
  3. Fixed any HcalDbHardcode dependencies accordingly (or removed unnecessary includes, in one case deleted an unused piece of code after discussion on HCAL CMSSW hypernews)
  4. Hcal_Conditions_forGlobalTag_cff has PSets for:HB, HE, HF, HO, HB upgrade, HE upgrade, HF upgrade
  5. Each subdetector can be set to Run1 or upgrade independently (testHFQIE10 “mixed case” still available)
  6. Run1 parameters based on dump of DB conditions from 7_6_3 (GT auto:run2_mc) + HcalQIEData_NormalMode_v7.05_mc for QIEData (newer tag)
  7. SiPM lumi offset and pedestal width lumi dependence parameters also now configurable (may be supplanted by new noise & raddam models in the future)
  8. Added a customization function customise_HcalPhase0p5 ("Phase 0.5"). Currently this enables QIE10 digitization for all HF cells, but keeps Run1 conditions for HE (SiPM + QIE11 not ready yet).

I've tested the 2017 mode in CMSSW_8_1_X_2016-03-29-2300 with customise_HcalPhase0p5 and the Extended2017dev geometry, which has HF depths 3/4 and HE depths up to 7. I used the following script:

#!/bin/bash

 cmsDriver.py SinglePiE50HCAL_pythia8_cfi  --conditions auto:phase1_2017_design -n 10 --era Run2_2017 --geometry "Configuration.Geometry.GeometryExtended2017dev_cff,Configuration.Geometry.GeometryExtended2017devReco_cff" --eventcontent FEVTDEBUG -s GEN,SIM --datatier GEN-SIM --beamspot Realistic50ns13TeVCollision --fileout file:step1.root --customise SLHCUpgradeSimulations/Configuration/HCalCustoms.customise_HcalPhase0p5 > step1_SinglePiE50_UP15+SinglePiE50_UP15+DIGIUP15+RECOUP15+HARVESTUP15.log  2>&1


 cmsDriver.py step2  --conditions auto:phase1_2017_design -s DIGI:pdigi_valid,L1,DIGI2RAW,HLT:@relval25ns --datatier GEN-SIM-DIGI-RAW-HLTDEBUG -n 10 --era Run2_2017 --geometry "Configuration.Geometry.GeometryExtended2017dev_cff,Configuration.Geometry.GeometryExtended2017devReco_cff" --eventcontent FEVTDEBUGHLT --filein file:step1.root  --fileout file:step2.root --customise SLHCUpgradeSimulations/Configuration/HCalCustoms.customise_HcalPhase0p5 > step2_SinglePiE50_UP15+SinglePiE50_UP15+DIGIUP15+RECOUP15+HARVESTUP15.log  2>&1


 cmsDriver.py step3  --runUnscheduled  --conditions auto:phase1_2017_design -s RAW2DIGI,L1Reco,RECO,EI,PAT --datatier GEN-SIM-RECO,MINIAODSIM -n 10 --era Run2_2017 --geometry "Configuration.Geometry.GeometryExtended2017dev_cff,Configuration.Geometry.GeometryExtended2017devReco_cff" --eventcontent RECOSIM,MINIAODSIM --filein file:step2.root  --fileout file:step3.root --customise SLHCUpgradeSimulations/Configuration/HCalCustoms.customise_HcalPhase0p5 > step3_SinglePiE50_UP15+SinglePiE50_UP15+DIGIUP15+RECOUP15+HARVESTUP15.log  2>&1


 cmsDriver.py step4  --runUnscheduled  --conditions auto:phase1_2017_design -s VALIDATION:@standardValidation+@miniAODValidation,DQM:@standardDQM+@miniAODDQM --datatier GEN-SIM-RECO,MINIAODSIM,DQMIO -n 10 --era Run2_2017 --geometry "Configuration.Geometry.GeometryExtended2017dev_cff,Configuration.Geometry.GeometryExtended2017devReco_cff" --eventcontent RECOSIM,MINIAODSIM,DQM --filein file:step3.root  --fileout file:step4.root --customise SLHCUpgradeSimulations/Configuration/HCalCustoms.customise_HcalPhase0p5 > step4_SinglePiE50_UP15+SinglePiE50_UP15+DIGIUP15+RECOUP15+HARVESTUP15.log  2>&1

The DIGI and RECO steps both actually succeed, though with some errors that need to be resolved. Validation/DQM fail, which is why I moved them to a separate step.

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @kpedro88 (Kevin Pedro) for CMSSW_8_1_X.

It involves the following packages:

CalibCalorimetry/HcalAlgos
CalibCalorimetry/HcalPlugins
CondTools/Hcal
IORawData/CaloPatterns
OnlineDB/HcalCondDB
SLHCUpgradeSimulations/Configuration
SimCalorimetry/HcalSimAlgos

The following packages do not have a category, yet:

OnlineDB/HcalCondDB

@civanch, @cerminar, @cmsbuild, @franzoni, @mdhildreth, @ggovi, @mmusich, @davidlange6 can you please review it and eventually sign? Thanks.
@makortel, @Martin-Grunewald, @apfeiffer1, @tocheng this is something you requested to watch as well.
@slava77, @Degano, @smuzaffar you are the release manager for this.

cms-bot commands are list here #13028

@mmusich
Copy link
Contributor

mmusich commented Mar 30, 2016

please test

@cmsbuild
Copy link
Contributor

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/12095/console

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

@kpedro88
Copy link
Contributor Author

@mmusich @ggovi @civanch - The comparison looks good to me. Again, no changes expected in standard workflows. Nevertheless, there should probably be some code review, since this is a moderately large change, even though it's only used for testing new features.

@davidlange6 - OnlineDB/HcalCondDB should probably be added to the 'db' category...

@kpedro88
Copy link
Contributor Author

NB: I just updated the 2017 dev testing recipe in the PR message so that the RECO step can actually run.

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 1, 2016

Pull request #13861 was updated. @civanch, @cerminar, @cmsbuild, @franzoni, @mdhildreth, @ggovi, @mmusich, @davidlange6 can you please check and sign again.

@kpedro88
Copy link
Contributor Author

kpedro88 commented Apr 1, 2016

Added a commit to remove DIGI2RAW and RAW2DIGI for HCAL in the Phase0p5 customization. This is necessary to get the new depths in HE to show up in RecHits. Otherwise, they get discarded in some step of the packing and unpacking. We're looking into what's needed to make the full chain work (probably FED lists, etc.); in the meantime, this solution was used for the UpgradeDataFrames in the past.

@civanch
Copy link
Contributor

civanch commented Apr 2, 2016

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 2, 2016

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/12142/console

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

@kpedro88
Copy link
Contributor Author

Comparison still looks fine. Rebase just had to include the technical change auto_ptr -> unique_ptr from #13999.

@civanch @ggovi @mmusich can you sign again?

@kpedro88
Copy link
Contributor Author

@civanch @ggovi @mmusich @davidlange6 - please sign and merge ASAP as discussed in ORP this morning...

@mmusich
Copy link
Contributor

mmusich commented Apr 13, 2016

+1

@abdoulline
Copy link

@civanch
@ggovi

please, approve.

@civanch
Copy link
Contributor

civanch commented Apr 13, 2016

+1

@ggovi
Copy link
Contributor

ggovi commented Apr 13, 2016

+1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next CMSSW_8_1_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar

@davidlange6
Copy link
Contributor

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants