Moving mesh 2d

Submitted by kevin.eipe on Mon, 05/18/2015 - 13:43

Hi guys,

I had a query about moving mesh in 2d.
I created granular particles on a lattice and imported a mesh from CAD, and moved that mesh. However, as soon as the mesh got close to the atoms and before they could interact, LIGGGHTS gave an error!

ERROR on proc 0: Internal error (../tri_mesh_I.h:108)
--------------------------------------------------------------------------
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.

Does this mean particles on a lattice cannot interact with a moving mesh? and only works if particles are in 3d?

Thank you
Kevin

Forums:

ckloss's picture

ckloss | Mon, 06/01/2015 - 12:43

Hi Kevin,

I think no one has tried moving mesh in 2D. I personally heavily dis-encourage 2D - the world is 3D and these simplifications do not work for the case of granular flow !
Make a narrow slice in 3D with periodic boundary conditions

Best wishes
Christoph

anandmds's picture

anandmds | Fri, 07/03/2015 - 08:43

hey, I have the same problem, but in 3-D. I created atoms using " create_atoms " command in a particular region and set its properties. The region is enclosed by the .stl walls I imported (Of which on is a moving wall) . The atoms are created nonetheless, but showing the same error as Kevin's. I don't know what seems to be the problem. Kindly help.

thanks
anand

Anand.M
M.S. Mechanical Engineering,
I.I.T. Madras

anandmds's picture

anandmds | Fri, 07/03/2015 - 08:45

hey, I have the same problem, but in 3-D. I created atoms using " create_atoms " command in a particular region and set its properties. The region is enclosed by the .stl walls I imported (Of which on is a moving wall) . The atoms are created nonetheless, but showing the same error as Kevin's. I don't know what seems to be the problem. Kindly help.

thanks
anand

Anand.M
M.S. Mechanical Engineering,
I.I.T. Madras

Maryam | Sun, 04/24/2016 - 07:44

For those who face the same error: I had the same problem and solved it by changing the lower coordinate of the insertion region box to something non-zero. For some weird reason if I put it zero LIGGGHTS will give me the above-mentioned error.

Maryam