fix: handle bad ctof_tdcadc fits
#223
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If the first peak fit is bad, it's possible that the 2nd peak finder will try to search for a peak in an _empty_ dataset, since the 1st peak's sigma may be wider than the full histogram range. In this bad case, just equate the 1st and 2nd peak positions so we get 2 bad fits that are equivalent.
Closed
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If the first peak fit is bad, it's possible that the 2nd peak finder will try to search for a peak in an empty dataset, since the 1st peak's sigma may be wider than the full histogram range. In this bad case, just equate the 1st and 2nd peak positions so we get 2 bad fits that are equivalent.