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
crash in MergedGenParticleProducer #82
Comments
the issue is here: then it crashes somewhere in produce() of |
it looks like the sample has a fancy particle listing with only a few particles and perhaps some assumptions of the GenParticles2HepMCConverter do not hold. @perrozzi |
I can confirm, fixing the problem in MergedGenParticleProducer (see below) leads to a crash in this line of GenParticles2HepMCConverter: HepMC::GenVertex* vertex1 = new HepMC::GenVertex(FourVector(parton1->vertex())); Using John's latest patch (cms-sw#21349) does not solve the problem. Does this sample even have incoming protons stored?? @jhgoh Do you have any idea? This is the input file: |
Yes I can reproduce crash even after applying PR21349.
I guess releasing eta cut will fix the problem. let me try. |
OK, two separate problems as pointed by @arizzi
Since the PR is not closed yet, I can apply changes above if this is reasonable. |
Hi John, thanks a lot! + if ( pk.mother(0) == nullptr ) return false; I think this will miss out on orphaned photons where no mother information is stored. Please see mseidel42@b49a38c for my solution. |
can you guys push the fixes in cms-sw/cmssw both for master and 94X branches? |
@intrepid42 I can cherry-pick this one, if it is not already in the master branch. |
Yes, please, I made the patch this morning :) |
we have a crash here:
#5 0x00007f6d6c89183a in MergedGenParticleProducer::isPhotonFromPrunedHadron(pat::PackedGenParticle const&) const () from /cvmfs/cms.cern.ch/slc6_amd64_gcc630/cms/cmssw/CMSSW_9_4_0/lib/slc6_amd64_gcc630/pluginGeneratorInterfaceRivetInterface_plugins.so
you can reproduce with (on lxplus) ~arizzi/public/test92X_NANO.py on 940 release + nanoaod master branch
@intrepid42
The text was updated successfully, but these errors were encountered: