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)

Tangential damping force

Submitted by robin on

Hi to all of you,

I did a little test case for the tangential damping model. It's a pair of indented particles with only tangential damping forces.
The forces computed by ligggths are compared to the theoretical damping force, computed with the velocities. The test case is attached.

The relative error on the force given by compute pair/gran/local is machine zero, which is fine.
The relative error on the force given for the atoms is much larger, and depends on the time step.

Is something wrong with my test case? Thanks for any hints!

Cheers,

copy & paste mistake in gran_cohesion_washino_capillary_viscous

Submitted by richti83 on

typo in http://www.cfdem.com/media/DEM/docu/gran_cohesion_washino_capillary_vis…

fix id all property/global contactAngle peratomtype value_1 value_2 ...
(value_i=value for contact angle of atom type i and fluid)
fix id all property/global maxLiquidContent peratomtype value_1 value_2 ...
(value_i=value for contact angle of atom type i and fluid)

Memory Leak in InputMeshTri

Submitted by Daniel Queteschiner on

Bug: ERROR on proc 0: Illegal situation in MultiNodeMesh<NUM_NODES>::registerMove

Submitted by aquinolarosa on

Hello, Please can you kindly help me with the following:

1) I think I have a bug. I am running liggghts version 3.3.0. I see there is a previous topic posted on the same topic but my understanding is that this should have been fixed on the liggghts version 3.0.6 and versions thereafter.

"Popping" behavior (Parallelization Bug?)

Submitted by sgeerster on

Greetings, Everyone!

I think there's still a parallelization bug in LIGGGHTS-PUBLIC. The posts at /forums/bug-mesh-granular-interaction and /forums/popping-behaviour suggest the issue has been fixed. I'm having problems that seem very similar to those posts, yet I have the latest and greatest version of LIGGGHTS-PUBLIC.

I'm creating a polydisperse cloud of spherical particles in LIGGGHTS and letting them fall into a virtual Petri dish... Imagine pouring sand into a bottle cap until the bottle cap overflows, leaving a conical pile of sand in the cap.

Misleading documentation for set_property option of fix insert/*

Submitted by Daniel Queteschiner on

The manual for the fix insert/* commands is misleading when it comes to the set_property option:
set_property values = property-ID val
property-ID = ID of a fix property/atom holding a scalar value for each particle

Actually property-ID must be set to the variablename of the fix property/atom and not its ID.

Particle-wall forces for surfacesClose in cohesion models

Submitted by nasato on

Dear,

I'm trying to implement a new cohesion model, however I'm having some difficulties in particle-wall forces when there is no particle-wall collision (only proximity). It looks like, "scdata.is_wall" flag is always evaluated false for particle-wall surfacesClose, inside the cohesion model, for all cohesion models I tested.

I added a capillary/washino model with some cout statements I tested with the latest LIGGGHTS-PUBLIC version (3.3.1).

IBVoidFraction bug (w/ fix)

Submitted by Nucleophobe on

Hi again,

I have a minor bug to report for the void fraction model 'IBVoidFraction'.

If the fluid-particle interface intersects exactly with a cell center in the CFD mesh, the void fraction is not calculated correctly and is instead set to '1' (i.e., fluid). This occurs because the lambda value returned is exactly '0' (e.g., see lines 162 -- 180).