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

Update the ADC->fC table, simplify the charge reconstruction algorith… #22974

Merged
merged 8 commits into from May 26, 2018
Merged

Update the ADC->fC table, simplify the charge reconstruction algorith… #22974

merged 8 commits into from May 26, 2018

Conversation

jkunkle
Copy link

@jkunkle jkunkle commented Apr 16, 2018

Updates to enable the HCAL laser monitoring. With this change, I take the opportunity to make a simplification of the code which performs the laser monitoring charge reconstruction. We have implemented the lasermon system in firmware rather than hardware. This means that we can remove the complicated matching algorithm because the firmware guarantees fixed latency between channels (the hardware implementation did not). The relevant changes are,

  • RecoMET/METProducers/src/HcalNoiseInfoProducer.cc : Update the adc->fC table to use qie10 ADCs
  • RecoMET/METProducers/src/HcalNoiseInfoProducer.cc : Update the reconstruction algorithm to simply take the first N samples of each channel where N is a new configurable parameter, laserMonitorSamples_.
  • RecoMET/METProducers/src/HcalNoiseInfoProducer.cc : Integrate the charge using a simple peak finding algorithm rather than integrating the whole readout
    -RecoMET/METFilters/plugins/HcalLaserEventFilter.cc - enable the laser filtering and update the threshold to 5000

The above changes have been tested with a recent global run for consistency against the old method and that the changes propagate to the Met filter

@deguio @mariadalfonso

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

-code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-22974/4357

Code check has found code style and quality issues which could be resolved by applying a patch in https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-22974/4357/git-diff.patch
e.g. curl https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-22974/4357/git-diff.patch | patch -p1

You can run scram build code-checks to apply code checks directly

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @jkunkle for master.

It involves the following packages:

RecoMET/METFilters
RecoMET/METProducers

@perrotta, @monttj, @cmsbuild, @slava77, @gpetruc, @arizzi can you please review it and eventually sign? Thanks.
@TaiSakuma, @gouskos, @ahinzmann, @mmarionncern, @jdamgov, @jdolen, @nhanvtran, @gkasieczka, @schoef, @mariadalfonso, @seemasharmafnal this is something you requested to watch as well.
@davidlange6, @slava77, @fabiocos you are the release manager for this.

cms-bot commands are listed here

7272,7597,7922,8247,8572,8897,9222,9547,10197,10847,11497,12147,
12797,13447,14097,15072,16047,17022,17997,19297,20597,21897,23522,25147};
//adc2fCHF = std::vector<float> {-3,-0.4,2.2,4.8,7.4,10,12.6,15.2,17.8,20.4,23,25.6,28.2,30.8,33.4,
// 36,41.2,46.4,51.6,56.8,62,67.2,73,80.8,88.6,96.4,104,114.4,124.8,135,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this commented out code needed?
Please remove or add comments inline in the code why the commented out block is relevant

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Indeed, I neglected to remove it. I've pushed the change

@slava77
Copy link
Contributor

slava77 commented Apr 16, 2018

@cmsbuild please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Apr 16, 2018

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/27508/console Started: 2018/04/16 15:32

@cmsbuild
Copy link
Contributor

The code-checks are being triggered in jenkins.

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Pull request #22974 was updated. @perrotta, @monttj, @cmsbuild, @slava77, @gpetruc, @arizzi can you please check and sign again.

@jkunkle
Copy link
Author

jkunkle commented May 23, 2018

I made the suggested code update. The testing prescription is not working just because the CMSSW version is outdated, I repeat the instructions below with updated CMSSW version

cmsrel CMSSW_10_2_X_2018-05-22-2300
cd CMSSW_10_2_X_2018-05-22-2300/src
cmsenv
git cms-merge-topic 22974
cp -r /afs/cern.ch/user/j/jkunkle//public/HcalLaserCodeTest2/* .
scram b -j4
cmsDriver.py step1 --conditions 101X_dataRun2_Prompt_v9 -s RAW2DIGI,RECO --data --era Run2_2018 --eventcontent RECO,AOD --datatier RECO,AOD --filein root://eoscms.cern.ch//eos/cms/store/data/Commissioning2018/MinimumBias/RAW/v1/000/311/869/00000/5EA73380-B727-E811-9B25-FA163E9BBEF9.root  -n 100   --customise Configuration/DataProcessing/RecoTLR.customisePostEra_Run2_2018 
cmsDriver.py step2 --filein file:step1_RAW2DIGI_RECO.root  --data --eventcontent MINIAOD --runUnscheduled --datatier MINIAOD --conditions 101X_dataRun2_Prompt_v9  --step PAT   --era Run2_2018 -n 100
cmsRun config_test.py 

@perrotta
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented May 23, 2018

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/28144/console Started: 2018/05/23 22:06

@perrotta
Copy link
Contributor

@jkunkle : in your recipe, how can a 10_1_X GT work in 10_2_X ?

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

Comparison job queued.

@cmsbuild
Copy link
Contributor

Comparison is ready
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-22974/28144/summary.html

Comparison Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 31
  • DQMHistoTests: Total histograms compared: 2901712
  • DQMHistoTests: Total failures: 2
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 2901520
  • DQMHistoTests: Total skipped: 190
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 30 files compared)
  • Checked 128 log files, 14 edm output root files, 31 DQM output files

@perrotta
Copy link
Contributor

Evidently you never tried the recipe in #22974 (comment), which is rather disappointing because I am supposed to have more interesting things to do rather than debugging your private test code.
However, after the following changes in the test script/recipe:

  • Correct GT for 102X
  • Fix the "trackeness" of the parameter vetoByLaserMonitor in your config_test.py
  • Correctly renamed the source file in your config_test.py
    I managed to run it and I can get the expected results: that's good!

While running that test, in the reco step I repeatedly get the following warnings in outputs (e.g.):

Begin processing the 3rd record. Run 311869, Event 1469500, LumiSection 72 on stream 0 at 24-May-2018 10:44:11.806 CEST
%MSG-w NoModule:   ByClusterSummaryMultiplicityPairEventFilter:toomanystripclus53X  24-May-2018 10:44:11 CEST Run: 311869 Event: 1469500
No information for requested module 5. Please check in the Provinence Infomation for proper modules.
%MSG
%MSG-w NoModule:   ByClusterSummaryMultiplicityPairEventFilter:toomanystripclus53X  24-May-2018 10:44:11 CEST Run: 311869 Event: 1469500
No information for requested module 0. Please check in the Provinence Infomation for proper modules.
%MSG

They may be originated by the filter code (not necessarily from these latest updates: but you have some related flag in your test, even if the warning itself comes from the Tracker ClusterSummary [1]), and they could become rather annoying if and when it will be switched on. But maybe they just derive from a loose threshold for warnings which was set in your test.
In any case, please have a look and verify whether those warnings are indeed justified, and whether they do point to any fix needed in the filter code or config.

[1] http://cmslxr.fnal.gov/source/DataFormats/TrackerCommon/src/ClusterSummary.cc#0047

@jkunkle
Copy link
Author

jkunkle commented May 24, 2018

I certainly tried the the testing procedure that I gave, and it produces the expected results as-is. If you observed some failure in the procedure that I gave (which I did not see, since it worked for me) then it would be good to know what that is. Otherwise it is up to you if you want to make unneeded changes to the testing procedure.

I used the GT that was consistent with the conditions used when the data sample was recorded. It is never clear to me what the 'correct' prescription for applying the GT is (if you know of some clear prescription please let me know), but I kept the GT associated to the conditions of that run.

I don't see any need to change the trackedness of the configuration for the test, and I don't see any problem with the source file name, again, it works for me as-is.

The warnings that you see are not related to this PR. This can be checked by simply not merging this pull request and running the cmsDriver commands. My aim was to run the 'nominal' data processing chain by using the cmsDriver commands. Perhaps I'm not running the exact correct cmsDriver command which exposes these warnings.

@perrotta
Copy link
Contributor

+1

  • Enable the HCAL laser monitoring (plus some tuning of the laser MET filter, and some code cleaning)
  • It potentially affects real data runs with HCAL laser on
  • No effect is visible on usual MC and data workflows, but the expected behavior had been confirmed while running it on commissioning data taken with the laser firing

@fabiocos
Copy link
Contributor

+1

@fabiocos
Copy link
Contributor

merge

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

5 participants