Bug Reports for CFDEM®coupling, LIGGGHTS®, and ParScale

(Possible) bugs / suspicious behavior should be reported as a new thread here, not in the user forum. This should give both you and the developers a clear idea about the status of your bug report (submitted/assigned/fixed)

Jump in KE in a multi processor run during multiple run @LIGGGHTS

Submitted by Rahul on

LIGGGHTS developers, community:

I am experiencing a jump in kinetic energy during a multiple runs. My simulation is about uni-axial compression setup.
After I read the restart file in the same number of processors, I see a jump in kinetic energy when I invoke the fix move/mesh command in between 2 runs. The jump is pretty high.

Particles deleted unexpectedly when using 'fix insert/pack' with CFDEM

Submitted by Nucleophobe on

CFDEM developers, community:

I am experiencing some strange behavior using CFD-DEM coupling with continuous particle insertion. On the timestep where a new particle is inserted, old particles are sometimes deleted erroneously.

Miracle of PBC and Meshes

Submitted by richti83 on

I needed to simulate a simple troughed chain conveyor, so I made a box from -1 to 1 and set PBC in conveying direction.
After the first plate goes through the PBC it starts to flicker, this means it is one time at the end and the other time at the beginning of the simulation box.

wall contact not detected

Submitted by richti83 on

I have encountered a strange behaviour in very rare cases when a particle hits exactly a common node of two triangles.
Attached a simple testcase with a single particle and a mesh with two triangles.
When the particle is at
0.075 0.0750001 0.425
everything works fine,
but if it is at
0.0750001 0.075 0.425
the contact is not detected.
I looked deep in the code but don't understand everything what happens in tri_mesh_I resolveEdgeContactBary.
The function everytime ends up in

....
else{
double closestPoint[3];

Dump mesh stl binary

Submitted by richti83 on

There is a bug when one tries to dump binary stl files. The dump class opens the file in textmode and not in binary mode.
I fixed this with an own openfile method in dump_mesh_stl.cpp which checks for writeBinarySTL_ flag.
if (filewriter) {
if (writeBinarySTL_) {
fp = fopen(filecurrent,"wb");
} else {
fp = fopen(filecurrent,"w");
}

everything else is like in the parent class.

On my case with 1570 triangles the dump binary stl is two times faster than ASCII dump !

Best,
Christian.

Sign Error in fix_wall_gran relating to cwl_->add_wall_1

Submitted by richti83 on

I think after the last changes in FixWallGran::post_force_eval_contact the line

vectorAdd3D(x_[cdata.i],cdata.delta,contactPoint);

Should be

vectorSubtract3D(x_[cdata.i],cdata.delta,contactPoint);

because the sign of delta has changed in the past.

[critical bug] Illegal situation in MultiNodeMesh

Submitted by richti83 on

LIGGGHTS 3.0.5 introduces a bug in multi_node_mesh_I.h when using mesh mover rotate in multicore mode.
Simply run examples/LIGGGHTS/Tutorials_public/movingMeshGran with np 12 or more to reproduce this issue.

ERROR on proc 0: Illegal situation in MultiNodeMesh::registerMove (../multi_node_mesh_I.h:327)
ERROR on proc 2: Illegal situation in MultiNodeMesh::registerMove (../multi_node_mesh_I.h:327)
ERROR on proc 1: Illegal situation in MultiNodeMesh::registerMove (../multi_node_mesh_I.h:327)

Compilation error

Submitted by jenslaube on

Hi I cloned the latest version of the LIGGGHTS development version from git://cfdem.git.sourceforge.net/gitroot/cfdem/liggghtsdev today (3rd of November 2014) and have problems compiling it. The error message is the following:

myvector.h(37): warning #1011: missing return statement at end of non-void function "LAMMPS_NS::vectorConstruct3D"
}
^

myvector.h(44): warning #1011: missing return statement at end of non-void function "LAMMPS_NS::vectorConstruct3D(int *, int, int, int)"
}
^