Peakwise fit function for calibration peak fits #72
+65
−41
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.
We want to have different peakshapes for the escape peaks and maybe for other low-statistics peaks. That's why I made the following changes:
fit_peaks()
now also accepts a vector offit_func
.f_fit
,fit_func
, ...). If you feel creative and have better suggestions, feel free to write them below.Available fit functions:
gamma_def
: "default" gamma peakshape with gaussian signal, low-energy tail, and background (flat + step)gamma_tails
: default gamma peakshape + high-energy tailgamma_bckSlope
: default gamma peakshape + linear background slopegamma_bckExp
: default gamma peakshape + exponential backgroundgamma_bckFlat
: default gamma peakshape - step background (only flat component!)gamma_tails_bckFlat
: default gamma peakshape + high-energy tail - step background (only flat component!)Example: with escape peaks with high-energy tail but w/o Compton step
@theHenks we could write the
fit_func
for theth228_names
in jldataprod config, as we discussed. Any additional suggestions?@fhagemann, @verenaaur I don't think that the A/E functions have to be adapted to this change, right?