Hybrid Interpolation on CPU - #847
Open
stefan-schnake wants to merge 17 commits into
Open
Conversation
# Conflicts: # src/asgard_term_sources.cpp
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
2 participants
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.
This PR adds hybrid interpolation on the CPU. Both hybrid source and hybrid md_terms are included.
Tests included:
Test of hybrid source by 1x1v BGK step to ensure hybrid interpolation of Maxwellian preserves collision invariants
Test of hybrid md_term by interpolating u_t(x,v) + lambda*(u(x,v)-g(x)u(x,v)) with both hybrid and standard interpolation (results should agree on a dense grid). WILL NOT AGREE ON SPARSE/ADAPTIVE GRID
Test to make sure num_pos and num_vel are positive for hybrid interpolation to work.
AI was used to generate test cases and incorporate into standard API calls.