Make ConformalTracking to behave less diruptively on encountering too many tracks #62
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before this, ConformalTracking would throw a SkipEventException resulting in further Marlin processors down the line to not be executed. However, when using Marlin processors from Gaudi with the k4MarlinWrapper, the expected behaviour of a failing processors is to (optionally warn and) emit its usual output collections. Otherwise PodioOutput crashes in the end...
BEGINRELEASENOTES
ENDRELEASENOTES
I tested the changes locally and they solved key4hep/k4MarlinWrapper#158 for me. The track pulss also did not change more than they do from run to run anyway so I hope I did not break anything.