-
Notifications
You must be signed in to change notification settings - Fork 126
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
Add a Schema for Scouting NanoAOD #1148
Comments
This sounds great! Indeed you have the correct approach in mind. For reference, you can look at PFNanoAODSchema, coffea/src/coffea/nanoevents/schemas/nanoaod.py Lines 336 to 355 in cb7c9ee
which also introduces a few new mixin class types. |
This reminds me I should push an L1NanoAOD schema for Phase 2... Edit: Here's the relevant L1Nano for Phase II (which should eventually go into cmssw...) |
Thanks, I wrote the basic Schema and made a draft pull request. |
For the scouting data sets in CMS, there are several fields with unique names. "ScoutingJet", "ScoutingElectron", so on and so forth. If you use NanoAODSchema to open these files, these objects won't be recognized as four vectors and won't have the nice methods like DeltaR and what not.
I suggest that there should be a Schema for these Scouting data sets. At first it would be pretty simple to just have these fields inherit from there non scouting counter-parts, but if the scouting people want to add custom functionality to these fields it would then be pretty easy.
A proposed solution would look something like this:
This is something I am interested in writing myself. I was hoping for feedback on if this is the correct approach and if this dataset warrants its own schema.
The text was updated successfully, but these errors were encountered: