MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
with errorcode 1.
NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them."
Thank you very much for the instant response and apologies for late response. I am currently working on it. Will report the feedback upon succesful completion.
I am experiencing problems with the bounding of the base mesh box around the multi region mesh geometry. A manual value input is giving me an unwanted result. Please help.
Manual entry of limits of base mesh box and material point.
Mesh Run .
Error :
“[0] --> FOAM FATAL ERROR:
[0] Cannot find triSurfaceMesh starting from “processor0/constant/triSurface/solid_0.stl”
[0]
[0] From function triSurfaceMesh::checkFile(const fileName&, const fileName&)
[0] in file searchableSurface/triSurfaceMesh.C at line 116.
[0]
FOAM parallel run exiting”
Yes. It happened in the same project. I think importing it again would really help.
I was wondering the problem might be either with the geometry format or the Material point definition.
Found no discrepancies.
Will be rechecking,
Found the problem in the material point definition. It was supposed to be in the fluid region but instead was defined in the solids region.
The system meshed it finally, although theres a lot of tweaking to be done.
glad that it worked out. You’re right, we’re currently looking into more automation steps for the meshing workflow, that there are more settings pre-configured adaptive to the geometry. Is there any specific that you’d like to see changed when meshing?