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

Mask more old b-taggers for run3_common #40464

Merged
merged 1 commit into from Jan 11, 2023

Conversation

francescobrivio
Copy link
Contributor

@francescobrivio francescobrivio commented Jan 9, 2023

PR description:

This PR is part of cms-AlCaDB/AlCaTools#58 to clean-up old b-tagging tags that are deprecated for Run3 (similar to #40043) and which are giving errors in the tests of #40445 (which actually removes the b-tagging tags from the Run3 MC GTs).
Namely:

  • in SoftLeptonByMVAComputers_cff.py the useCondDB flag is set to False for Run3 so that the BDT loads the weights from the xml and not from the CondDB tag.
  • in applySubstructure_cff.py only the DeepCSV taggers are kept for patJetsAK8PFPuppiSoftDropSubjets and patJetsAK8Puppi

I'd like to ask @cms-sw/btv-pog-l2 and @AlexDeMoor (who were previously involved in the review of similar PRs) if they agree with the proposed solution, or they have a different suggestion?

FYI @cms-sw/alca-l2 @yuanchao

PR validation:

I have successfully run some of the wfs failing in #40445 (including the GTs proposed in that PR) with:
runTheMatrix.py -l 312.0,13234.0 -j9 --ibeos

Backport:

Not a backport, no backport needed

@cmsbuild
Copy link
Contributor

cmsbuild commented Jan 9, 2023

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40464/33631

  • This PR adds an extra 16KB to repository

@cmsbuild
Copy link
Contributor

cmsbuild commented Jan 9, 2023

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

It involves the following packages:

  • PhysicsTools/PatAlgos (xpog, reconstruction)
  • RecoBTag/SoftLepton (reconstruction)

@cmsbuild, @mandrenguyen, @clacaputo, @swertz, @vlimant can you please review it and eventually sign? Thanks.
@rappoccio, @gouskos, @hatakeyamak, @emilbols, @mbluj, @demuller, @seemasharmafnal, @mmarionncern, @missirol, @ahinzmann, @jdolen, @azotz, @jdamgov, @nhanvtran, @gkasieczka, @schoef, @andrzejnovak, @AlexDeMoor, @AnnikaStein, @JyothsnaKomaragiri, @gpetruc, @mariadalfonso this is something you requested to watch as well.
@perrotta, @dpiparo, @rappoccio you are the release manager for this.

cms-bot commands are listed here

@tvami
Copy link
Contributor

tvami commented Jan 9, 2023

enable nano

@tvami
Copy link
Contributor

tvami commented Jan 9, 2023

@cmsbuild , please test

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d73827/29867/summary.html
COMMIT: 11ec1a4
CMSSW: CMSSW_13_0_X_2023-01-09-1100/el8_amd64_gcc11
Additional Tests: NANO
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/40464/29867/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: 2774 differences found in the comparisons
  • DQMHistoTests: Total files compared: 49
  • DQMHistoTests: Total histograms compared: 3555538
  • DQMHistoTests: Total failures: 1219
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3554297
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 48 files compared)
  • Checked 211 log files, 162 edm output root files, 49 DQM output files
  • TriggerResults: no differences found

NANO Comparison Summary

Summary:

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

Nano size comparison Summary:

Sample kb/ev ref kb/ev diff kb/ev ev/s/thd ref ev/s/thd diff rate mem/thd ref mem/thd
2500.31 2.209 2.209 0.000 ( +0.0% ) 9.05 9.52 -4.9% 1.520 1.541
2500.311 2.329 2.329 0.000 ( +0.0% ) 8.77 9.17 -4.3% 1.890 1.850
2500.312 2.284 2.284 0.000 ( +0.0% ) 8.91 9.03 -1.3% 1.883 1.847
2500.33 1.096 1.096 0.000 ( +0.0% ) 19.38 21.63 -10.4% 1.635 1.629
2500.331 1.396 1.396 0.000 ( +0.0% ) 14.63 15.88 -7.9% 1.789 1.792
2500.332 1.328 1.328 0.000 ( +0.0% ) 16.45 17.43 -5.6% 1.743 1.731
2500.4 2.097 2.097 0.000 ( +0.0% ) 10.10 10.16 -0.5% 1.421 1.429
2500.401 2.164 2.164 0.000 ( +0.0% ) 10.04 10.26 -2.1% 1.219 1.235
2500.5 1.668 1.668 0.000 ( +0.0% ) 16.39 16.26 +0.8% 1.136 1.131
2500.501 1.729 1.729 0.000 ( +0.0% ) 16.45 16.24 +1.3% 1.141 1.138
2500.51 1.071 1.071 0.000 ( +0.0% ) 28.64 28.95 -1.1% 1.424 1.417
2500.511 1.137 1.137 0.000 ( +0.0% ) 28.58 28.30 +1.0% 1.450 1.438
2500.6 2.006 2.006 0.000 ( +0.0% ) 12.98 13.03 -0.4% 1.199 1.211
2500.601 2.076 2.076 0.000 ( +0.0% ) 12.92 12.92 +0.0% 1.208 1.215

@francescobrivio
Copy link
Contributor Author

@cms-sw/reconstruction-l2 @cms-sw/xpog-l2 @cms-sw/btv-pog-l2 could you kindly review this PR and let me know in case you have comments/suggestions?

This is currently blocking the merging of #40445 (which needs this PR), and in turn #40445 is blocking further developments of MC GTs for 2023.

Thanks a lot!

)
run3_common.toModify(softPFMuonComputer,
useCondDB = cms.bool(False),
)
Copy link
Contributor

Choose a reason for hiding this comment

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

Just a suggestion, not a strict requirement (coming from BTV Reco):
To apply these changes to all the Computers which might be called somewhere, these modifications could be extended to also touch positiveSoftPFMuonComputer,negativeSoftPFMuonComputer,positiveSoftPFElectronComputer,positiveSoftPFElectronComputer in the exact same way. All six producers here use the same PSet, so they could be changed now as well in one go to also set useCondDB = cms.bool(False), even if these additional four producers are not responsible for any errors in the tests currently.
Otherwise the changes look fine.

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 @AnnikaStein thanks for the suggestion!
Sure I can extend the change to the other producers, but I have one question:
all of them are using the same PSets (softPF[Muon|Electron]Common), so wouldn't it be easier to modify directly the "Common" PSets? Or that's too risky because the Common ones might be imported somewhere else?

Copy link
Contributor

Choose a reason for hiding this comment

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

Hi @francescobrivio
I totally agree it would be easier. My initial concern was exactly what you mentioned, with the risk that it might be imported somewhere else. But actually, using the cmssdt lxr and github search, I only found some place in HLT for Phase-2, where this PSet is defined as well, but I found no place where it gets directly imported. From that point of view, it should be safe to follow up with changing the PSet itself in another PR.

Copy link
Contributor

Choose a reason for hiding this comment

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

hi @AnnikaStein given that from that on it's less of an AlCaDB business, I'm wondering if you could submit the PR? (If yes, please also tag us, just that we can follow it was done)

Copy link
Contributor

Choose a reason for hiding this comment

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

Hi @tvami
Ok, will do!

Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks!

@tvami
Copy link
Contributor

tvami commented Jan 11, 2023

hi @cms-sw/reconstruction-l2 @cms-sw/xpog-l2 may I suggest to merge this PR as it is, and follow up with an another PR to tidy up the rest of the computer as suggested by @AnnikaStein ? My reasoning is that we actually have another GT update in the queue, after #40445 is merged (which needs this to be merged first)

@swertz
Copy link
Contributor

swertz commented Jan 11, 2023

+1

That's fine by me.

@mandrenguyen
Copy link
Contributor

type btv

@cmsbuild cmsbuild added the btv label Jan 11, 2023
@mandrenguyen
Copy link
Contributor

+reconstruction
Follow-up plan proposed by @tvami based on comments from @AnnikaStein sounds reasonable.

@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, @rappoccio (and backports should be raised in the release meeting by the corresponding L2)

@perrotta
Copy link
Contributor

+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

7 participants