-
Notifications
You must be signed in to change notification settings - Fork 32
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
pmb->loc
broken?
#1061
Comments
No, this is the expected behavior as the grid you are using results in a forest of six trees. Each block has a logical location relative to the tree it is in, but 'LogicalLocation' now also contains the index of the tree in which it is contained accessible via 'LogicalLocation::tree()'. Getting on a plane now (and writing this from my phone), I will look at how to extract the offsets you want tomorrow morning. They are probably already contained in the neighbor block information. |
For now, you could use Forest::GetLegacyTreeLocation using the locations stored in the MeshBlocks to get the old global logical location, but this will not work with general forests. |
Perfect, that did the job! Thanks for the quick reply. |
@lroberts36 I'm trying to calculate the effective offsets for each block for writing outputs.
Within a block like (on a mesh with 64x96 and blocks of 32x32)
Block 0 writes chunk of [32 32 ] with offset [0 0] and logical locs [0 0]
Block 1 writes chunk of [32 32 ] with offset [0 0] and logical locs [0 0]
Block 2 writes chunk of [32 32 ] with offset [0 0] and logical locs [0 0]
Block 3 writes chunk of [32 32 ] with offset [0 0] and logical locs [0 0]
Block 4 writes chunk of [32 32 ] with offset [0 0] and logical locs [0 0]
Block 5 writes chunk of [32 32 ] with offset [0 0] and logical locs [0 0]
The text was updated successfully, but these errors were encountered: