-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Plugin to obtain the best track index for Run3ScoutingElectron #47726
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
Plugin to obtain the best track index for Run3ScoutingElectron #47726
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-47726/44295
|
A new Pull Request was created by @arsahasransu for master. It involves the following packages:
@cmsbuild, @ftorrresd, @hqucms can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Note contributions by @patinkaew . @elfontan @donated The PR for the Run3ScoutingElectronBestTrackProducer is now created for NanoAOD. Tagging to follow. |
I also believe Scouting needs to be added to monitor the code in the package PhysicsTools/Scouting. |
what does this mean?
Is there a way to test it directly from the PR? Is this going to run in any central nano sequence only at a later time? |
Basically, I meant that the scouting convenors should get a notice when the code in the repo PhysicsTools/Scouting changes so that they can review and are aware of the change. I also do not know the formalism. I was merely speculating.
So, a command |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-47726/44315 |
Pull request #47726 was updated. @cmsbuild, @ftorrresd, @hqucms can you please check and sign again. |
that's possible. https://github.com/cms-sw/cms-bot/blob/1774727cfa2c5040288ddb3bf2657d91fa6823e7/groups.yaml and then add to that category the packages of interest as it's done for example for that way all the people in the
if all it needs is to run a |
Hi Marco, Thank you for pointing out the instruction to create |
Hi @arsahasransu, all, I was checking this with 2022-24 data and the plugin crashes for 2023 because I'm not sure what is the best solution for this. For ScoutingNano, we can have era modifier so we only output these for 2024 and afterwards. So we only need to make sure the plugin doesn't crash. A Hi @hqucms @ftorrresd, we will eventually put this in ScoutingNano. The |
enable nano |
is this producer meant to run in the HLT only. |
this is definitely NOT meant to run in the HLT. |
please test |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-47726/44458 |
Pull request #47726 was updated. @cmsbuild, @ftorrresd, @hqucms can you please check and sign again. |
@cmsbuild, please test |
+1 Size: This PR adds an extra 24KB to repository Comparison SummarySummary:
NANO Comparison SummarySummary:
Nano size comparison Summary:
|
Unit test worked, see log. |
@cms-sw/xpog-l2 I think all fixes suggested by Marco have been implemented (thanks Marco) |
+1 |
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. @sextonkennedy, @mandrenguyen, @rappoccio, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
The new plugin returns the best track index and other associated variables as value maps for use in NanoAOD creation for HLTSCOUT dataset. Discussed extensively in Scouting meeting. Relevant slides are linked below.
Also includes a test functionality in the test directory to manually verify the sensibility of the code output.
PR validation: