additional Momentum apperture method #92
Open
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
Update with atcollab/at master
New function MomAperture_Project2Start: Similar to MomAperture_allRing, but all positions are first tracked until the ring starting point and then tracked together as many turns as required. It speeds up the calculations around a 50%, results are similar but not exactly the same since the searching method is also different (bipartition).
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.
A new file: MomAperture_Projecect2Start.m. This method speeds up the calculation time for non-compiled scripts. It uses a bi-partition search of the momentum threshold.
I have observed some discrepancies, which I think it is due to the fussiness of the momentum aperture. Could you check the method and see if it also speeds up calculations in your case?
Cheers