-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multipole boundary data #291
Open
mrhardman
wants to merge
17
commits into
master
Choose a base branch
from
multipole-boundary-data
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
…s rather than using coord.element_scale and coord.element_shift for get_KJ_local!() matrix. Introduce initial explanatory documentation.
…for unused function.
…ALIBUR report and giving input parameter information. Modify the index to feature this note and the note on magnetic geometry.
…tions for the calculation of the Rosenbluth potentials.
…he exact results for the Rosenbluth potentials for the Maxwellian piece of F, and multipole for the rest. Tests extended to this option. Rename boundary_data -> boundary_data_option to make internal code easier to follow.
…tion across cores in delta_f_multipole option.
…f different boundary data calculations.
…hat these options are precompiled.
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.
Option to calculate boundary data from a multipole expansion. Effective, fast, and accurate if velocity domain is large enough. Further testing likely required. The option permits the collision operator to run at very large resolutions, by avoiding the need to compute integration weights, but the actual speedup of the simulation at runtime appears to be small for the examples tested. A potentially useful feature for future work.
Now featuring three (enum) options for calculating the boundary data:
vpa.L
andvperp.L
when the solution is closer to Maxwellian.These features are tested in
fokker_planck_tests.jl
. Further simulations are required to test the performance of these features.