AHDC helix fitter printing error

[N-Plx]

The AHDC service prints an error whenever there are not enough point for the helix track fitter:

https://github.com/JeffersonLab/coatjava/blob/f772c46c36298c85246c30528f7bda11da2b[…]lert/src/main/java/org/jlab/rec/ahdc/HelixFit/HelixFitJava.java

This has been a problem cooking data, creating very heavy log files that fill up the log directory for some runs where this was printed every event.

A temporary solution could be to simply remove printing that line.

But it also needs to be checked why there are no good event, and how to deal with them. And if it is worth cooking with the AHDC service, if other information from the track finding or KF can be still looked at.

@ftouchte @mathieuouillon Do you have insights please?

[ftouchte]

It is true that we have a lot of bad events. Preventing them will same a lot of computed time and resources. I need to look deeply in the code. @RDupre

[N-Plx]

@efuchey

[efuchey]

if there are too many hits, The conventional track finder seems to be used:
https://github.com/efuchey/coatjava/blob/development/reconstruction/alert/src/main/java/org/jlab/service/ahdc/AHDCEngine.java#L177
That means there might not be a problem on AI track finder, but the fact we use the conventional track finder means we need to give it a bit of attention