Add observables with amplitude corrected by baseline #152
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.
Up to this, the PeaksFinderProcess uses the ADC amplitude of the peaks, but does not correct it substracting the baseline. Some changes are made to keep track of the baseline of each signal and substract it to the peak´s amplitude in order to better reconstruct the energy deposited.
Before:
Fig 1: Observables for a given event before the change.
Now, the event is unaltered, but 2 new observables are added ("peaksAmplitudeBaseLineCorrectedADC" and "peaksAmplitudeBaseLineCorrectedADCSum"):
Fig 2: Observables after the change.
These new observables take into account the baseline of each signal, calculated as the PeaksFinderProcess does for other capabilities:
Fig 3: Calculation of the baseline for each signal.
As we can see, the "peaksAmplitudeBaseLineCorrectedADC" substracts the corresponding baseline:
3578-254=3324
3262-250=3012
Also, the "peaksEnergy", that uses the calibration factor, is now calculated with the corrected amplitude.