-
Notifications
You must be signed in to change notification settings - Fork 111
Use Mesh::addCoordinates(location) to initialize Coordinates #1372
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
Closed
Closed
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
bdb56d8
Use localmesh for d2x and d2y, and interpolate them to location
johnomotani 8795aca
Remove uses of global 'mesh' in BoutMesh::addBoundaryRegions()
johnomotani 21a0fc5
Allow initialization of Coordinates with Mesh::addCoordinates(location)
johnomotani f528e6a
Add nullptr entries to coords_map in FakeMesh of unit tests
johnomotani b5b80f2
Fix error message, replacing reference to 'REQUEST_STAGGER'
johnomotani 0bf16af
Remove createDefaultCoordinates() method from header
johnomotani 75ce522
Revert change of Mesh::coords_map to use std::unique_ptr
johnomotani 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 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
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
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
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
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
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
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
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.
This logic is in
Coordinates::geometrytoo -- does it need to be here?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.
I think it does need to be here. This code ensures the
Coordinatesare created at each location initially. The code inCoordinates::geometry()replaces (and therefore re-calculates) the staggeredCoordinatesobjects after theCELL_CENTRECoordinatesis changed bygeometry(). The idea is that #1392 will update things so that here we only create theCELL_CENTRECoordinates(i.e. lines 845-860 are deleted), the user has to callMesh::addCoordinates(location)for any needed staggered location, and if the user callsgeometry()it has to be before the staggeredCoordinatesare initialized.Maybe there is a neater way, but I don't think we want to call
Coordinates::geometry()here because it would duplicate work already done whengeometryNoRecalculateis called as part of the constructor inaddCoordinates(CELL_CENTRE).