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)

contact_distance_factor and wall temperature don't work together

Submitted by Gustavo Ruiz on

Hello,

I'm trying to use contact_distance_factor while imposing a wall temperature, but it doesn't calculate the particles temperature (nor hettran) instead "-nan" appears.

I tried modifying the example "in.heatGran" (attached) by adding contact_distance_factor and wall temperature and the same thing happened.

Do you have any idea how I can solve it?

I hope you can help me.

Best regards.

Bug in Makefile.shlib when compiling for the python wrapper

Submitted by AndresMM on

Intro to the problem: /forums/python-interface-liggghts-using-auto-makefile

TL;DR: I want to compile the python wrapper for liggghts using the auto make file.
The commands:

make makeshlib
make -f Makefile.shlib auto

Do not work. The make tries to work in Obj_auto and not in Obj_shlib_auto as it should.

The bug itself lies in the Makefile.shlib, originally it reads:

compute rigid is missing compute_array() method

Submitted by richti83 on

I found when using compute rigid and variable c_ID[body][dim] and than printing the variable to file the data is not updated. As variable.cpp calls compute->compute_array() there should be a method in compute_rigid.cpp which calls update_pointers().
Best,
Christian.

Compilation with JPG support: test in Makefile.auto

Submitted by JoG on

The new Makefile.auto in Version 3.7.0 is quite useful.

However, I could not compile with jpeg support as before with version 3.4.1 even though I was pretty sure I gave the right paths for the include and the library. The test for the jpeg environment in Makefile.auto around line 750 failed every time.

Since I was pretty sure I set the right paths, I removed the test from Makefile.auto and tried to compile again - then it worked as expected and I can dump .jpg files of my particles now.

fix move all move/mesh viblin

Submitted by JoG on

I updated my LIGGGHTS version from 3.4.1 to 3.7.0. I can run my cases as usual. However, in some cases I use the command

fix move all move/mesh mesh plateMesh viblin axis -1. 0 0 order 6 amplitude 9.1921529142e-03 3.9214650496e-03 3.5675133623e-03 1.7885852357e-03 1.0341196266e-03 2.1750110172e-04 phase -1.1178244768e+00 -2.5012171783e+00 1.0835842279e+00 -2.7415575968e+00 -3.4168127884e+00 1.5499497574e+00 period 5.4625439049e+02 3.7999999186e-01 2.9650316014e+02 1.8999999621e-01 1.2666668904e-01 1.2924680176e+02

Bug when inserting particle size distribution

Submitted by Matteo on

Hello,

As reported here
/forums/different-particle-size-distribution-between-input-file-and-output-file-smallest-particles#comment-18389

It seems that LIGGGHTS is not able to insert the required mass of spherical particles when specifying a particle distribution using
particledistribution/discrete/numberbased

Comparing the particle distribution expected with the one in the output file it is possible to notice an important shift in the mean value.
Moreover LIGGGHTS seems to insert much more mass than the one required.

Best regards
Matteo

Mei lift force

Submitted by Daniel Queteschiner on

I think there is a mistake in the implementation of the Mei lift force (and the paper of Kurose and Komori, Eq. 3.7), when I compare the function to the original data of McLaughlin 1991. Unfortunately, in the original paper of Mei 1992, a left parenthesis seems to be missing in the corresponding Eq 10, but it is there in Mei and Klausner 1994 (Eq 17), as well as in Loth and Dorgan 2009 (Eq 32).

coupling aborted due to timeStepFraction > 1

Submitted by gelinhan on

Hi everyone,

I'm simulating a simple solid-liquid fluidized bed case using cfdemSolverPiso. The coupling interval is specified as 1 which results in a CFD time step 1e-5 and DEM time step 1e-5. Everything went well at the begin until the simulation aborted at somewhere between 35s and 36s and gave fatal error as:

"cfdemCloud::dataExchangeM().timeStepFraction()>1:Do not do this, since dangerous. This might be due to the fact that you used an adjustable CFD time step. Please use a fixed CFD time step."