Mortar: fix mapping at multigrid levels #1900
Merged
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.
Description
The same mapping object was being used at every multigrid level which, when the mortar feature is enabled, led to incorrect setup of mapping within level operators. This PR fixes this, as well as some other minor typos/descriptions.
Solution
A MappingQCache object is now created at every level when
set enable = truein the mortar subsection.Testing
No new tests were added. This issue was only spotted in larger simulations, which is why existing application tests were not affected.
Documentation
Miscellaneous (will be removed when merged)
Checklist (will be removed when merged)
See this page for more information about the pull request process.
Code related list:
Pull request related list: