Conversation
… that step and can delete the segments with bad fits, etc
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Convergence of the position fit still isn't great, but that can be worked out as we go along. The main infrastructure is now in place and tested.
If you give the 22Ne data on CD2 target, with an appropriate settings file, calibration file and reaction file, but also add the
-anglefitflag, the code will sort the data, fit the Doppler shifted 440 keV peaks in each segment, and build a position fit for all clusters, using the values in the reaction file as the starting values.Once this is done, the peak centroids are written to a file at
22Ne_fitted_energies.dat, which can be edited to remove segments with bad fits (fits can be inspected in the pdf file atpeak_fits.pdf) or add manual points. This file can then be read back in tomb_sortusing the-angledataflag, in place of the data files. This skips the process of fitting the peaks and goes directly to the peak position determination, saving time and using the user provided values.The next step is to include the phi angle constraints from the 22Ne on 196Pt data, but I first have to make the analysis for this.