You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the following procedures are used to load partitioned mesh in both XGCm and GITRm following PUMIPic example:
read in the full mesh
load in the partition file and create PICparts
delete the full mesh as necessary
These procedures are not optimal at all and will encounter memory issue as the mesh size becomes large (>20-50 million mesh elements for example, depending on the GPU memory). They are similarly to this test:
I thought I had remembered using pre-constructed meshes for performance testing. The read(...) function you found looks correct and the write(...) function to produce the constructed mesh is also in src/pumipic_file.cpp.
This doesn't solve the high memory usage issue, but may give you a chance to run the mesh construction job on nodes (possibly using a CPU only build) with more memory as a pre-processing step before running an analysis.
@cwsmith: yes, looking further we need to write the partition file *.ppm file in a node with more memory to get the partitioned mesh and partition information.
Currently, the following procedures are used to load partitioned mesh in both
XGCm
andGITRm
followingPUMIPic
example:These procedures are not optimal at all and will encounter memory issue as the mesh size becomes large (
>20-50 million
mesh elements for example, depending on the GPU memory). They are similarly to this test:pumi-pic/test/test_full_mesh.cpp
Lines 22 to 34 in b6678b0
The proper way would be to read in the partitioned mesh directly. It's not clear if below function is already providing the necessary steps:
pumi-pic/src/pumipic_file.cpp
Lines 118 to 206 in b6678b0
The above function is used in the following test:
pumi-pic/test/pseudoXGCm.cpp
Lines 379 to 388 in b6678b0
The text was updated successfully, but these errors were encountered: