-
Notifications
You must be signed in to change notification settings - Fork 54
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
Migration to cmssw #29
Comments
For reference, the current names are: AK8 Puppi Jets:
AK8 Gen jets:
I assume XPOG are ok with the redundancy of the associations and candidates branches? Since in principle here we do not need the separate association since the candidates are only belonging to the FatJet collections. Of course for the JME extended nano it is necessary to store both AK4 and AK8. |
I think it's still useful because they are still open to including the btag information, which is extra. |
Since the merge won't include ak4 jets which is bulk of what btv is interested in, this repo isn't going anywhere. We can switch the naming here, but it should stay 1 to 1 |
The code will already be integrated in cmssw. There's no reason this needs to be duplicated. |
@rappoccio so just so I understand the flags/producers for ak4 will be available in cmssw, and the AK8 only will be produced centrally then? If so that's perfect. |
There's no difference in the code for AK4 and/or AK8 or all PF cands. These are just differences in the flags. |
The XPOG conveners are now in favor of integrating into CMSSW to include the AK8 candidates in the default nano. Since this will be the primary use case, we propose the following naming:
AK8 PF Jets:
AK8 Gen Jets:
The text was updated successfully, but these errors were encountered: