Write and read mesh partitioning information to/from file#52
Open
Write and read mesh partitioning information to/from file#52
Conversation
Major GPU support, parallel HDF5 I/O, channel forcing module, and CI improvements
3a3c17b to
ef9481e
Compare
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
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.
The idea of this PR is to bypass the bottleneck of the mesh read in (reading and partitioning the mesh in serial).
A new LOGICAL control file keyword has been added:
read partitioning from fileswith the default value of.FALSE.. The keyword specifies if the solver should read the partitioning information from files instead of performing the mesh partitioning. When.FALSE., the solver reads the mesh file in serial at preprocessing, partitions the mesh, and writes the partitioning information to files in./MESH/partitioning_NUMRANKS_ranks(whereNUMRANKSis the number of ranks). When.TRUE., the solver will directly try to read the files in that folder. If the files do not exist, the solver will throw an error.