Please review the developer documentation
on the wiki of this project that contains help and requirements.
Proposed changes
Currently, if we coarsen to level 0, the poisson solver crashes due to assuming x_lev >= 1. This fixes the issue by bypassing the solve and generating the solution based on the given boundary conditions.
What type(s) of changes does this code introduce?
Put an x in the boxes that apply.
[x] Bugfix
[ ] New feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):
Does this introduce a breaking change?
[ ] Yes
[x] No
What systems has this change been tested on?
andremarie
Checklist
Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you're unsure about any of them, don't hesitate to ask. This is
simply a reminder of what we are going to look for before merging your code.
[X] this PR is up to date with current the current state of 'develop'
[X] code added or changed in the PR has been clang-formatted
[ ] this PR adds tests to cover any new code, or to catch a bug that is being fixed
Please review the developer documentation on the wiki of this project that contains help and requirements.
Proposed changes
Currently, if we coarsen to level 0, the poisson solver crashes due to assuming x_lev >= 1. This fixes the issue by bypassing the solve and generating the solution based on the given boundary conditions.
What type(s) of changes does this code introduce?
Put an
xin the boxes that apply.Does this introduce a breaking change?
What systems has this change been tested on?
andremarie
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. This is simply a reminder of what we are going to look for before merging your code.