Added missing bracket

[DaGeibl]

Hi, I noticed that something strange was happening with the LQ processor. I noticed that the dirft time correction property function got broken during Florians debugging. Previoues to this PR the lq_ctc_correction() function expected the ctc_driftime_expression to have brackets. I now changed this so that the function also returns the correct property function if ctc_driftime_expression does not have explicitly brackets.

@theHenks I also noticed that during your debugging you encountered some problems with my plots. This happened because the the wrong ctc correction broke them. With this fix they all work again as intended and it would suggest to include the lq_cut plot again as it is currently commented out. Except you had another reason the remove it from the lq processors

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 28.52%. Comparing base (2ba3dd2) to head (a83d3f2).
Report is 8 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #126   +/-   ##
=======================================
  Coverage   28.52%   28.52%           
=======================================
  Files          37       37           
  Lines        3527     3527           
=======================================
  Hits         1006     1006           
  Misses       2521     2521           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[theHenks]

Hi, I noticed that something strange was happening with the LQ processor. I noticed that the dirft time correction property function got broken during Florians debugging. Previoues to this PR the lq_ctc_correction() function expected the ctc_driftime_cutoff_method to have brackets. I now changed this so that the function also returns the correct property function if ctc_driftime_cutoff_method does not have explicitly brackets.

How did the the property function break during my debugging? I never touched this code??

@theHenks I also noticed that during your debugging you encountered some problems with my plots. This happened because the the wrong ctc correction broke them. With this fix they all work again as intended and it would suggest to include the lq_cut plot again as it is currently commented out. Except you had another reason the remove it from the lq processors.

The issue with the plotting is related to NaN values within your Vectors to be plotted, in particular the histogram2d plots. I don't see how this PR is fixing this?

[DaGeibl]

Sry i Had a Mistake in my Comment. You did not change the Code you Changed how the ctc_drift_expression is passed to the Function. I passed the expression work brackets, you Save it and pass it without brackets. So we could also Change the Expression in the config but adding the brackets here is the Most robust Solution if something is changed again.

This other Problem i have to admit I did Never encounter and After this PR also did not encounter again. Your error is I think behause I have a fixed Window for the Plot and the Expression Bug Gas the Effekt That not a Single Event is in That window. Without one Element the Plot fails. But when the Plot geht’s valid values they work.

[fhagemann]

Can you continue discussing the NaN plotting issue somewhere else, for example by opening a new issue?
I feel like this PR fixes a very obvious and straight-forward-to-fix bug and should be merged ASAP.

Clarify the correct placing of the brackets

[theHenks]

Can you continue discussing the NaN plotting issue somewhere else, for example by opening a new issue? I feel like this PR fixes a very obvious and straight-forward-to-fix bug and should be merged ASAP.

I created a new issue

[theHenks]

I will go ahead and merge since I want to test this on data