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)

Trouble with Restarts and insert/stream

Submitted by cTop89 on

It seems that while running a restarted simulation with an insert/stream fix, the insert/stream fix never starts inserting particles again. I've tried a couple different versions of the script but nothing seems to work. My most "successful" version, I've attached.

When I run this script I get an "INFO" line in the log that tells me how often the insert/stream will insert, but then it never actually does.

I'm attaching the original input files used to generate the restart file, and the input files for running the restart.

Let me know if I can provide anything else.

Multiple STL Output/Multiprocessor Bug (LIGGGHTS 2.3.2)

Submitted by cTop89 on

When using liggghts to output a separate stl file for several different components (conveyor belts, pulleys, chutes) using multiple processors (at least 2), the last line of the stl file is omitted ("endsolid LIGGGHTS_STL_EXPORT") in all stl files but the last stl file written at each dump interval.

I can provide simple examples upon request.

Triangle-grain force computation depends on numbering (Liggghts 1.5.x)

Submitted by Franzzzzzzzz on

I've found a problem in Liggghts 1.5 and 1.5.3 when computing the force between a grain and a mesh triangle when the triangle size is of the order of the grain diameter. It appears that the force on the triangle depends on the way the triangles are numbered in the mesh. For example, when a grain slide on a square (2 triangles separated by the diagonal), the force on each triangle depends on which one was defined first in the imported stl (I can attached the input file if needed).

Problem when parallelizing w/ two particle insertions

Submitted by cstoltz on

I'm having a problem with a pair of simulations in which I use two particle insertions to fill the system. Each simulation seems to run fine in serial mode, but crashes during the insertion phase when I try to run in parallel. It also runs fine if I turn off one of the insertions. I've also tried this with both insert_stream and insert_rate_region.

definition of phi

Submitted by cheng1988sjtu on

I guess if we want to use turbulence model, we'd better stick to the original definition of phi = fvc::interpoplate(U) & mesh.Sf(), because, for example, if we want to use k-epsilon model, in k-equation and epsilon equation, the convection term could use phi as well.

Meanwhile, in p-equation, we need to account for the divergence of the face velocity field by taking out the difference between the interpolated velocity and the flux: fvc::ddtPhiCorr(rUA, U, phi)

Bug when restarting with mesh walls in liggghts version 2.2

Submitted by tapsab on

There is a bug in version 2.2 which causes a simulation that reads data from a restart file to crash if mesh walls are used. In the zipped folder attached with this post you will find the files necessary to recreate the problem. First run Step1.in to generate the restart file and then run Step2.in. The bug is version dependent. It only appears when I run it with version 2.2. It works fine with version 2.1.2

Thanks,
Tapan

bug in rdf/gran

Submitted by eddie on

Hi,
Greeting,
firstly, I did not see files that looks like 'compute_rdf_gran.h and compute_rdf_gran.cpp' in the released LIGGGHTS version,
so I just created them because they are very similar to compute_rdf.h and compute_rdf.cpp. But still have bugs.
1. It seems the skin of neighbor bin is not accounted for before computing the width of the shell, though it is addressed in the manual.
2. It is safer to recount the number of particles before start calculate the g(r) for granular, since number change in the simulation box is often in granular simulation, for example, pouring.

LIGGGHTS 2.1.2 (2.1.1 and 2.06 tested): fix insert/pack error

Submitted by qfhou on

related input:
"fix ins12 all insert/pack seed 100001 distributiontemplate pdd7 vel constant 0. 0.1 -0. insert_every once overlapcheck yes all_in yes particles_in_region 3 region bc7

run 250000 upto

fix ins13 all insert/pack seed 100001 distributiontemplate pdd3 vel constant 0.1 0. -0. insert_every once overlapcheck yes all_in yes particles_in_region 3 region bc3

fix ins14 all insert/pack seed 100001 distributiontemplate pdd4 vel constant 0. 0.1 -0. insert_every once overlapcheck yes all_in yes particles_in_region 3 region bc4"

error message:

Bug when using particle type 3 walltype 2 combo

Submitted by tapsab on

This seems to be a peculiar bug which only shows up if I use a particle of type "3" and wall of type "2" in a simulation. Even if the material property for each "type" is the same the simulation will blow up. For any other combination of particle and wall type the simulation runs fine. To illustrate the case I attach a simple one particle and one wall simulation. If you run it as it is, it should blow up.

Best,
Tapan

Spurious horizontal movement with mesh walls

Submitted by tapsab on

Hi,
Sorry to flood the bug report forum. Here's a synopsis of a bug that i recently encountered that causes spurious motion of particles that interact with mesh walls. The simulation (which can be recreated using the attached files) involves just one particle falling under gravity. The particles falls down vertically on a bottom wall. I tried three different ways to model the bottom and here is a summary of what I observe in each case: