Skip to content
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

Make sure that reading of LCIO events stops early enough #210

Merged
merged 6 commits into from
Dec 16, 2024

Conversation

tmadlener
Copy link
Contributor

@tmadlener tmadlener commented Dec 10, 2024

BEGINRELEASENOTES

  • Stop the reading of the LCIO events early enough, such that no empty event is processed after the last event (which breaks "regular" Algorithms in the same chain)
  • Make it a hard error (exception) when reading an event fails
  • Add documentation about the small conceptual differences that might lead to unexpected results

ENDRELEASENOTES

This is iteration N of fixing #208

Some more things to consider in this whole thing:

  • marlin::SkipEventException will most likely lead to problems if the chain has non wrapped algorithms
    • Gaudi technically has a similar thing with revoverable exceptions, but I am not entirely sure if it still works
  • The LCEventStatusWrapper should probably renamed now that it is completely decoupled from the LCIO Event status.

tmadlener and others added 5 commits December 15, 2024 21:00
Effectively stop the run when processing the last event even if it is at
the beginning of the event loop. Also make it throw a proper exception
to immediately abort when the reading fails.
Co-authored-by: Mateusz Jakub Fila <[email protected]>
@tmadlener tmadlener merged commit 880b57a into main Dec 16, 2024
11 checks passed
@tmadlener tmadlener deleted the stop-right-event branch December 16, 2024 13:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

MarlinProcessorWrapper loops extra event with EvtMax=-1 in ApplicationMgr
2 participants