-
Notifications
You must be signed in to change notification settings - Fork 17
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
Add leapfrog pusher for plasma #847
Merged
MaxThevenet
merged 22 commits into
Hi-PACE:development
from
AlexanderSinn:leapfrog_pusher_with_ab5_option
Jan 31, 2023
+627
−650
Merged
Changes from all commits
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
9e4fd00
leapfrog pusher
AlexanderSinn 5ceaecd
Add second order using DualNumber Autodiff
AlexanderSinn daea610
include new header
AlexanderSinn 2b3af6e
add second gather
AlexanderSinn 87ccd5d
test with second gather
AlexanderSinn f07bc32
remove force terms
AlexanderSinn 53c3f71
fix salame
AlexanderSinn 51280dd
fix periodic issue
AlexanderSinn 91b2d9f
leapfrog pusher with ab5 option
AlexanderSinn 4d1e0cd
Push after ionization and collisions
AlexanderSinn 72c62c9
fix missing variable
AlexanderSinn 15e4cda
fix missing variable
AlexanderSinn ea969aa
Merge branch 'development' into leapfrog_pusher_with_ab5_option
AlexanderSinn 3140376
merge dev
AlexanderSinn 9685963
Merge branch 'development' into leapfrog_pusher_with_ab5_option
AlexanderSinn 46e8d2e
push psi instead of psi_inv
AlexanderSinn 604eee0
Add support for collisions and ionization
AlexanderSinn e5bf096
make leapfrog pusher the default
AlexanderSinn da1d688
Make AB5 pusher default and reset CI for reasons mentioned above
AlexanderSinn ab79215
Reset production SI benchmark manually ☹
AlexanderSinn 730433b
Add pusher printout
AlexanderSinn 590677d
add suggestions
AlexanderSinn File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AlexanderSinn is it work making this a compile-time option?
I think pre-compiling both options and doing a runtime switch before the two specialized kernels would be more user friendly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Discussed: needs additional (25) force terms on the particle, so that's a bit of a heavy lift.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As mentioned, it is a compile-time option not for performance of the push kernel, but rather to save on memory of the 25 Adams-Bashforth force terms (per plasma particle) if the leapfrog pusher is used. One would need to change these to runtime components to make this a runtime option.