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

Migration to cmssw #29

Open
rappoccio opened this issue Feb 17, 2021 · 6 comments
Open

Migration to cmssw #29

rappoccio opened this issue Feb 17, 2021 · 6 comments

Comments

@rappoccio
Copy link
Member

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:

  • FatJet: AK8 PFJets
  • FatJetPFCand : Candidates associated to FatJets
  • FatJetPFCandAssoc: Association between FatJetPFCands and FatJet.

AK8 Gen Jets:

  • GenFatJet: AK8 GenJets
  • GenFatJetCand : Candidates associated to FatJets
  • GenFatJetCandAssoc: Association between FatJetPFCands and FatJet.
@nsmith-
Copy link
Contributor

nsmith- commented Feb 17, 2021

For reference, the current names are:

AK8 Puppi Jets:

  • collection: FatJet
  • association: FatJetPFCands
  • candidates: PFCands

AK8 Gen jets:

  • collection: GenJetAK8
  • association: GenFatJetCands
  • candidates: GenCands

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.

@rappoccio
Copy link
Member Author

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.

@andrzejnovak
Copy link
Collaborator

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

@rappoccio
Copy link
Member Author

The code will already be integrated in cmssw. There's no reason this needs to be duplicated.

@andrzejnovak
Copy link
Collaborator

@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.

@rappoccio
Copy link
Member Author

There's no difference in the code for AK4 and/or AK8 or all PF cands. These are just differences in the flags.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants