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

Configure HCAL FIR Filter Based on HcalTPChannelParameters #35222

Merged
merged 6 commits into from
Sep 28, 2021

Conversation

JHiltbrand
Copy link
Contributor

PR description:

The enabling of a new FIR filter for HCAL trigger primitive reconstruction (#31661) is now done via the use of HcalTPChannelParameters conditions. Here, TT channels are used (specifically the value of their auxi1 parameter, the weight for the filter) to determine if the FIR filter should be used in HB and/or HE. The absence of TT channels in the HcalTPChannelParameters conditions OR a value of -1.0 for the auxi1 field is interpreted as to NOT use the new filter. These changes will mirror logic in online software that is used to determine if HCAL backend electronics should be configured to use the new FIR filter, thus giving equivalent behavior online and offline.

PR validation:

By default, with no changes made to the HcalTPChannelParameters, the default algorithm is used and no changes in trigger primitives are expected.

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 9, 2021

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35222/25174

  • This PR adds an extra 24KB to repository

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 9, 2021

A new Pull Request was created by @JHiltbrand (Joshua Hiltbrand) for master.

It involves the following packages:

  • CalibCalorimetry/HcalTPGAlgos (l1, alca)
  • SimCalorimetry/HcalTrigPrimProducers (l1)

@malbouis, @yuanchao, @cmsbuild, @rekovic, @francescobrivio, @cecilecaillol, @tvami can you please review it and eventually sign? Thanks.
@bsunanda, @mmusich, @abdoulline, @rovere, @tocheng this is something you requested to watch as well.
@perrotta, @dpiparo, @qliphy you are the release manager for this.

cms-bot commands are listed here

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 9, 2021

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35222/25175

  • This PR adds an extra 24KB to repository

@tvami
Copy link
Contributor

tvami commented Sep 9, 2021

@cmsbuild , please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 9, 2021

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-be0582/18470/summary.html
COMMIT: 317da9f
CMSSW: CMSSW_12_1_X_2021-09-09-1100/slc7_amd64_gcc900
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/35222/18470/install.sh to create a dev area with all the needed externals and cmssw changes.

The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:

You can see more details here:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-be0582/18470/git-recent-commits.json
https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-be0582/18470/git-merge-result

Comparison Summary

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 39
  • DQMHistoTests: Total histograms compared: 3001001
  • DQMHistoTests: Total failures: 40
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3000939
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 38 files compared)
  • Checked 165 log files, 37 edm output root files, 39 DQM output files
  • TriggerResults: no differences found

@tvami
Copy link
Contributor

tvami commented Sep 10, 2021

By default, with no changes made to the HcalTPChannelParameters, the default algorithm is used and no changes in trigger primitives are expected.

Quite a lot of changes in HcalDigisV, for example:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_12_1_X_2021-09-09-1100+be0582/45343/23234.0_TTbar_14TeV+2026D49+TTbar_14TeV_TuneCP5_GenSimHLBeamSpot14+DigiTrigger+RecoGlobal+HARVESTGlobal/HcalDigisV_HcalDigiTask.html

From the quote above I understand that this is not expected, @JHiltbrand please comment

@JHiltbrand
Copy link
Contributor Author

By default, with no changes made to the HcalTPChannelParameters, the default algorithm is used and no changes in trigger primitives are expected.

Quite a lot of changes in HcalDigisV, for example:
https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_12_1_X_2021-09-09-1100+be0582/45343/23234.0_TTbar_14TeV+2026D49+TTbar_14TeV_TuneCP5_GenSimHLBeamSpot14+DigiTrigger+RecoGlobal+HARVESTGlobal/HcalDigisV_HcalDigiTask.html

From the quote above I understand that this is not expected, @JHiltbrand please comment

Hi @tvami,
Interesting, I will take a closer look.

@abdoulline
Copy link

abdoulline commented Sep 10, 2021

@JHiltbrand
TP changes occured only Phase2 (2026) wfs
https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_12_1_X_2021-09-09-1100+be0582/45343/dqm-histo-comparison-summary.html

Where we have hardcoded conditions. Please, look back to the second footnote in my e-mail of August 27.
I suppose that in this case HcalTPChannelParameters record is produced for all cells (including HT channels)...
A quick and dirty fix would be to explictly skip HT channels ( if DetId is TriggerTowerId, then continue ...) from the loop
https://cmssdt.cern.ch/lxr/source/CalibCalorimetry/HcalPlugins/src/HcalHardcodeCalibrations.cc#0829
Could you check it (that no any change would then happen to TPs) with wf 34634.0 ?

And when we'll come to PFA1' for Phase2 (we're not there yet, right? - just considering solely Run3 ) we'll revert it in hardcoded conditions, unless we'll move to DB conditions for Phase2 by then...

@JHiltbrand
Copy link
Contributor Author

Hello @abdoulline ,

Thank you for this, I will look into the hardcoded conditions to see that I can get no changes in the output for this Phase2 wf.

@abdoulline
Copy link

abdoulline commented Sep 14, 2021

Changes may come from added #35081
Its validation (DQM bin-by-bin) pattern
https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_12_1_X_2021-09-06-2300+4104ab/45267/dqm-histo-comparison-summary.html
is very much the same as what we see for this PR.

@tvami
Copy link
Contributor

tvami commented Sep 14, 2021

@cmsbuild , please test

  • ok let's see if we get clean comparison results now...

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-be0582/18602/summary.html
COMMIT: db116a2
CMSSW: CMSSW_12_1_X_2021-09-13-2300/slc7_amd64_gcc900
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/35222/18602/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

The workflows 140.53 have different files in step1_dasquery.log than the ones found in the baseline. You may want to check and retrigger the tests if necessary. You can check it in the "files" directory in the results of the comparisons

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 1299 differences found in the comparisons
  • DQMHistoTests: Total files compared: 39
  • DQMHistoTests: Total histograms compared: 3001001
  • DQMHistoTests: Total failures: 3671
  • DQMHistoTests: Total nulls: 19
  • DQMHistoTests: Total successes: 2997289
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: -45.703 KiB( 38 files compared)
  • DQMHistoSizes: changed ( 140.53 ): -44.531 KiB Hcal/DigiRunHarvesting
  • DQMHistoSizes: changed ( 140.53 ): -1.172 KiB RPC/DCSInfo
  • Checked 165 log files, 37 edm output root files, 39 DQM output files
  • TriggerResults: no differences found

@tvami
Copy link
Contributor

tvami commented Sep 14, 2021

Ok great, now only 140.53 fails, that's expected due to "The workflows 140.53 have different files in step1_dasquery.log than the ones found in the baseline"

@tvami
Copy link
Contributor

tvami commented Sep 14, 2021

+alca

@rekovic
Copy link
Contributor

rekovic commented Sep 27, 2021

+1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2)

@qliphy
Copy link
Contributor

qliphy commented Sep 28, 2021

please test

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-be0582/19156/summary.html
COMMIT: db116a2
CMSSW: CMSSW_12_1_X_2021-09-27-2300/slc7_amd64_gcc900
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/35222/19156/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 40
  • DQMHistoTests: Total histograms compared: 3211080
  • DQMHistoTests: Total failures: 0
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3211058
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 39 files compared)
  • Checked 169 log files, 37 edm output root files, 40 DQM output files
  • TriggerResults: no differences found

@qliphy
Copy link
Contributor

qliphy commented Sep 28, 2021

+1

@cmsbuild cmsbuild merged commit f35c82c into cms-sw:master Sep 28, 2021
@JHiltbrand JHiltbrand deleted the handleFIRfilterCond branch September 13, 2023 20:37
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

6 participants