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
I am trying to test mesh.deform function. It did work well with serial run.
However, it returned an error with mpirun when the number of elements in x > number of elements in y.
The traceback is:
uw.libUnderworld.StgDomain.Mesh_DeformationUpdate( self._cself )
RuntimeError: Error encountered. Full restart recommended as exception safety not guaranteed. Error message:
An error occurred when checking mesh metrics. Possibly two nodes are in an identical location.
It may be due to the StgDomain distribute local rank related to the direction having larger number of element.
Let's assume using 2 processors (mpirun -np 2 ...), underworld gives
Global element size: 40x30
Local offset of rank 0: 0x0
Local range of rank 0: 20x30
Thus, if I change the value of Model.mesh.data[index][1] in the deform_mesh() function, the two processors may not know how the y coordinate has been changed in another process, and then return the error.
Hi all,
I am trying to test mesh.deform function. It did work well with serial run.
However, it returned an error with mpirun when the number of elements in x > number of elements in y.
The traceback is:
uw.libUnderworld.StgDomain.Mesh_DeformationUpdate( self._cself )
RuntimeError: Error encountered. Full restart recommended as exception safety not guaranteed. Error message:
An error occurred when checking mesh metrics. Possibly two nodes are in an identical location.
It may be due to the StgDomain distribute local rank related to the direction having larger number of element.
Let's assume using 2 processors (mpirun -np 2 ...), underworld gives
Global element size: 40x30
Local offset of rank 0: 0x0
Local range of rank 0: 20x30
Thus, if I change the value of Model.mesh.data[index][1] in the deform_mesh() function, the two processors may not know how the y coordinate has been changed in another process, and then return the error.
I also attach the test file below:
mesh_deform_mpi_test.txt
Do we have a way to overcome this issue?
Thank you in advance.
Best regards,
Pham Ngoc Kien
Ph.D. Student
School of Earth and Environmental Sciences
Seoul National University
The text was updated successfully, but these errors were encountered: