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
re-check GenJet clustering for GenHFHadronMatcher #145
Comments
that's the error you get if you do not recluster or what? do you have an example producing such error to look at? |
Exactly, this is without reclustering: to reproduce, change this to "slimmedGenJets" also needs to be changed here. i'll make it configurable in a PR which fixes GenJet stuff: https://github.com/vhbb/cmssw/blob/vhbbHeppy74X/VHbbAnalysis/Heppy/python/GenHFHadronMatcher.py#L67 |
@jpata , sorry for a rather long silence from our side; we were very busy lately with many other things. The three points that you've raised as support for matching to the |
@bartonas, thanks for following up nevertheless and bringing it again to the experts. Could you point me again to the discussion about matching to |
@jpata, I was refering to your first post in this issue discussion. The hadron-matched jet flavour is the standard definition implemented in the JetFlavour tool, which is then used internally by the GenHFHadronMatcher. This is exactly what we are reproducing by reclustering jets, and running the JetFlavour code on them. Thus, jets and their flavour are in principle identical to the ones stored in miniAOD. I will perform additional checks to see how large are differences between reclustered jets and jets in miniAOD. |
@bartonaz ah OK, thanks for the clarification. If the re-clustered jets are identical, then this matching is only for our convenience not to store gen-jets twice and still keep the original miniAOD definition of genjets. In short I'd simply like to fix what will be the GenHFHadronMatcher recipe: re-clustered jets or not, but I suppose we are still waiting for feedback from the experts. |
OK, so from what I understand we will need to re-cluster and we are safe in matching original slimmedGenJets to reclustered until cms-sw#11081 is merged. @arizzi: do you prefer to pull this into vhbb/cmssw or go with re-clustering? Below a mail from @bartonaz describing the situation. Thanks all.
|
I'd say to fix the hadron flavour importing the 11081 so that we run faster (one clustering step less). |
OK, I'll make a single PR containing the isAvailable fix and updated vhbb-side hadron matching/gen-jet code against vhbb today. |
making an issue so I know to solve GenJet stuff from #67 which is closed.
from Andrea:
those are the open points in my view:
we should not remake the gen jets as they should be the same but I understand that for the hadron matching this could be actually needed? can you confirm?
in output we should have a single gen jet having all needed features, namely:
the standard flavour coming from PAT
the hadron matched flavour
the genNu correction
if hadron matcher needs to remake its own jets, then we have to back match those to the original collection and just set a had-flavour attribute
With spring15, the genjets still need to be re-clustered. As far as I know, the original authors (Johannes Hauk, @bartonaz) are taking a look since June.
This is the error we get halfway through the processing.
The text was updated successfully, but these errors were encountered: