Skip to content
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

Switch over generic_fill/hypfill to AMReX implementation #837

Merged
merged 7 commits into from
Apr 11, 2020

Conversation

maxpkatz
Copy link
Member

@maxpkatz maxpkatz commented Apr 5, 2020

PR summary

AMReX provides CpuBndryFuncFab and GpuBndryFuncFab which are very similar to what generic_fill and hypfill did. The AMReX implementations are now used. We still have a hypfill and denfill function, so that existing problems are not broken, but the main one in Source/ no longer calls amrex_filcc (it only has the ambient code now). The problems that do override bc_fill_nd.F90 are thus no longer required to call amrex_filcc, although I have left them alone for now (they will just redundantly do it a second time).

PR checklist

  • test suite needs to be run on this PR
  • this PR will change answers in the test suite
  • all functions have docstrings as per the coding conventions
  • the CHANGES file has been updated
  • if appropriate, this change is described in the docs

@zingale zingale merged commit f565bfd into development Apr 11, 2020
@zingale zingale deleted the bndryfuncfab branch April 11, 2020 21:32
zingale pushed a commit that referenced this pull request Jun 21, 2020
PR #837 removed the need for any problem setup to call amrex_filccn in its local bc_fill_nd.F90 routines, hypfill and denfill, because now we will always call the AMReX BC routines prior to entering hypfill or denfill. However that PR did not remove the calls to it from the problem setups that used it, noting that these calls are now redundant. These calls are now removed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants