feat(ALERTEngine): initialize ATOF detector and check that there are … #1054
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.
…5 interclusters for the prediction
Found a lot of text is spit out by the ALERT Engine:
INFO: [DB] ---> open 11 | default | Thu Jan 08 08:56:42 EST 2026 | mysql://clas12reader@clasdb-farm.jlab.org/clas12
Exception in ALERTEngine processDataEvent: java.lang.NullPointerException
INFO: [DB] ---> open 11 | default | Thu Jan 08 08:56:44 EST 2026 | mysql://clas12reader@clasdb-farm.jlab.org/clas12
Exception in ALERTEngine processDataEvent: java.lang.IndexOutOfBoundsException: Index 4 out of bounds for length 4
INFO: [DB] ---> open 11 | default | Thu Jan 08 08:56:45 EST 2026 | mysql://clas12reader@clasdb-farm.jlab.org/clas12
Exception in ALERTEngine processDataEvent: java.lang.NullPointerException
INFO: [DB] ---> open 11 | default | Thu Jan 08 08:56:45 EST 2026 | mysql://clas12reader@clasdb-farm.jlab.org/clas12
Exception in ALERTEngine processDataEvent: java.lang.NullPointerException
Fix that by building the ATOF detector in the init method and by checking that there are 5 interclusters in the tracks (It means 4 clusters).