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

Muon POG NanoAOD v2 #43642

Merged
merged 19 commits into from
Feb 21, 2024
Merged

Muon POG NanoAOD v2 #43642

merged 19 commits into from
Feb 21, 2024

Conversation

rbhattacharya04
Copy link
Contributor

This PR adds a list of variables to the Muon collection for the custom Muon POG NanoAOD. A set of Trigger Object filterBits has also been added in a new section in Trigger Objects called "Muon POG" with Id - 1313.

This PR is opened to start the review for the approach to add the additional Trigger Object filterBits and it is not fully complete. Variables, corresponding to displaced Muon collection, will be added in later pushes.

@cmsbuild
Copy link
Contributor

cmsbuild commented Jan 1, 2024

cms-bot internal usage

@cmsbuild
Copy link
Contributor

cmsbuild commented Jan 1, 2024

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43642/38302

  • This PR adds an extra 28KB to repository

@cmsbuild
Copy link
Contributor

cmsbuild commented Jan 1, 2024

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

It involves the following packages:

  • PhysicsTools/NanoAOD (xpog)

@cmsbuild, @hqucms, @vlimant can you please review it and eventually sign? Thanks.
@AnnikaStein, @gpetruc this is something you requested to watch as well.
@antoniovilela, @rappoccio, @sextonkennedy you are the release manager for this.

cms-bot commands are listed here

@vlimant
Copy link
Contributor

vlimant commented Jan 10, 2024

as you implement new features, please remember to include this custom nano with the autoNano syntax #42238 and think about adding a test workflow in the nano matrix

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43642/38509

@cmsbuild
Copy link
Contributor

Pull request #43642 was updated. @sunilUIET, @hqucms, @AdrianoDee, @srimanob, @miquork, @cmsbuild, @vlimant, @subirsarkar can you please check and sign again.

@rbhattacharya04
Copy link
Contributor Author

I have increased the precision for the GenParticle pt, eta, phi, which are needed for the Rochester corrections. You can go forward with the merging.

@vlimant
Copy link
Contributor

vlimant commented Feb 20, 2024

please test

@cmsbuild
Copy link
Contributor

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-6b55f5/37566/summary.html
COMMIT: 1977a60
CMSSW: CMSSW_14_1_X_2024-02-19-2300/el8_amd64_gcc12
Additional Tests: NANO
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/43642/37566/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

NANO Comparison Summary

Summary:

  • You potentially added 1 lines to the logs
  • Reco comparison results: 0 differences found in the comparisons
  • DQMHistoTests: Total files compared: 15
  • DQMHistoTests: Total histograms compared: 16430
  • DQMHistoTests: Total failures: 0
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 16430
  • DQMHistoTests: Total skipped: 0
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 0.0 KiB( 14 files compared)
  • Checked 38 log files, 18 edm output root files, 15 DQM output files

Nano size comparison Summary:

  • Nano ERROR: Missing ref/2500.314-size.json
  • Nano ERROR: Missing ref/2500.314-size.json
  • Nano ERROR: Missing ref/2500.401-size.json
  • Nano ERROR: Missing ref/2500.401-size.json
    | Sample | kb/ev | ref kb/ev | diff kb/ev | ev/s/thd | ref ev/s/thd | diff rate | mem/thd | ref mem/thd |
    | --- | --- | --- | --- | --- | --- | --- | --- | --- |
    | 2500.0 | 2.551 | 2.551 | 0.000 ( +0.0% ) | 5.24 | 5.22 | +0.4% | 2.221 | 2.216 |
    | 2500.001 | 2.700 | 2.700 | 0.000 ( +0.0% ) | 4.66 | 4.69 | -0.8% | 2.650 | 2.625 |
    | 2500.002 | 2.641 | 2.641 | 0.000 ( +0.0% ) | 4.88 | 4.89 | -0.2% | 2.634 | 2.626 |
    | 2500.01 | 1.322 | 1.322 | 0.000 ( +0.0% ) | 9.51 | 9.69 | -1.8% | 2.338 | 2.270 |
    | 2500.011 | 1.745 | 1.745 | 0.000 ( +0.0% ) | 5.25 | 5.26 | -0.3% | 2.524 | 2.530 |
    | 2500.012 | 1.586 | 1.586 | 0.000 ( +0.0% ) | 7.55 | 7.51 | +0.6% | 2.441 | 2.411 |
    | 2500.1 | 2.194 | 2.194 | 0.000 ( +0.0% ) | 5.25 | 5.25 | +0.0% | 2.060 | 2.059 |
    | 2500.2 | 2.310 | 2.310 | 0.000 ( +0.0% ) | 6.00 | 6.04 | -0.7% | 1.972 | 1.973 |
    | 2500.21 | 1.185 | 1.185 | 0.000 ( +0.0% ) | 4.33 | 4.33 | -0.1% | 2.270 | 2.250 |
    | 2500.211 | 1.549 | 1.549 | 0.000 ( +0.0% ) | 3.71 | 3.76 | -1.4% | 2.357 | 2.333 |
    | 2500.3 | 2.060 | 2.060 | 0.000 ( +0.0% ) | 12.44 | 12.66 | -1.7% | 1.960 | 1.951 |
    | 2500.31 | 1.257 | 1.257 | 0.000 ( +0.0% ) | 19.21 | 20.16 | -4.7% | 2.364 | 2.349 |
    | 2500.311 | 1.646 | 1.646 | 0.000 ( +0.0% ) | 11.95 | 12.32 | -3.0% | 2.440 | 2.412 |
    | 2500.312 | 7.159 | 7.159 | 0.000 ( +0.0% ) | 1.40 | 1.39 | +1.3% | 1.684 | 1.681 |
    | 2500.313 | 1.564 | 1.564 | 0.000 ( +0.0% ) | 6.73 | 6.70 | +0.5% | 1.037 | 1.032 |
    | 2500.4 | 2.060 | 2.060 | 0.000 ( +0.0% ) | 12.30 | 12.66 | -2.8% | 1.957 | 1.954 |
    | 2500.5 | 19.575 | 19.575 | 0.000 ( +0.0% ) | 1.12 | 1.17 | -4.2% | 1.346 | 1.343 |

@vlimant
Copy link
Contributor

vlimant commented Feb 20, 2024

+1

@subirsarkar
Copy link

+Upgrade

@jordan-martins
Copy link
Contributor

Hi @cms-sw/pdmv-l2,
please review this PR and sign this -off as we want to have this to follow up the Nano v14 (as a MUO flavour, a-lá jmenano) for the DATA-taking and also for the upcoming PAG MC (all in 14_0_X and onwards). From the PPD side, this is ready to go in.
Best,
PPD

@sunilUIET
Copy link
Contributor

+pdmv

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

@rappoccio
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit 426442b into cms-sw:master Feb 21, 2024
13 checks passed
@@ -28,6 +28,8 @@ def expandNanoMapping(seqList, mapping, key):
# L1 flavours: add tables through customize, supposed to be combined with PHYS
'L1' : {'customize': 'nanoL1TrigObjCustomize'},
'L1FULL' : {'customize': 'nanoL1TrigObjCustomizeFull'},
# Muon POG flavours : add tables through customize, supposed to be combined with PHYS
'MUPOG' : {'customize' : 'PhysicsTools/NanoAOD/custom_muon_cff.PrepMuonCustomNanoAOD'},
Copy link
Contributor

Choose a reason for hiding this comment

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

Hello, I think it would have been wiser for me to spot that @PHYS should be added by default here, if you are never going to ask --step NANO:@MUPOG alone (i.e not including the @PHYS part. we might need a quick PR for this

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@vlimant we were using always --step @phys+@MUPOG even in the relval_nano.py. I can make a quick PR to change this.

Copy link
Contributor

Choose a reason for hiding this comment

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

done in #44425

Copy link
Contributor

Choose a reason for hiding this comment

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

can you please have a look at #44428 ?

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 @vlimant , I have posted a comment in #44428. The changes look fine to me. but please wait a little bit for other muon pog colleagues to confirm.

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.