-
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
utilities for HGCAL end of life #30697
Changes from 10 commits
e6682da
31ae3a4
e965d54
c30129d
2a9ea4c
696f958
88b86a1
8e2a45d
92964ef
8aead95
846f094
3ea431a
a22c7f7
b43af76
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 |
---|---|---|
|
@@ -71,6 +71,8 @@ HGCSiNoiseMapAnalyzer::HGCSiNoiseMapAnalyzer(const edm::ParameterSet &iConfig) { | |
//configure the dose map | ||
std::string doseMapURL(iConfig.getParameter<std::string>("doseMap")); | ||
unsigned int doseMapAlgo(iConfig.getParameter<unsigned int>("doseMapAlgo")); | ||
double scaleByDoseFactor = | ||
iConfig.getParameter<edm::ParameterSet>("noise_fC").getParameter<double>("scaleByDoseFactor"); | ||
std::vector<double> ileakParam( | ||
iConfig.getParameter<edm::ParameterSet>("ileakParam").template getParameter<std::vector<double>>("ileakParam")); | ||
std::vector<double> cceParamFine( | ||
|
@@ -82,11 +84,15 @@ HGCSiNoiseMapAnalyzer::HGCSiNoiseMapAnalyzer(const edm::ParameterSet &iConfig) { | |
|
||
noiseMaps_[DetId::HGCalEE] = std::unique_ptr<HGCalSiNoiseMap>(new HGCalSiNoiseMap); | ||
noiseMaps_[DetId::HGCalEE]->setDoseMap(doseMapURL, doseMapAlgo); | ||
noiseMaps_[DetId::HGCalEE]->setDoseMap(doseMapURL, doseMapAlgo); | ||
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. Duplicate line 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. Thanks will address once back to a better keyboard 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. done. |
||
noiseMaps_[DetId::HGCalEE]->setFluenceScaleFactor(scaleByDoseFactor); | ||
|
||
noiseMaps_[DetId::HGCalEE]->setIleakParam(ileakParam); | ||
noiseMaps_[DetId::HGCalEE]->setCceParam(cceParamFine, cceParamThin, cceParamThick); | ||
|
||
noiseMaps_[DetId::HGCalHSi] = std::unique_ptr<HGCalSiNoiseMap>(new HGCalSiNoiseMap); | ||
noiseMaps_[DetId::HGCalHSi]->setDoseMap(doseMapURL, doseMapAlgo); | ||
noiseMaps_[DetId::HGCalHSi]->setFluenceScaleFactor(scaleByDoseFactor); | ||
noiseMaps_[DetId::HGCalHSi]->setIleakParam(ileakParam); | ||
noiseMaps_[DetId::HGCalHSi]->setCceParam(cceParamFine, cceParamThin, cceParamThick); | ||
|
||
|
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.
Could you please remind me why all these parameters are defined inside a Reco producer, but they are only read and used in Simulation?
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.
Ciao @perrotta valid and good question.
The cluster algorithms import, by deliberate choice, parameters from the digitisation psets to access info like noise etc, and to ensure they use values consistent with those employed upstream. Together with parameters actually employed, the descriptor of the clustering producers end up having to include also values which are not employed actually.
I don't particularly like this set up however I would not plan to re-engineer this aspect of the clustering and if these lines are not added redo crashes lamenting the producer is provided an invalid parameter.
I hope I am clear and accurate enough.
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.
I think the problem is not related to the underlying mechanism of validating the input parameters but to the way in which parameters used for reconstruction and simulation have been bundled together in the same PSet. Once you've made this choice, anything else is just a mere consequence of that.