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)

Bug in compute wall/gran/local (Part -II)

Submitted by tapsab on

There is another bug in "compute wall/gran/local". The number of contacts reported seems to change if you split the mesh into several .stl files instead of just one .stl file. I again attach a simple example which is exactly the same as the one attached before under "Bug in compute wall/gran/local". The mesh consists of three walls, bottom, left and right. There are two options, to use a single .stl file (mesh.stl) which contains all three walls.

Bug in compute wall/gran/local

Submitted by tapsab on

There seems to be a bug in "compute wall/gran/local" when multiple meshes exist in a simulation. The mesh id's reported by the compute are erroneous. I attach an example to illustrate the same. The simulation has two particles tightly bound between three walls, bottom, left and right. As per the order in the command "wall/gran/hertz/history" the mesh id's should be bottom->0, left->1, right->2. The bottom wall is touching one particle and the left and right walls are touching the both the particles.

problem with cfdemSolvers :pointer being freed was not allocated

Submitted by qzt on

Hello,

I am trying to install the CFD-DEM following the githubAccess_public.pdf. Both LIGGGHTS and CFDEM compiled well and did give me the binary execution files of solvers (i.e. cfdemSolverPiso, cfdemSolverIB, cfdemSolverPisoScalar).
However, when I try to run the tutorial cases, all of them interrupted with error like : (just put the error message from cfdemSolverIB for example)

cfdemSolverIB(52051) malloc: *** error for object 0x7fff7f97f860: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug

Mesh interaction bug

Submitted by tapsab on

Hi,
The bug that caused "exploding" particles when they interact with mesh corners seems to be still there in version 2.1. I attach a case to illustrate the same. As you run the input file "Bug.in" and monitor the kinetic energy you will notice that it jumps between steps 432000 to 433000. The particle that explodes is particle id 58. The bug is processor dependent, similar to what Eric had reported earlier. If you use one, two or three processors everything is fine. The bug only occurs when I specify 4 processors.

Best,
Tapan

Possible bug in particle interaction with edge of a mesh (another example)

Submitted by ericparteli on

Hi, Christoph, Tapan and Philippe,
here another case that seemingly represents a similar problem as the one Tapan found in his case.
The figure frameA.jpg shows the geometry used in my simulation (run with LIGGGHTS 2.0.6).
The particle that explodes is identified in the figure, whereas a zoom at that particle possibly shows what is causing the explosion (see frameB.jpg): the particle is ignoring the CAD walls and penetrating into it.

Possible bug in particle interaction with edge of a mesh

Submitted by tapsab on

I encountered a possible bug while running a simulation wherein particles are falling onto the edge of a cylinder (modeled using mesh/surface). I mentioned this bug in the user forum thread titled "Older version of LIGGGHTS (2.0.6)" but I guess its better served in this forum. To illustrate the problem I made up a simple case of a single particle falling onto the edge of a cylinder.

Triangle ID always zero in wall/gran/local

Submitted by msbentley on

I'm having a problem with compute wall/gran/local. I have a simulation with a single mesh floor (see image for the mesh IDs produced with dump mesh/vtk):

fix floor all mesh/surface file mesh_asc.stl type 1
fix meshes all wall/gran/hertz/history mesh n_meshes 1 meshes floor

and I want to dump the wall/particle interactions with

compute wallcomp all wall/gran/local pos id contactArea

Constant high omega for few particles close to base of system

Submitted by msbentley on

This may be a bug, or just a lack in my understanding - but I have noticed in many sims that often get one or two particles with unexpectedly high omega, usually at the bottom of the sim domain (in contact with the lower wall). As a simple example, I took the in.newModels example from the contactModels tutorial and simply ran for a bit longer (150000 instead of 50000 timesteps).

bug in mesh-granular interaction?

Submitted by ericparteli on

Dear Sirs,
there seems to be a bug which is causing an error in the interaction between mesh surfaces and granular particles depending on the processors specification.
I try to run the attached case with LIGGGHTS_2.0.4 using "nice -19 mpirun -np < in.device"

cfdemSolverPiso ncorrSoph issue

Submitted by schmeeck on

In cfdemSolverPiso there is the following line of code:
int nCorrSoph = nCorr + 5 * pow((1-particleCloud.dataExchangeM().timeStepFraction()),1);
I have been running on othogonal grids with nCorr set to 2, and timeStepFraction =1. Unfortunately nCorrSoph evaluates to 2 or 1. It swithches off between the two values within the same run. This seems to be a double to int casting error.

Later in the Piso algorithm there is this:
if
(
corr == nCorr-1
&& nonOrth == nNonOrthCorr
)