CFDEM®coupling - User Forum

When I run twoSpheresGlowinskiMPI tutorial I got a error on a reconstructPar step:
=========
--> FOAM FATAL IO ERROR:
cannot find file

file: /home/sega/CFDEM/CFDEMcoupling-PUBLIC-2.1.x/tutorials/cfdemSolverIB/twoSpheresGlowinskiMPI/CFD/processor0/0.003/polyMesh/pointProcAddressing at line 0.

From function regIOobject::readStream()
in file db/regIOobject/regIOobjectRead.C at line 73.

FOAM exiting
=========

I use OpenFOAM 2.1.x, LIGGGHTS-1.5.1 and CFDEM-2.4.1

>> on behalf of Zhen Li

Dear all,

I just tried the new version of CFDEM Coupling. It worked very well. But I have a small problem by the post processing lpp.py. I copied the lpp folder according to the guide in the LIGGGHTS folder. If i tried to convert dump file to VTK, i got such an error:
Traceback (most recent call last):
File "/home/administrator/LIGGGHTS/mylpp/src/lpp.py", line 5, in
from dump import dump
File "/home/administrator/LIGGGHTS/mylpp/src/dump.py", line 194, in
import Numeric as np
ImportError: No module named Numeric

Hello everyone,
I have installed OpenFOAM2.1.x. As per the procedure given in pdf (name of pdf file is githubAccess_public.pdf available at download section of Open source CFD-DEM), at the page number 3 of pdf at the last line it is not clear what is written, i think something is missing there.Also after executing CFDEMCompLIG (given on page 4) i am getting error of following type:
Please Help me get rid of this error.

Makefile:93: fix_wall_gran_hertz_history_simple.d: No such file or directory
Makefile:93: fix_wall_gran_hooke.d: No such file or directory

hi everybody,
I am a beginner in CFDEM coupling. I want to run my own case.How to run that case.In tutorial cases we have Allrun script, but for our own case how to do that.Plz help!
Regards
Nikhil

Hi,
I am trying to simulate the incompressible flow of water through a cylinder.The cylinder at its base have many small circular openings.I have made the mesh of required geometry through gmesh.But while executing the file in OpenFoam the courant number is becoming high.My pressure and velocity fields are as follows:

/*--------------------------------*- C++ -*----------------------------------*\
| ========= | |
| \\ / F ield | OpenFOAM: The Open Source CFD Toolbox |

Hi Christoph,

I was just wondering, is the example "test case: partly fluidized bed" included in the CFDEM tutorial folder? so that i could check the first impression of CFD-DEM coupling?

with kind regards,

David Long

Hi Friends,

Can any one please tell me the procedure to install LIGGGHTS and CFDEM in ubuntu CAE-linux-2011 ..
From past couple of days i am struggling to install this ... Please help me out of this problem..

Thanks in advance .

Best Regards,

Ravi

Dear CFDEM users,
I am using the CFDEM 2.3 and have been bothered with "Segmentation fault" errors these days. I have done a few cases using this version and it worked fine, at lest no strange errors. But recently I set up a case almost the same with the other one except for the drag force, and the "Segmentation fault" error emerged along. The case will "cash" or stop at somewhere around 0.2s whaterver I change the settings, and the output is like this:

Time = 0.17394

Courant Number mean: 0.0454717 max: 1.05449
- evolve()
Starting up LIGGGHTS
Executing command: 'run 10 '

Hi

I was wondering what the difference is between "resolved" and "unresolved" CFD-DEM? If I am correct, the solver "cfdemSolverIB" uses resolved CFD-DEM with the "immersed boundary" method.

One obvious benefit is that a finer CFD mesh can be used (smaller than the particle). This would give more accurate flow calculations, but with greater computational expense I am guessing. Is there extra computational expense, other than the extra CFD cells?

Hello,

Thanks for the new CFDEM release.
Is there a new way of running CFDEM 2.4.0 cases?
I tried to run the tutorial "ErgunTestMPI" with "mpirun -np 2 cfdemSolverPiso -parallel" but it fails due to an openmpi error:
=====================================================
--------------------------------------------------------------------------
It looks like MPI_INIT failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during MPI_INIT; some of which are due to configuration or environment