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

Move to L1Nano #50

Closed
5 tasks done
artlbv opened this issue Jan 16, 2024 · 1 comment · Fixed by #65
Closed
5 tasks done

Move to L1Nano #50

artlbv opened this issue Jan 16, 2024 · 1 comment · Fixed by #65
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@artlbv
Copy link
Collaborator

artlbv commented Jan 16, 2024

We want to move from L1 menu ntuples to the nanoAOD-based menu ntuples "L1Nano":
https://github.com/cms-l1-dpg/Phase2-L1Nano

The nano contains almost all the relevant objects as in the old menu ntuples except:

In addition to the previous "L1 objects" also "GT objects" were added. a summary of the current content is shown here:
https://alobanov.web.cern.ch/L1T/Phase2/L1Nano/l1nano_doc_report.html

This branch/commit tried a first version of adapting the cache and object performance code to the L1Nano: 9a1aa4a
https://github.com/artlbv/Phase2-L1MenuTools/tree/dev_nano

Note that apart from the (branch) name changes of the L1 objects, the major change for this framework is the update of the generator-level particle collections.

Instead of storing all particles, the default, filtered, GenPart collection is used now:
https://alobanov.web.cern.ch/L1T/Phase2/L1Nano/l1nano_doc_report.html#GenPart

The migration to nano can be split in these tasks:

@artlbv
Copy link
Collaborator Author

artlbv commented Mar 13, 2024

Closed by #65

@artlbv artlbv closed this as completed Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant