CFDEM®coupling- Developer Forum

Topics related to developing with CFDEM®coupling can be discussed here: discussion about implementation details, C++, MPI and debugging tools

Parallel problem: can't find particles crossing processors

Submitted by cheng1988sjtu on

Hi,

I'm using CFDEM coupling 3.5.1, which couples Openfoam 2.4.x and LIGGGHTS 3.5.0. and I've tried to run one settling case with 4 processors. Here is what I found that's wierd behavior:

I have 800 particles, and in the drag model, I added the following line to output the particle location :

if (index==200) //index is particle ID, it's ranging from 0 to 799, so there must be one particle index =200
{
Pout << "pos = " << particleCloud_.position(index)<<endl;
}

LIGGGHTS fix does not work in CFDEM

Submitted by RobertG on

Hello everyone,
I have a strange problem.

Based on the fixedcouple / cfd / speciesConvection in LIGGGHTS and
The solver cfdemSolverPisoSTM I wrote the functionFixedCome / cfd / reaction for LIGGGHTS.

When I run the modified in.liggghts_run file in LIGGGTS from the cfdemSolverPisoSTM tutorial,
It works fine.
But when I start the modified CFDEM solver I get the error:

ERROR: Invalid fixstyle: "couple / cfd / reaction" (../modify.cpp:826)

I did a new compilation of LIGGGHTS and CFDEM and everything.
So, I realy dont know why ...

Void fraction models (Big-particle & Divided) implemented simultaneously together in Single CFDEMcoupling Case

Submitted by ksbiefr on

Hello!

I have a very general question Specially for Developers....
Can we use two Void Fraction models (Big-particle & Divided) simultaneously together in Single CFDEMcoupling Case.
I believe that it is only possible, if two separate "couplingProperties" files (couplingProperties_Big & couplingProperties_divided) are prepared/used according to case requirements .

Please Developers correct me if i am Right ?

cellsPerParticle_

Submitted by jpola on

Hi,
Is there any particular reason that the voidFractionModel class field cellsPerParticle_ is a 2D array?

When I searched trough the whole CFDEM project it is always present in following context:

cellsPerParticle_[index][0]

except when this table is allocated:

...dataExchangeM().allocateArray(cellsPerParticle_,1,1,nP);

It is due to this function?

Thanks,
Jakub.

Coupling beetwen LIGGGHTS and Code_Aster‏

Submitted by DanielBR on

Dear all,

I am doing an analysis on LIGGGHTS, witch i am filling a geometry with particles. However, my aim is to export the results to do an non linear simulation on Code_Aster.

I believe that I need to extract the tension grid, re-programming the source code file fix_mesh_surface_stress.cpp of the LIGGGHTS.

Is this the correct way? if yes, how can I do this? If no, what is the better way to accomplish this?

Best regards,

Daniel Oliveira

a new forceModel

Submitted by yyu on

Hi CFDEMers,

I'm trying to create a new forceModel in CFDDEM. For example, forceModel Archimedes was changed a little bit to "StokesDrag". When running parCFDDEM, Error came out:

[1] Selecting forceModel StokesDrag

[1]
21

[1] --> FOAM FATAL ERROR:
[1] forceModel::New(const dictionary&, const spray&) :
unknown forceModelType type StokesDrag, constructor not in hash table

IOModel including particle temperature

Submitted by kalei on

I want to define an IO model including the particle temperature based on basicIO. To my understanding I need to extend dupDEMdata in basicIO.C in order to stream the particle temperature to a file as it is done for positions, velocities and radii:
streamDataToPath(lagPath_, particleCloud_.positions(),nPProc_,"positions","vector","Cloud","0");
streamDataToPath(lagPath_, particleCloud_.velocities(),nPProc_,"v","vector","vectorField","");
streamDataToPath(lagPath_, particleCloud_.radii(),nPProc_,"r","scalar","scalarField","");