-
Notifications
You must be signed in to change notification settings - Fork 19
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
MarlinProcessorWrapper loops extra event with EvtMax=-1 in ApplicationMgr #208
Comments
I thought we had fixed this already. See #154 |
#154 is empty and says it is a duplicate of #94. It also mentioned that key4hep/k4FWCore#125 is potentially related that was fixed in key4hep/k4FWCore#132. But if I understand correctly, it just changes the return code of the program. But we obviously do not count events properly... This is still here. |
The underlying problem in this case is that there is no real way here to stop at the "end of an event", we can only schedule a stop during the event to stop after the current event. It should be possible to schedule the stop at the right event to make this appear as if it has stopped after the event. |
Ah sorry, I had an impression yesterday that it missed one event because of this error. |
Issue
Running Gaudi over all events with
EvtMax=-1
(the default from the documentation) tries to run one extra event withMarlinProcessprWrapper
. Running withEvtMax=manually_set_max_events
works without errors.Reproducible
Running the default reconstruction test from ILDConfig
with
Relevant output in the end:
Expected result should be exactly as
Running the default reconstruction test from ILDConfig
with
The same output now:
Environment
Note
The EDM4HEP root file is still produced, but one (I guess the last) event is empty.
Seems like an off-by-one error and
MarlinProcessprWrapper
counts from 1 in this particular case.This also may arise from the difference between Marlin and Gaudi:
In Gaudi all events is set by
EvtMax=-1
In Marlin all events is set by
MaxRecordNumber = 0
The text was updated successfully, but these errors were encountered: