[Peter_600]

Hi Foamers,

who of you has successfully applied attach/detach topo changes in parallel?
How to decompose the grid. I ve been told that the faces have to be treated on one processor and shouldn t be distributed on several processors.
Thanks in advance!

Cheers Peter

[Peter_600]

Hi Foamers,

who of you has successfully applied attach/detach topo changes in parallel?
How to decompose the grid. I ve been told that the faces have to be treated on one processor and shouldn t be distributed on several processors.

Here, a small description of my problem.

I am using OF-1.6-ext for in-cylinder aerodynamic problems. For the valve and piston motion I am using the accordionEngineMesh class. It uses the FEM automesh motion solver for the valve and piston motion and for valve opening and closure the attach/detach boundaries. And here the problem pops up.
Everything works fine in serial but in parallel it doesn t.
The problem comes from the attach/detach faces. When I decompose my case on 2 processors and I try to run it following error message appear.

Create engine time

Create mesh

Selecting engineTopoChangerMesh accordionEngineMesh
[0]
[0]
[0] --> FOAM FATAL ERROR:
[0] Attach/detach zone contains no faces. Please check your mesh definition.
[0]
[0] From function void Foam::attachDetach::checkDefinition()
[0] in file polyMeshModifiers/attachDetach/attachDetach.C at line 104.
[0]
FOAM parallel run aborting
[0]
--------------------------------------------------------------------------
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.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
mpirun has exited due to process rank 0 with PID 8568 on
node nusm-14 exiting without calling "finalize". This may
have caused other processes in the application to be
terminated by signals sent by mpirun (as reported here).
--------------------------------------------------------------------------

The faces for my the detach/attach topoChanger are only on one processor. Since all processors are executing the same tasks, one processor is complaining that it don t have faces for the attach/detach topoChanger.

I ve added a small description with my problem (simplified single cylinder engine, only for mesh motion tests)

DummyEngine.jpg


Cheers Peter

[novakm]

Originally Posted by Peter_600

Hi Foamers,

who of you has successfully applied attach/detach topo changes in parallel?
How to decompose the grid. I ve been told that the faces have to be treated on one processor and shouldn t be distributed on several processors.

Here, a small description of my problem.

I am using OF-1.6-ext for in-cylinder aerodynamic problems. For the valve and piston motion I am using the accordionEngineMesh class. It uses the FEM automesh motion solver for the valve and piston motion and for valve opening and closure the attach/detach boundaries. And here the problem pops up.
Everything works fine in serial but in parallel it doesn t.
The problem comes from the attach/detach faces. When I decompose my case on 2 processors and I try to run it following error message appear.


The faces for my the detach/attach topoChanger are only on one processor. Since all processors are executing the same tasks, one processor is complaining that it don t have faces for the attach/detach topoChanger.

I ve added a small description with my problem (simplified single cylinder engine, only for mesh motion tests)

Attachment 15703


Cheers Peter

Hi Peter,

Did you made any progress on the topic that you have described here?
I would like to simulate real engines in OF, so this topic is essential for me.
It will be so great if would you mind if you share your insight to the problem

[Joe Wang]

Hi, Peter,
I'm recently working on a project and I have troubles on setting up the dynamic mesh feature. I've looked up for information but haven't figured it out. It seems that your problem has a similar feature with mine. Could you share me your simulation setup as a tutorial? Thank you.
Joe