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 MeshMoverLinearVariable

Submitted by R Schubert on

The constructor of MeshMoverLinearVariable (mesh_mover.cpp:117) starts

int n;
n = strlen(&var1[2]) + 1;
var1str_ = new char[n];
strcpy(var1str_,&var1[2]);
myvar1_ = input->variable->find(var1str_);

n = strlen(&var1[2]) + 1;
var2str_ = new char[n];
strcpy(var2str_,&var2[2]);
myvar2_ = input->variable->find(var2str_);

Force on mesh not consistent

Submitted by jlstrom on

I have a case that involves pulling a meshed rod through a bed of material that is loaded from an input file, not a restart file. When I change the number of processor divisions used the results of the force on the rod at the final state are significantly different. I have tried this with V3.10, 3.21 and 3.30, all have similar results. The only change to the input script was the number of processors alotted.

1 processor final force was -29.98 N
2 processors final force was -23.14 N
3 processors final force was -19.04 N

VTK parser of InputMeshTri is broken

Submitted by Daniel Queteschiner on

In InputMeshTri::meshtrifile_vtk
https://github.com/CFDEMproject/LIGGGHTS-PUBLIC/blob/3.2.1/src/input_me…

The line counter is off by one due to skipping of the first line in the VTK file.
The check for the line 'DATASET UNSTRUCTURED_GRID' is wrong.
(see InputMeshTet for working version)

cfdemSolverIB bug - force calculation on non-uniform meshes is incorrect

Submitted by Nucleophobe on

Greetings,

Over the past few months, I have been experimenting with the fictitious domain solver 'cfdemSolverIB' and have discovered a few bugs / limitations (CFDEMcoupling v. 2.7.1). I realize the solver is experimental, but I thought I'd share what I've found to raise awareness for new users and to identify areas for future development.

From my experience, as implemented, the fictitious domain solver cfdemSolverIB does not appropriately handle force calculations when the immersed particle occupies cells with differing cell volumes.

CFDEMcoupling on cluster: "MPI_Comm_rank() function was called before MPI_INIT was invoked"

Submitted by Swantje on

Hi,

I've installed LIGGGHTS-PUBLIC as well as CFDEMcoupling-PUBLIC from git using openmpi 1.8.4 and OpenFOAM 2.3.1 on a RHEL 6-cluster.

Running LIGGGHTS and OpenFOAM individually works fine. However, running CFDEM cases using cfdemSolverPiso fails, resulting in the following error messages.

Reading g
Selecting incompressible transport model Newtonian
Selecting turbulence model type RASModel
Selecting RAS turbulence model laminar
Selecting locateModel engine
Selecting dataExchangeModel twoWayMPI
Starting up LIGGGHTS for first time execution

fix ave/euler

Submitted by Daniel Queteschiner on

The average velocity gets divided by the number of particles, but it also gets divided by the sum of particle masses. That's too much, hence
https://github.com/CFDEMproject/LIGGGHTS-PUBLIC/blob/master/src/fix_ave…
if(ncount_[icell]) vectorScalarDiv3D(v_av_[icell],static_cast<double>(ncount_[icell])*mass_[icell]);
should read
if(mass_[icell] > 0.) vectorScalarDiv3D(v_av_[icell],mass_[icell]);

first step installation of CFDM coupling

Submitted by naceur on

Hello everybody

I followed the installation instructions step by step

and run cfdemSysTest

and here is what I get

*********************************************
* C F D E M (R) c o u p l i n g *
* *
* by DCS Computing GmbH *
* www.dcs-computing.com *
*********************************************

cfdemSolverPiso: Foam::sigSegv

Submitted by naukkarinen on

Hey,

I have a case where I get segmentation violation when LIGGGHTS is started up after solving flow. First I was wondering am I losing particles through some wall but I think it is not the case. The end of the normal log and error log are in the attachment.