Add some Mesh methods for handling Z parallelisation
#3245
Conversation
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Tests are updated because `FakeMesh` has `GlobalZ(z) == z`. This is completely arbitrary, we could have a `GlobalZ` definition that matches `BoutMesh` (`z / nz`) then we wouldn't need to change the tests, but this way is a bit clearer what we're testing.
Also make related methods all `const`
These are just the `BoutReal` overloads of the equivalent `getGlobal?Index` methods
dschwoerer
previously approved these changes
Jan 13, 2026
| Solver* UNUSED(solver)) | ||
| : Laplacian(opt, loc, mesh_in), A(0.0), C(1.0), D(1.0) { | ||
|
|
||
| bout::fft::checkZSerial(*localmesh, "`tri` inversion"); |
Contributor
There was a problem hiding this comment.
Would it be clearer to name this assertZSerial()?
| ASSERT2(var.getMesh()->getNguard(direction) >= nGuards); | ||
| ASSERT2(direction == DIRECTION::Z); // Only in Z for now | ||
| ASSERT2(stagger == STAGGER::None); // Staggering not currently supported | ||
| ASSERT2(bout::utils::is_Field3D_v<T>); // Should never need to call this with Field2D |
Contributor
There was a problem hiding this comment.
Isn't that known at compile time?
So there is no runtime overhead, to have this check always included?
(Same for several of the above)
Member
Author
There was a problem hiding this comment.
Yes, but checking at compile implies that we need to not build some of these for certain types, which might complicate the various macros. At any rate, it's something for a different PR!
[skip ci] Co-authored-by: David Bold <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Supports #3242
Note these don't actually add Z parallelisation, just let us handle it correctly in various places
Mesh::GlobalZfor global Z index in[0, 1]Mesh::getNZPE/getZProcIndexfor Z processor infobout::fft::checkZSerialto guard routines using FFTThese also make a lot of code more consistent between the directions