Closed nachogargar closed 7 years ago
Could you copy/paste/upload your steering file to https://gist.github.com/ And point us to the input lcio files please
1) The parsing of boolean values given as strings ("true"
/"false"
) doesn't work. LCFIPlus will always set the value to false
. That is why the crash happens if you have the parameter in the steering file, if the parameter doesn't exist it is using the default, which is true.
2) I think the "PrimaryVertex" collection is empty when your crash happens, so this tries to access some memory it shouldn't, https://github.com/lcfiplus/LCFIPlus/blob/master/src/process.cc#L161 Not sure if getPrimaryVertex returns a nullptr or getPrimaryVertex itself does something illegal.
If BeamspotContraint is on a Vertex will be created in any case (https://github.com/lcfiplus/LCFIPlus/blob/master/src/VertexFinderTearDown.cc#L48 here?) and the crash is avoided. This would also explain why things are worse for bb events as it is more likely to have no tracks from the primary vertex.
Thanks for the comments.
Please find below the link to my steering file https://gist.github.com/nachogargar/71c442d267ee22f6a86d993c39206e5c
I additionally uploaded some examples lcio files with bb events to /afs/cern.ch/user/i/iggarcia/public
What is the ExpandJetProcessor
?
It is a private processor that creates a collection of PFOs from the output jet collection of FastJetProcessor
(which runs just before in the steering file).
The code can be found here https://gist.github.com/nachogargar/7b6c912b44dab0d250d226f7d94f8b58
It would be better if you can provide a steering file that doesn't need additional processors to reproduce the problem.
I have just commented the private processor and I made the properly changes, please check a new version of the steering file on: https://gist.github.com/nachogargar/71c442d267ee22f6a86d993c39206e5c
When the parameter BeamspotConstraint defined in "VertexFinderSuehara" is set (true or false doesn't matter), LCFIPlus crashes after processing N events (being N a random number)
<parameter name="PrimaryVertexFinder.BeamspotConstraint" type="bool" value="false" />
with the following backtrace:
This issue mostly happens when bb events are processed, partially for cc events and rarely for qq events.
Anyone else has experimented that?
Same problem with BeamspotSmearing parameter:
<parameter name="PrimaryVertexFinder.BeamspotSmearing" type="bool" value=“true" />
Thanks in advance!