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 Scouting Run3 format #36840

Merged

Conversation

alintulu
Copy link
Contributor

@alintulu alintulu commented Jan 31, 2022

PR description:

  • Several features of the PF Candidate bestTrack() has been added to the class Run3ScoutingParticle. The included variables are necessary to run b-tagging with ParticleNet, and has also been identified as helpful for additional analyses groups.
  • A couple of changes to HLTScoutingPFProducer.cc to bring the overall scouting data size down. These include:
    • Reduced precision of vertex and jet quantities.
    • Configurable option (doCandIndsForJets) which dictates if the output should contain the indices of the PF constituents of the jet.
  • Reduced precision of the vertex quantities in the primary vertex producer.
  • Pt cut (default value of 0.3) for tracks in the track producer.

PR validation:

I ran scram b runtests as well as runTheMatrix. On lxplus runTheMatrix came back with 9 fails but all due to DAS_ERROR.

@alintulu
Copy link
Contributor Author

@clelange @dsperka

@cmsbuild
Copy link
Contributor

-code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36840/28030

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-36840/28031

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @alintulu (Adelina Lintuluoto) for master.

It involves the following packages:

  • DataFormats/Scouting (core)
  • HLTrigger/JetMET (hlt)
  • HLTrigger/Muon (hlt)

@Martin-Grunewald, @Dr15Jones, @smuzaffar, @makortel, @cmsbuild, @missirol can you please review it and eventually sign? Thanks.
@Fedespring, @HuguesBrun, @missirol, @silviodonato, @abbiendi, @rovere, @Martin-Grunewald, @calderona, @sscruz, @jhgoh, @CeliaFernandez, @trocino, @cericeci 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

@Martin-Grunewald
Copy link
Contributor

Martin-Grunewald commented Jan 31, 2022

Hmm, typically we do not add new V2 versions of C++ files but rather modify/evolve the existing code and files. What is the reason here?

Copy link
Contributor

@missirol missirol left a comment

Choose a reason for hiding this comment

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

Here's a first round of comments.

DataFormats/Scouting/interface/Run3ScoutingParticleV2.h Outdated Show resolved Hide resolved
DataFormats/Scouting/interface/Run3ScoutingParticleV2.h Outdated Show resolved Hide resolved
HLTrigger/JetMET/plugins/HLTScoutingPFProducerV2.cc Outdated Show resolved Hide resolved
HLTrigger/JetMET/plugins/HLTScoutingPFProducerV2.cc Outdated Show resolved Hide resolved
HLTrigger/JetMET/plugins/HLTScoutingPFProducerV2.cc Outdated Show resolved Hide resolved
HLTrigger/JetMET/plugins/HLTScoutingPFProducerV2.cc Outdated Show resolved Hide resolved
HLTrigger/JetMET/plugins/HLTScoutingPFProducerV2.cc Outdated Show resolved Hide resolved
HLTrigger/JetMET/plugins/HLTScoutingPFProducerV2.cc Outdated Show resolved Hide resolved
HLTrigger/JetMET/plugins/HLTScoutingPFProducerV2.cc Outdated Show resolved Hide resolved
HLTrigger/JetMET/plugins/HLTScoutingPFProducerV2.cc Outdated Show resolved Hide resolved
@alintulu
Copy link
Contributor Author

Hmm, typically we do not add new V2 versions of C++ files but rather modify/evolve the existing code and files. What is the reason here?

It was decided with @dsperka that keeping the old version would allow us to more easily change producers if necessary. David, maybe you would like to elaborate on this?

@Martin-Grunewald
Copy link
Contributor

Hmm, I would not want to have variants of code around, based on studies you should settle on one and refine/update that one again if needed (both producer and dataformat), esp. if one is a (almost?) superset of the other.

@cmsbuild
Copy link
Contributor

-code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36840/28038

ERROR: Build errors found during clang-tidy run.

--
HLTrigger/JetMET/plugins/HLTScoutingPFProducerV2.cc:114:97: error: use of undeclared identifier 'mantissaPrecision'; did you mean 'mantissaPrecision_'? [clang-diagnostic-error]
                                MiniFloatConverter::reduceMantissaToNbitsRounding(vtx.yError(), mantissaPrecision),
                                                                                                ^~~~~~~~~~~~~~~~~
                                                                                                mantissaPrecision_
--
HLTrigger/JetMET/plugins/HLTScoutingPFProducerV2.cc:116:95: error: use of undeclared identifier 'mantissaPrecision'; did you mean 'mantissaPrecision_'? [clang-diagnostic-error]
                                MiniFloatConverter::reduceMantissaToNbitsRounding(vtx.chi2(), mantissaPrecision),
                                                                                              ^~~~~~~~~~~~~~~~~
                                                                                              mantissaPrecision_
--
HLTrigger/JetMET/plugins/HLTScoutingPFProducerV2.cc:133:7: error: use of undeclared identifier 'doMet' [clang-diagnostic-error]
  if (doMet && iEvent.getByToken(metCollection_, metCollection)) {
      ^
HLTrigger/JetMET/plugins/HLTScoutingPFProducerV2.cc:141:7: error: use of undeclared identifier 'doCandidates' [clang-diagnostic-error]
  if (doCandidates && iEvent.getByToken(pfCandidateCollection_, pfCandidateCollection)) {
      ^
HLTrigger/JetMET/plugins/HLTScoutingPFProducerV2.cc:143:23: error: use of undeclared identifier 'pfCandidatePtCut'; did you mean 'pfCandidatePtCut_'? [clang-diagnostic-error]
      if (cand.pt() > pfCandidatePtCut && std::abs(cand.eta()) < pfCandidateEtaCut) {
                      ^~~~~~~~~~~~~~~~
                      pfCandidatePtCut_
--
gmake: *** [config/SCRAM/GMake/Makefile.coderules:129: code-checks] Error 2
gmake: *** [There are compilation/build errors. Please see the detail log above.] Error 2

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 4, 2022

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36840/28148

@missirol
Copy link
Contributor

missirol commented Feb 4, 2022

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 4, 2022

Pull request #36840 was updated. @makortel, @missirol, @Dr15Jones, @Martin-Grunewald, @smuzaffar can you please check and sign again.

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 4, 2022

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-3cb4b5/22223/summary.html
COMMIT: 752421e
CMSSW: CMSSW_12_3_X_2022-02-03-2300/slc7_amd64_gcc10
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/cmssw/36840/22223/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: 9 differences found in the comparisons
  • DQMHistoTests: Total files compared: 46
  • DQMHistoTests: Total histograms compared: 3765022
  • DQMHistoTests: Total failures: 19
  • DQMHistoTests: Total nulls: 1
  • DQMHistoTests: Total successes: 3764980
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.004 KiB( 45 files compared)
  • DQMHistoSizes: changed ( 312.0 ): 0.004 KiB MessageLogger/Warnings
  • Checked 193 log files, 42 edm output root files, 46 DQM output files
  • TriggerResults: no differences found

@makortel
Copy link
Contributor

makortel commented Feb 7, 2022

+core

@missirol
Copy link
Contributor

missirol commented Feb 7, 2022

+hlt

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 7, 2022

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 Feb 8, 2022

+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

8 participants