Nearest neighbor handling

[robin4730]

Add Nearest Neighbor handling to Energy Calibration and TAC

Remove MModuleNearestNeighbor from GUI and execution flow

• Disables MModuleNearestNeighbor in the main Nuclearizer GUI and removes
  associated actions. Nearest Neighbors will now be processed through the
  standard strip dataflow with module-specific handling, rather than
  relying on this standalone module.
• Note: Source files are retained for now but should be deleted in a future cleanup.

Add option to include/exclude Nearest Neighbors in HDF Loader

• Updates MModuleLoaderMeasurementsHDF with a toggle to filter Nearest
  Neighbor hits.
• Default: Include Nearest Neighbors (true).

Implement configurable energy thresholds for Nearest Neighbors

Updates MModuleEnergyCalibrationUniversal to allow specific cuts on
Nearest Neighbor hits. Users can now select between:

• No cut
• A flat lower-bound threshold (user-defined in keV)

Add Nearest Neighbor timing cuts to MModuleTACcut

Extends TAC module to process Nearest Neighbor hits.

• Implements a specific timing cut: Nearest Neighbors with calibrated timing <= 200ns (like in the python tools)

[zoglauer]

Is there anything left to protect against negative values if we neither do slow nor next neighbor cuts?

[robin4730]

No there is nothing left to protect against negative energy. I just didn't think we wanted to automatically remove negative energy values, especially for the nearest neighbors. But if negative energy breaks other modules then I will add the "if Energy < 0, Energy gets set to 0" safeguard back in.

[zoglauer]

What happens if we have Ignore?

[robin4730]

My answer to this changes based on if we can or can't have negative nearest neighbor values

[zoglauer]

Does is compile for you?

I get:
dyld[97705]: symbol not found in flat namespace '__ZN29MModuleLoaderMeasurementsFITS11m_BatchSizeE'
zsh: abort nuclearizer

[robin4730]

I can compile and run nuclearizer from this commit without issues. Gemini says that the issue is that m_BatchSize in src/MModuleLoaderMeasurementsFITS.cxx doesn't have memory allocated for it? It says to add:

#ifdef ___CLING___
ClassImp(MModuleLoaderMeasurementsFITS)
#endif

// Initialize the static variable
int MModuleLoaderMeasurementsFITS::m_BatchSize = 1000; // <--- FIX IS HERE: Add this line!

But I didn't change this file at all so not really sure...?

[zoglauer]

That should not be a static variable...
I'll fix that.

[zoglauer]

Fixed it in the develop/em branch

[zoglauer]

Let me know when I can merge it.

[robin4730]

Hi Andreas, I think this is ready to merge? Or, let me know if there are any other issues to fix.

[zoglauer]

Can you fix the above mentioned conflicts? Or below...