You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the LcioEventAlgo does not handle the following two cases gracefully:
Specifying to run over a number of events in the options file (or via --num-events) that is larger than the number of events in the input file.
Specifying to run over all events via --num-events=-1 (or EvtMax = -1 in the options file)
The underlying reason for both problems is probably the same. When the input file is exhausted LcioEventAlgo::execute returns StatusCode::FAILURE but the event processing will continue. Since the LcioEventAlgo didn't register an LCEvent with the event service the MarlinProcessorWrapper will create a new but empty LCEvent and register that with the event service. That empty event will then break at some point in the chain of wrapped Marlin processors, where the first processor does not gracefully handle missing collections in the event.
The text was updated successfully, but these errors were encountered:
Currently the
LcioEventAlgo
does not handle the following two cases gracefully:--num-events
) that is larger than the number of events in the input file.--num-events=-1
(orEvtMax = -1
in the options file)The underlying reason for both problems is probably the same. When the input file is exhausted
LcioEventAlgo::execute
returnsStatusCode::FAILURE
but the event processing will continue. Since theLcioEventAlgo
didn't register anLCEvent
with the event service theMarlinProcessorWrapper
will create a new but emptyLCEvent
and register that with the event service. That empty event will then break at some point in the chain of wrapped Marlin processors, where the first processor does not gracefully handle missing collections in the event.The text was updated successfully, but these errors were encountered: