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)

fix_scalar_transport_equation: Unnecessary loop

Submitted by paul on

I stumbled over https://github.com/CFDEMproject/LIGGGHTS-PUBLIC/blob/28301df8853491784b…

for(int i=1;i< max_type+1; i++)
for(int j=1;j<max_type+1;j++)
capacity[i] = fix_capacity->compute_vector(i-1);

The loop over j is unnecessary since this is not a binary interaction parameter.

SEGMENTATION ERROR IN LIGGGHTS AFTER INSTALLING PASCAL

Submitted by yesaswi92 on

Hi,

I'm trying to install PARSCALE and re-build LIGGGHTS again. The following are the steps I followed (based on https://github.com/CFDEMproject/ParScale-PUBLIC/blob/master/src/INSTALL… and /system/files/2_usage_1_introductioninstallation.pdf)

2 mistakes in the postprocessing tools checkCouplingInterval and particleVolume

Submitted by NewUser1 on

Hello,

I think I found 2 mistakes in the CFDEM-code. They are only for postprocessing, so nothing major.

The first:
in checkCouplingInterval.C in line 226 is no radius or diameter in the code. Normally there should be a 4*radius^2, but there is only a scaleRad*scaleRad witch is -1*-1

The second:
in particleVolume.C in line 125 is a wrong equation for the volume of a sphere. It should be either pi/6*d^3 or 4pi/3*r^3. Now there is a 4pi/3*d^3

I hope this helps.

Best regards,
Dimitri

Possible bug when calling lammp_open() with certain dump styles

Submitted by frankiebetancourt on

Summary:
========
Using the lammmps_open() function on certain dump styles involving VTK causes a
deadlock.

More info:
==========
When starting liggghts with the library call lammps_open(), and using the
following dump styles,

custom/vtk
custom/vtm
local/gran/vtk
mesh/gran/vtk
mesh/vtm

causes a deadlock when the lammps_open() MPI_Comm parameter is set to anything
other than MPI_COMM_WORLD.

Segmentation fault when using -screen none

Submitted by mschramm on

Hello,
While I was running a test using python, I wanted no screen output.
I was told to use -screen none (liggghts -screen none -log none -in in.liggghts).
When doing so I received a segmentation fault error.
(I confirmed issue using the chute_wear example --> liggghts -screen none -in in.chute)

To get around this, I used -screen /dev/null

NOTE: -log none works as intended...

LIGGGHTS version
LIGGGHTS-PUBLIC 3.8.0

OS
Redhat 7

Please let me know if any other information is needed.

Thank you.