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

Introduce L1TMuonBarrelKalmanParams and Record #34494

Merged
merged 10 commits into from
Jul 28, 2021

Conversation

panoskatsoulis
Copy link
Contributor

@panoskatsoulis panoskatsoulis commented Jul 14, 2021

  • Description
    This PR introduces new Records and Objects required for implementing a primary "configuration from CondDB" for the L1 Kalman Barrel Emulator. There will be a follow up with the second part of development but this is the bare minimum for testing during the upcoming CRAFT and MWGRs.
    The object L1TMuonBarrelKalmanParams holds some (not all yet) of the parameters required by the emulator.
    (a static version of these params can be found here [1])
    To be discussed during [2]

  • Validation
    This code is validated locally, wrote and read to a local sqlite file

  • No Backport Needed

[1] https://github.com/cms-sw/cmssw/blob/master/L1Trigger/L1TMuonBarrel/python/simKBmtfDigis_cfi.py
[2] https://indico.cern.ch/event/1060075/#11-introduce-l1tmuonbarrelkalm

@cmsbuild cmsbuild changed the base branch from CMSSW_12_0_X to master July 14, 2021 22:55
@cmsbuild
Copy link
Contributor

@panoskatsoulis, CMSSW_12_0_X branch is closed for direct updates. cms-bot is going to move this PR to master branch.
In future, please use cmssw master branch to submit your changes.

@cmsbuild
Copy link
Contributor

-code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-34494/23966

  • This PR adds an extra 60KB to repository

Code check has found code style and quality issues which could be resolved by applying following patch(s)

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-34494/23967

  • This PR adds an extra 60KB to repository

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @panoskatsoulis (Panos) for master.

It involves the following packages:

  • CondCore/L1TPlugins (db, l1)
  • CondFormats/DataRecord (db, alca)
  • CondFormats/L1TObjects (l1, db, alca)
  • L1Trigger/L1TMuonBarrel (l1)
  • L1TriggerConfig/Utilities (l1)

@malbouis, @yuanchao, @cmsbuild, @rekovic, @tlampen, @ggovi, @pohsun, @francescobrivio, @cecilecaillol, @tvami can you please review it and eventually sign? Thanks.
@tocheng, @Martin-Grunewald, @thomreis, @dinyar, @mmusich, @seemasharmafnal this is something you requested to watch as well.
@silviodonato, @dpiparo, @qliphy, @perrotta you are the release manager for this.

cms-bot commands are listed here

@panoskatsoulis
Copy link
Contributor Author

panoskatsoulis commented Jul 14, 2021

@rekovic this PR is moved to master (but still under the 12_0_X milestone) since "CMSSW_12_0_X branch is closed for direct updates" as the bot mentions above.
I don't know if it's a problem given that it's targeting the prereleases of CMSSW 12

@perrotta
Copy link
Contributor

please test

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-cbd22a/16838/summary.html
COMMIT: a1e3263
CMSSW: CMSSW_12_0_X_2021-07-14-1100/slc7_amd64_gcc900
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/34494/16838/install.sh to create a dev area with all the needed externals and cmssw changes.

CMS StaticAnalyzer warnings: There are 4 EventSetupRecord::get warnings. See https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-cbd22a/16838/llvm-analysis/esrget-sa.txt for details.
CMS StaticAnalyzer warnings: There are 2 inherits from legacy modules warnings. See https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-cbd22a/16838/llvm-analysis/legacy-mod-sa.txt for details.

Comparison Summary

Summary:

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

@tvami
Copy link
Contributor

tvami commented Jul 27, 2021

@cmsbuild , please test

@tvami
Copy link
Contributor

tvami commented Jul 27, 2021

unhold

Only Francesco can do that :) (and the release managers)

@panoskatsoulis
Copy link
Contributor Author

unhold

Only Francesco can do that :) (and the release managers)

didn't know, thx

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-cbd22a/17275/summary.html
COMMIT: 18bc00e
CMSSW: CMSSW_12_0_X_2021-07-27-1100/slc7_amd64_gcc900
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/34494/17275/install.sh to create a dev area with all the needed externals and cmssw changes.

CMS StaticAnalyzer warnings: There are 4 EventSetupRecord::get warnings. See https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-cbd22a/17275/llvm-analysis/esrget-sa.txt for details.
CMS StaticAnalyzer warnings: There are 2 inherits from legacy modules warnings. See https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-cbd22a/17275/llvm-analysis/legacy-mod-sa.txt for details.

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: 2998564
  • DQMHistoTests: Total failures: 3672
  • DQMHistoTests: Total nulls: 19
  • DQMHistoTests: Total successes: 2994851
  • 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

@francescobrivio
Copy link
Contributor

unhold

@cmsbuild cmsbuild removed the hold label Jul 28, 2021
@francescobrivio
Copy link
Contributor

+alca

  • differences are due to different files in step1 of wf 140.53

@cecilecaillol
Copy link
Contributor

+l1

@ggovi
Copy link
Contributor

ggovi commented Jul 28, 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. @silviodonato, @dpiparo, @qliphy, @perrotta (and backports should be raised in the release meeting by the corresponding L2)

auto pnodes = ptr->pnodes_[ptr->CONFIG];
cout << "version : " << ptr->version_ << endl;
cout << "fwVersion : " << hex << pnodes.fwVersion_ << dec << endl;
cout << "LUTsPath : " << pnodes.kalmanLUTsPath_ << endl;
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hi, thanks for the notice about this
This module here is an L1T private tester and is not used in any central CMSSW workflow.
The purpose is to read 1 event (only) and print out the info included in the db Rcd
However, if it's required we can update it with MesageLogger in the next iteration of this development, is this fine?

Copy link
Contributor

Choose a reason for hiding this comment

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

@panoskatsoulis For the next iteration: if it is a private test, it shoud be better moved into the \test area?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hi @perrotta, this is a good point
it is the entire pkg L1TriggerConfig/Utilities that contains these testing modules
Let me discuss this with the other L1 guys tho, thx

@panoskatsoulis
Copy link
Contributor Author

About these warnings,
I have put a comment above [1] and we keep in mind to apply patches in the next PR about this development.
Again these are about code that is not included in central WFs and if possible we would like to proceed with this PR for now and will fix them.

[1] #34494 (comment)

@qliphy
Copy link
Contributor

qliphy commented Jul 28, 2021

ok, thanks @panoskatsoulis

@qliphy
Copy link
Contributor

qliphy commented Jul 28, 2021

+1

@cmsbuild cmsbuild merged commit bec73cc into cms-sw:master Jul 28, 2021
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

10 participants