ICODE-ADC/CFDEMcoupling-PUBLIC
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

release on 2012-06-06_09-48-35

Browse Source
This commit is contained in:
cfdem
2012-06-06 09:48:35 +02:00
commit d40620a9a5
439 changed files with 35136 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

0
README Normal file
View File

3
applications/solvers/cfdemSolverIB/Make/files Executable file
View File

@ -0,0 +1,3 @@
cfdemSolverIB.C
EXE=$(FOAM_USER_APPBIN)/cfdemSolverIB

20
applications/solvers/cfdemSolverIB/Make/options Executable file
View File

@ -0,0 +1,20 @@
EXE_INC = \
-I$(LIB_SRC)/turbulenceModels/incompressible/turbulenceModel \
-I$(LIB_SRC)/transportModels \
-I$(LIB_SRC)/transportModels/incompressible/singlePhaseTransportModel \
-I$(LIB_SRC)/finiteVolume/lnInclude \
-I$(CFDEM_SRC_DIR)/lnInclude \
-I$(LIB_SRC)/dynamicFvMesh/lnInclude \
-I$(LIB_SRC)/dynamicMesh/lnInclude \
-I$(LIB_SRC)/dynamicMesh/dynamicFvMesh/lnInclude \
-I$(LIB_SRC)/dynamicMesh/dynamicMesh/lnInclude
EXE_LIBS = \
-L$(FOAM_USER_LIBBIN)\
-lincompressibleRASModels \
-lincompressibleLESModels \
-lincompressibleTransportModels \
-lfiniteVolume \
-ldynamicFvMesh \
-ldynamicMesh \
-l$(CFDEM_LIB_NAME)

175
applications/solvers/cfdemSolverIB/cfdemSolverIB.C Executable file
View File

@ -0,0 +1,175 @@
/*---------------------------------------------------------------------------*\
CFDEMcoupling - Open Source CFD-DEM coupling
CFDEMcoupling is part of the CFDEMproject
www.cfdem.com
Christoph Goniva, christoph.goniva@cfdem.com
Copyright (C) 1991-2009 OpenCFD Ltd.
Copyright (C) 2009-2012 JKU, Linz
Copyright (C) 2012- DCS Computing GmbH,Linz
-------------------------------------------------------------------------------
License
This file is part of CFDEMcoupling.
CFDEMcoupling is free software: you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
CFDEMcoupling is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
for more details.
You should have received a copy of the GNU General Public License
along with CFDEMcoupling. If not, see <http://www.gnu.org/licenses/>.
Application
cfdemSolverIB
Description
Transient solver for incompressible flow.
The code is an evolution of the solver pisoFoam in OpenFOAM 1.6,
where additional functionality for CFD-DEM coupling using immersed body
(fictitious domain) method is added.
Contributions
Alice Hager
\*---------------------------------------------------------------------------*/
#include "fvCFD.H"
#include "singlePhaseTransportModel.H"
#include "turbulenceModel.H"
#include "cfdemCloudIB.H"
#include "implicitCouple.H"
#include "averagingModel.H"
#include "regionModel.H"
#include "voidFractionModel.H"
#include "dynamicFvMesh.H" //dyM
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
int main(int argc, char *argv[])
{
#include "setRootCase.H"
#include "createTime.H"
#include "createDynamicFvMesh.H"
#include "createFields.H"
#include "initContinuityErrs.H"
// create cfdemCloud
#include "readGravitationalAcceleration.H"
cfdemCloudIB particleCloud(mesh);
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Info<< "\nStarting time loop\n" << endl;
while (runTime.loop())
{
Info<< "Time = " << runTime.timeName() << nl << endl;
//=== dyM ===================
interFace = mag(mesh.lookupObject<volScalarField>("voidfractionNext"));
mesh.update(); //dyM
#include "readPISOControls.H"
#include "CourantNo.H"
// do particle stuff
Info << "- evolve()" << endl;
particleCloud.evolve();
// Pressure-velocity PISO corrector
{
// Momentum predictor
fvVectorMatrix UEqn
(
fvm::ddt(U)
+ fvm::div(phi, U)
+ turbulence->divDevReff(U)
);
UEqn.relax();
if (momentumPredictor)
{
solve(UEqn == -fvc::grad(p));
}
// --- PISO loop
for (int corr=0; corr<nCorr; corr++)
{
volScalarField rUA = 1.0/UEqn.A();
U = rUA*UEqn.H();
phi = (fvc::interpolate(U) & mesh.Sf())
+ fvc::ddtPhiCorr(rUA, U, phi);
adjustPhi(phi, U, p);
// Non-orthogonal pressure corrector loop
for (int nonOrth=0; nonOrth<=nNonOrthCorr; nonOrth++)
{
// Pressure corrector
fvScalarMatrix pEqn
(
fvm::laplacian(rUA, p) == fvc::div(phi)
);
pEqn.setReference(pRefCell, pRefValue);
if
(
corr == nCorr-1
&& nonOrth == nNonOrthCorr
)
{
pEqn.solve(mesh.solver("pFinal"));
}
else
{
pEqn.solve();
}
if (nonOrth == nNonOrthCorr)
{
phi -= pEqn.flux();
}
}
#include "continuityErrs.H"
U -= rUA*fvc::grad(p);
U.correctBoundaryConditions();
}
}
turbulence->correct();
Info << "particleCloud.calcVelocityCorrection() " << endl;
particleCloud.calcVelocityCorrection(p,U,phiIB);
runTime.write();
Info<< "ExecutionTime = " << runTime.elapsedCpuTime() << " s"
<< " ClockTime = " << runTime.elapsedClockTime() << " s"
<< nl << endl;
}
Info<< "End\n" << endl;
return 0;
}
// ************************************************************************* //

128
applications/solvers/cfdemSolverIB/createFields.H Executable file
View File

@ -0,0 +1,128 @@
Info<< "Reading field p\n" << endl;
volScalarField p
(
IOobject
(
"p",
runTime.timeName(),
mesh,
IOobject::MUST_READ,
IOobject::AUTO_WRITE
),
mesh
);
Info<< "Reading physical velocity field U" << endl;
Info<< "Note: only if voidfraction at boundary is 1, U is superficial velocity!!!\n" << endl;
volVectorField U
(
IOobject
(
"U",
runTime.timeName(),
mesh,
IOobject::MUST_READ,
IOobject::AUTO_WRITE
),
mesh
);
//mod by alice
Info<< "Reading physical velocity field U" << endl;
Info<< "Note: only if voidfraction at boundary is 1, U is superficial velocity!!!\n" << endl;
volVectorField Us
(
IOobject
(
"Us",
runTime.timeName(),
mesh,
IOobject::MUST_READ,
IOobject::AUTO_WRITE
),
mesh
);
//========================
// drag law modelling
//========================
Info<< "\nCreating dummy density field rho = 1\n" << endl;
volScalarField rho
(
IOobject
(
"rho",
runTime.timeName(),
mesh,
IOobject::READ_IF_PRESENT,
IOobject::AUTO_WRITE
),
mesh,
dimensionedScalar("0", dimensionSet(1, -3, 0, 0, 0), 1.0)
);
Info<< "Reading field phiIB\n" << endl;
volScalarField phiIB
(
IOobject
(
"phiIB",
runTime.timeName(),
mesh,
IOobject::MUST_READ,
IOobject::AUTO_WRITE
),
mesh
);
//mod by alice
Info<< "Reading field phiIB\n" << endl;
volScalarField voidfraction
(
IOobject
(
"voidfraction",
runTime.timeName(),
mesh,
IOobject::MUST_READ,
IOobject::AUTO_WRITE
),
mesh
);
//========================
# include "createPhi.H"
label pRefCell = 0;
scalar pRefValue = 0.0;
setRefCell(p, mesh.solutionDict().subDict("PISO"), pRefCell, pRefValue);
singlePhaseTransportModel laminarTransport(U, phi);
autoPtr<incompressible::turbulenceModel> turbulence
(
incompressible::turbulenceModel::New(U, phi, laminarTransport)
);
//=== dyM ===================
Info<< "Reading field interFace\n" << endl;
volScalarField interFace
(
IOobject
(
"interFace",
runTime.timeName(),
mesh,
IOobject::READ_IF_PRESENT,
IOobject::AUTO_WRITE
),
mesh,
//dimensionedScalar("0", dimensionSet(0, -1, 0, 0, 0), 0.0)
dimensionedScalar("0", dimensionSet(0, 0, 0, 0, 0), 0.0)
);
//===========================

3
applications/solvers/cfdemSolverPiso/Make/files Normal file
View File

@ -0,0 +1,3 @@
cfdemSolverPiso.C
EXE=$(FOAM_USER_APPBIN)/cfdemSolverPiso

15
applications/solvers/cfdemSolverPiso/Make/options Normal file
View File

@ -0,0 +1,15 @@
EXE_INC = \
-I$(LIB_SRC)/turbulenceModels/incompressible/turbulenceModel \
-I$(LIB_SRC)/transportModels \
-I$(LIB_SRC)/transportModels/incompressible/singlePhaseTransportModel \
-I$(LIB_SRC)/finiteVolume/lnInclude \
-I$(CFDEM_SRC_DIR)/lnInclude \
-I$(CFDEM_SRC_DIR)/cfdTools \
EXE_LIBS = \
-L$(FOAM_USER_LIBBIN)\
-lincompressibleRASModels \
-lincompressibleLESModels \
-lincompressibleTransportModels \
-lfiniteVolume \
-l$(CFDEM_LIB_NAME)

196
applications/solvers/cfdemSolverPiso/cfdemSolverPiso.C Normal file
View File

@ -0,0 +1,196 @@
/*---------------------------------------------------------------------------*\
CFDEMcoupling - Open Source CFD-DEM coupling
CFDEMcoupling is part of the CFDEMproject
www.cfdem.com
Christoph Goniva, christoph.goniva@cfdem.com
Copyright (C) 1991-2009 OpenCFD Ltd.
Copyright (C) 2009-2012 JKU, Linz
Copyright (C) 2012- DCS Computing GmbH,Linz
-------------------------------------------------------------------------------
License
This file is part of CFDEMcoupling.
CFDEMcoupling is free software: you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
CFDEMcoupling is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
for more details.
You should have received a copy of the GNU General Public License
along with CFDEMcoupling. If not, see <http://www.gnu.org/licenses/>.
Application
cfdemSolverPiso
Description
Transient solver for incompressible flow.
Turbulence modelling is generic, i.e. laminar, RAS or LES may be selected.
The code is an evolution of the solver pisoFoam in OpenFOAM 1.6,
where additional functionality for CFD-DEM coupling is added.
\*---------------------------------------------------------------------------*/
#include "fvCFD.H"
#include "singlePhaseTransportModel.H"
#include "turbulenceModel.H"
#include "cfdemCloud.H"
#include "implicitCouple.H"
#include "clockModel.H"
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
int main(int argc, char *argv[])
{
#include "setRootCase.H"
#include "createTime.H"
#include "createMesh.H"
#include "createFields.H"
#include "initContinuityErrs.H"
// create cfdemCloud
#include "readGravitationalAcceleration.H"
cfdemCloud particleCloud(mesh);
#include "checkModelType.H"
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Info<< "\nStarting time loop\n" << endl;
particleCloud.clockM().start(1,"Global");
while (runTime.loop())
{
Info<< "Time = " << runTime.timeName() << nl << endl;
#include "readPISOControls.H"
#include "CourantNo.H"
// do particle stuff
particleCloud.clockM().start(2,"Coupling");
Info << "- evolve()" << endl;
particleCloud.evolve(voidfraction,Us,U);
Info << "update Ksl.internalField()" << endl;
Ksl.internalField() = particleCloud.momCoupleM(0).impMomSource();
Ksl.correctBoundaryConditions();
#include "solverDebugInfo.H"
particleCloud.clockM().stop("Coupling");
particleCloud.clockM().start(10,"Flow");
// Pressure-velocity PISO corrector
{
// Momentum predictor
fvVectorMatrix UEqn
(
fvm::ddt(voidfraction,U)
+ fvm::div(phi, U)
// + turbulence->divDevReff(U)
+ particleCloud.divVoidfractionTau(U, voidfraction)
==
- fvm::Sp(Ksl/rho,U)
);
UEqn.relax();
if (momentumPredictor)
{
//solve UEqn
if (modelType=="B")
solve(UEqn == - fvc::grad(p) + Ksl/rho*Us);
else
solve(UEqn == - voidfraction*fvc::grad(p) + Ksl/rho*Us);
}
// --- PISO loop
//for (int corr=0; corr<nCorr; corr++)
int nCorrSoph = nCorr + 5 * pow((1-particleCloud.dataExchangeM().timeStepFraction()),1);
Info << "nCorrSoph = " << nCorrSoph << endl;
Info << "particleCloud.dataExchangeM().timeStepFraction() = " << particleCloud.dataExchangeM().timeStepFraction() << endl;
for (int corr=0; corr<nCorrSoph; corr++)
{
volScalarField rUA = 1.0/UEqn.A();
surfaceScalarField rUAf("(1|A(U))", fvc::interpolate(rUA));
U = rUA*UEqn.H();
phi = fvc::interpolate(U*voidfraction) & mesh.Sf();
//+ fvc::ddtPhiCorr(rUA, U, phi)
surfaceScalarField phiS(fvc::interpolate(Us*voidfraction) & mesh.Sf());
surfaceScalarField phiGes = phi + rUAf*(fvc::interpolate(Ksl/rho) * phiS);
volScalarField rUAvoidfraction("(voidfraction2|A(U))",rUA*voidfraction);
if (modelType=="A")
rUAvoidfraction = volScalarField("(voidfraction2|A(U))",rUA*voidfraction*voidfraction);
// Non-orthogonal pressure corrector loop
for (int nonOrth=0; nonOrth<=nNonOrthCorr; nonOrth++)
{
// Pressure corrector
fvScalarMatrix pEqn
(
fvm::laplacian(rUAvoidfraction, p) == fvc::div(phiGes) + fvc::ddt(voidfraction)
);
pEqn.setReference(pRefCell, pRefValue);
if
(
corr == nCorr-1
&& nonOrth == nNonOrthCorr
)
{
pEqn.solve(mesh.solver("pFinal"));
}
else
{
pEqn.solve();
}
if (nonOrth == nNonOrthCorr)
{
phiGes -= pEqn.flux();
}
} // end non-orthogonal corrector loop
#include "continuityErrs.H"
if (modelType=="B")
U -= rUA*fvc::grad(p) - Ksl/rho*Us*rUA;
else
U -= voidfraction*rUA*fvc::grad(p) - Ksl/rho*Us*rUA;
U.correctBoundaryConditions();
} // end piso loop
}
turbulence->correct();
runTime.write();
Info<< "ExecutionTime = " << runTime.elapsedCpuTime() << " s"
<< " ClockTime = " << runTime.elapsedClockTime() << " s"
<< nl << endl;
particleCloud.clockM().stop("Flow");
}
Info<< "End\n" << endl;
particleCloud.clockM().stop("Global");
return 0;
}
// ************************************************************************* //

124
applications/solvers/cfdemSolverPiso/createFields.H Normal file
View File

@ -0,0 +1,124 @@
Info<< "Reading field p\n" << endl;
volScalarField p
(
IOobject
(
"p",
runTime.timeName(),
mesh,
IOobject::MUST_READ,
IOobject::AUTO_WRITE
),
mesh
);
Info<< "Reading physical velocity field U" << endl;
Info<< "Note: only if voidfraction at boundary is 1, U is superficial velocity!!!\n" << endl;
volVectorField U
(
IOobject
(
"U",
runTime.timeName(),
mesh,
IOobject::MUST_READ,
IOobject::AUTO_WRITE
),
mesh
);
//===============================
// particle interaction modelling
//===============================
Info<< "\nReading momentum exchange field Ksl\n" << endl;
volScalarField Ksl
(
IOobject
(
"Ksl",
runTime.timeName(),
mesh,
IOobject::MUST_READ,
IOobject::AUTO_WRITE
),
mesh
//dimensionedScalar("0", dimensionSet(1, -3, -1, 0, 0), 1.0)
);
Info<< "\nReading voidfraction field voidfraction = (Vgas/Vparticle)\n" << endl;
volScalarField voidfraction
(
IOobject
(
"voidfraction",
runTime.timeName(),
mesh,
IOobject::MUST_READ,
IOobject::AUTO_WRITE
),
mesh
);
Info<< "\nCreating dummy density field rho\n" << endl;
volScalarField rho
(
IOobject
(
"rho",
runTime.timeName(),
mesh,
IOobject::MUST_READ,
IOobject::AUTO_WRITE
),
mesh//,
//dimensionedScalar("0", dimensionSet(1, -3, 0, 0, 0), 1.0)
);
Info<< "Reading particle velocity field Us\n" << endl;
volVectorField Us
(
IOobject
(
"Us",
runTime.timeName(),
mesh,
IOobject::MUST_READ,
IOobject::AUTO_WRITE
),
mesh
);
//===============================
//# include "createPhi.H"
#ifndef createPhi_H
#define createPhi_H
Info<< "Reading/calculating face flux field phi\n" << endl;
surfaceScalarField phi
(
IOobject
(
"phi",
runTime.timeName(),
mesh,
IOobject::READ_IF_PRESENT,
IOobject::AUTO_WRITE
),
linearInterpolate(U*voidfraction) & mesh.Sf()
);
#endif
label pRefCell = 0;
scalar pRefValue = 0.0;
setRefCell(p, mesh.solutionDict().subDict("PISO"), pRefCell, pRefValue);
singlePhaseTransportModel laminarTransport(U, phi);
autoPtr<incompressible::turbulenceModel> turbulence
(
incompressible::turbulenceModel::New(U, phi, laminarTransport)
);

3
applications/solvers/cfdemSolverPisoScalar/Make/files Normal file
View File

@ -0,0 +1,3 @@
cfdemSolverPisoScalar.C
EXE = $(FOAM_USER_APPBIN)/cfdemSolverPisoScalar

15
applications/solvers/cfdemSolverPisoScalar/Make/options Normal file
View File

@ -0,0 +1,15 @@
EXE_INC = \
-I$(LIB_SRC)/turbulenceModels/incompressible/turbulenceModel \
-I$(LIB_SRC)/transportModels \
-I$(LIB_SRC)/transportModels/incompressible/singlePhaseTransportModel \
-I$(LIB_SRC)/finiteVolume/lnInclude \
-I$(CFDEM_SRC_DIR)/lnInclude \
-I$(CFDEM_SRC_DIR)/cfdTools \
EXE_LIBS = \
-L$(FOAM_USER_LIBBIN)\
-lincompressibleRASModels \
-lincompressibleLESModels \
-lincompressibleTransportModels \
-lfiniteVolume \
-l$(CFDEM_LIB_NAME)

197
applications/solvers/cfdemSolverPisoScalar/cfdemSolverPisoScalar.C Normal file
View File

@ -0,0 +1,197 @@
/*---------------------------------------------------------------------------*\
CFDEMcoupling - Open Source CFD-DEM coupling
CFDEMcoupling is part of the CFDEMproject
www.cfdem.com
Christoph Goniva, christoph.goniva@cfdem.com
Copyright (C) 1991-2009 OpenCFD Ltd.
Copyright (C) 2009-2012 JKU, Linz
Copyright (C) 2012- DCS Computing GmbH,Linz
-------------------------------------------------------------------------------
License
This file is part of CFDEMcoupling.
CFDEMcoupling is free software: you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
CFDEMcoupling is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
for more details.
You should have received a copy of the GNU General Public License
along with CFDEMcoupling. If not, see <http://www.gnu.org/licenses/>.
Application
cfdemSolverPisoScalar
Description
Transient solver for incompressible flow.
Turbulence modelling is generic, i.e. laminar, RAS or LES may be selected.
The code is an evolution of the solver pisoFoam in OpenFOAM 1.6,
where additional functionality for CFD-DEM coupling is added.
\*---------------------------------------------------------------------------*/
#include "fvCFD.H"
#include "singlePhaseTransportModel.H"
#include "turbulenceModel.H"
#include "cfdemCloud.H"
#include "implicitCouple.H"
#include "forceModel.H"
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
int main(int argc, char *argv[])
{
#include "setRootCase.H"
#include "createTime.H"
#include "createMesh.H"
#include "createFields.H"
#include "initContinuityErrs.H"
// create cfdemCloud
#include "readGravitationalAcceleration.H"
cfdemCloud particleCloud(mesh);
#include "checkModelType.H"
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Info<< "\nStarting time loop\n" << endl;
while (runTime.loop())
{
Info<< "Time = " << runTime.timeName() << nl << endl;
#include "readPISOControls.H"
#include "CourantNo.H"
// do particle stuff
Info << "- evolve()" << endl;
particleCloud.evolve(voidfraction,Us,U);
Ksl.internalField() = particleCloud.momCoupleM(0).impMomSource();
Ksl.correctBoundaryConditions();
#include "solverDebugInfo.H"
// get scalar source from DEM
particleCloud.forceM(1).manipulateScalarField(Tsource);
Tsource.correctBoundaryConditions();
// solve scalar transport equation
phi = fvc::interpolate(U*voidfraction) & mesh.Sf();
solve
(
fvm::ddt(voidfraction,T)
+ fvm::div(phi, T)
- fvm::laplacian(DT*voidfraction, T)
==
Tsource
);
// Pressure-velocity PISO corrector
{
// Momentum predictor
fvVectorMatrix UEqn
(
fvm::ddt(voidfraction,U)
+ fvm::div(phi, U)
+ turbulence->divDevReff(U)
==
- fvm::Sp(Ksl/rho,U)
);
UEqn.relax();
if (momentumPredictor)
{
//solve UEqn
if (modelType=="B")
solve(UEqn == - fvc::grad(p) + Ksl/rho*Us);
else
solve(UEqn == - voidfraction*fvc::grad(p) + Ksl/rho*Us);
}
// --- PISO loop
//for (int corr=0; corr<nCorr; corr++)
int nCorrSoph = nCorr + 5 * pow((1-particleCloud.dataExchangeM().timeStepFraction()),1);
for (int corr=0; corr<nCorrSoph; corr++)
{
volScalarField rUA = 1.0/UEqn.A();
surfaceScalarField rUAf("(1|A(U))", fvc::interpolate(rUA));
U = rUA*UEqn.H();
phi = fvc::interpolate(U*voidfraction) & mesh.Sf();
//+ fvc::ddtPhiCorr(rUA, U, phi)
surfaceScalarField phiS(fvc::interpolate(Us*voidfraction) & mesh.Sf());
surfaceScalarField phiGes = phi + rUAf*(fvc::interpolate(Ksl/rho) * phiS);
volScalarField rUAvoidfraction("(voidfraction2|A(U))",rUA*voidfraction);
if (modelType=="A")
rUAvoidfraction = volScalarField("(voidfraction2|A(U))",rUA*voidfraction*voidfraction);
// Non-orthogonal pressure corrector loop
for (int nonOrth=0; nonOrth<=nNonOrthCorr; nonOrth++)
{
// Pressure corrector
fvScalarMatrix pEqn
(
fvm::laplacian(rUAvoidfraction, p) == fvc::div(phiGes) + fvc::ddt(voidfraction)
);
pEqn.setReference(pRefCell, pRefValue);
if
(
corr == nCorr-1
&& nonOrth == nNonOrthCorr
)
{
pEqn.solve(mesh.solver("pFinal"));
}
else
{
pEqn.solve();
}
if (nonOrth == nNonOrthCorr)
{
phiGes -= pEqn.flux();
}
} // end non-orthogonal corrector loop
#include "continuityErrs.H"
if (modelType=="B")
U -= rUA*fvc::grad(p) - Ksl/rho*Us*rUA;
else
U -= voidfraction*rUA*fvc::grad(p) - Ksl/rho*Us*rUA;
U.correctBoundaryConditions();
} // end piso loop
}
turbulence->correct();
runTime.write();
Info<< "ExecutionTime = " << runTime.elapsedCpuTime() << " s"
<< " ClockTime = " << runTime.elapsedClockTime() << " s"
<< nl << endl;
}
Info<< "End\n" << endl;
return 0;
}
// ************************************************************************* //

174
applications/solvers/cfdemSolverPisoScalar/createFields.H Normal file
View File

@ -0,0 +1,174 @@
Info<< "Reading field p\n" << endl;
volScalarField p
(
IOobject
(
"p",
runTime.timeName(),
mesh,
IOobject::MUST_READ,
IOobject::AUTO_WRITE
),
mesh
);
Info<< "Reading physical velocity field U" << endl;
Info<< "Note: only if voidfraction at boundary is 1, U is superficial velocity!!!\n" << endl;
volVectorField U
(
IOobject
(
"U",
runTime.timeName(),
mesh,
IOobject::MUST_READ,
IOobject::AUTO_WRITE
),
mesh
);
//========================
// drag law modelling
//========================
Info<< "\nReading momentum exchange field Ksl\n" << endl;
volScalarField Ksl
(
IOobject
(
"Ksl",
runTime.timeName(),
mesh,
IOobject::MUST_READ,
IOobject::AUTO_WRITE
),
mesh
//dimensionedScalar("0", dimensionSet(0, 0, -1, 0, 0), 1.0)
);
Info<< "\nReading voidfraction field voidfraction = (Vgas/Vparticle)\n" << endl;
volScalarField voidfraction
(
IOobject
(
"voidfraction",
runTime.timeName(),
mesh,
IOobject::MUST_READ,
IOobject::AUTO_WRITE
),
mesh
);
Info<< "\nCreating density field rho\n" << endl;
volScalarField rho
(
IOobject
(
"rho",
runTime.timeName(),
mesh,
IOobject::READ_IF_PRESENT,
IOobject::AUTO_WRITE
),
mesh,
dimensionedScalar("0", dimensionSet(1, -3, 0, 0, 0), 1.0)
);
Info<< "Reading particle velocity field Us\n" << endl;
volVectorField Us
(
IOobject
(
"Us",
runTime.timeName(),
mesh,
IOobject::MUST_READ,
IOobject::AUTO_WRITE
),
mesh
);
//========================
// scalar field modelling
//========================
Info<< "\nCreating dummy density field rho = 1\n" << endl;
volScalarField T
(
IOobject
(
"T",
runTime.timeName(),
mesh,
IOobject::MUST_READ,
IOobject::AUTO_WRITE
),
mesh//,
//dimensionedScalar("0", dimensionSet(0, 0, -1, 1, 0), 273.15)
);
Info<< "\nCreating fluid-particle heat flux field\n" << endl;
volScalarField Tsource
(
IOobject
(
"Tsource",
runTime.timeName(),
mesh,
IOobject::MUST_READ,
IOobject::AUTO_WRITE
),
mesh//,
//dimensionedScalar("0", dimensionSet(0, 0, -1, 1, 0), 0.0)
);
IOdictionary transportProperties
(
IOobject
(
"transportProperties",
runTime.constant(),
mesh,
IOobject::MUST_READ,
IOobject::NO_WRITE
)
);
dimensionedScalar DT
(
transportProperties.lookup("DT")
);
//========================
//# include "createPhi.H"
#ifndef createPhi_H
#define createPhi_H
Info<< "Reading/calculating face flux field phi\n" << endl;
surfaceScalarField phi
(
IOobject
(
"phi",
runTime.timeName(),
mesh,
IOobject::READ_IF_PRESENT,
IOobject::AUTO_WRITE
),
linearInterpolate(U*voidfraction) & mesh.Sf()
);
#endif
label pRefCell = 0;
scalar pRefValue = 0.0;
setRefCell(p, mesh.solutionDict().subDict("PISO"), pRefCell, pRefValue);
singlePhaseTransportModel laminarTransport(U, phi);
autoPtr<incompressible::turbulenceModel> turbulence
(
incompressible::turbulenceModel::New(U, phi, laminarTransport)
);

3
applications/utilities/cfdemPostproc/Make/files Normal file
View File

@ -0,0 +1,3 @@
cfdemPostproc.C
EXE=$(FOAM_USER_APPBIN)/cfdemPostproc

17
applications/utilities/cfdemPostproc/Make/options Normal file
View File

@ -0,0 +1,17 @@
EXE_INC = \
-I$(LIB_SRC)/turbulenceModels/incompressible/turbulenceModel \
-I$(LIB_SRC)/transportModels \
-I$(LIB_SRC)/transportModels/incompressible/singlePhaseTransportModel \
-I$(LIB_SRC)/finiteVolume/lnInclude \
-I$(CFDEM_SRC_DIR)/lnInclude \
-I$(LIB_SRC)/meshTools/lnInclude \
EXE_LIBS = \
-L$(FOAM_USER_LIBBIN)\
-lincompressibleRASModels \
-lincompressibleLESModels \
-lincompressibleTransportModels \
-lfiniteVolume \
-l$(CFDEM_LIB_NAME) \

137
applications/utilities/cfdemPostproc/cfdemPostproc.C Normal file
View File

@ -0,0 +1,137 @@
/*---------------------------------------------------------------------------*\
========= |
\\ / F ield | OpenFOAM: The Open Source CFD Toolbox
\\ / O peration |
\\ / A nd | Copyright (C) 1991-2009 OpenCFD Ltd.
\\/ M anipulation |
-------------------------------------------------------------------------------
License
This file is part of OpenFOAM.
OpenFOAM is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version.
OpenFOAM is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
for more details.
You should have received a copy of the GNU General Public License
along with OpenFOAM; if not, write to the Free Software Foundation,
Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
Application
cfdemPostproc
Description
Tool for DEM->CFD (Lagrange->Euler) mapping to calculate local voidfraction
\*---------------------------------------------------------------------------*/
#include "fvCFD.H"
#include "singlePhaseTransportModel.H"
#include "turbulenceModel.H"
#include "cfdemCloud.H"
#include "dataExchangeModel.H"
#include "voidFractionModel.H"
#include "regionModel.H"
#include "locateModel.H"
#include "averagingModel.H"
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
int main(int argc, char *argv[])
{
#include "setRootCase.H"
#include "createTime.H"
#include "createMesh.H"
#include "createFields.H"
// create cfdemCloud
cfdemCloud particleCloud(mesh);
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * //
Info<< "\nStarting time loop\n" << endl;
int count=0;
double **positions_;
double **velocities_;
double **radii_;
double **voidfractions_;
double **particleWeights_;
double **particleVolumes_;
double **cellIDs_;
particleCloud.dataExchangeM().allocateArray(positions_,0.,3);
particleCloud.dataExchangeM().allocateArray(velocities_,0.,3);
particleCloud.dataExchangeM().allocateArray(radii_,0.,1);
particleCloud.dataExchangeM().allocateArray(voidfractions_,0.,1);
particleCloud.dataExchangeM().allocateArray(particleWeights_,0.,1);
particleCloud.dataExchangeM().allocateArray(particleVolumes_,0.,1);
particleCloud.dataExchangeM().allocateArray(cellIDs_,0.,1);
while (runTime.loop())
{
Info<< "Time = " << runTime.timeName() << nl << endl;
particleCloud.regionM().resetVolFields(Us);
particleCloud.dataExchangeM().couple();
particleCloud.dataExchangeM().getData("x","vector-atom",positions_,count);
particleCloud.dataExchangeM().getData("v","vector-atom",velocities_,count);
particleCloud.dataExchangeM().getData("radius","scalar-atom",radii_,count);
particleCloud.set_radii(radii_);
particleCloud.locateM().findCell(particleCloud.regionM().inRegion(),positions_,cellIDs_,particleCloud.numberOfParticles());
particleCloud.set_cellIDs(cellIDs_);
particleCloud.voidFractionM().setvoidFraction
(
particleCloud.regionM().inRegion(),voidfractions_,particleWeights_,particleVolumes_
);
voidfraction.internalField() = particleCloud.voidFractionM().voidFractionInterp();
voidfraction.correctBoundaryConditions();
particleCloud.averagingM().setVectorAverage
(
particleCloud.averagingM().UsNext(),
velocities_,
particleWeights_,
particleCloud.averagingM().UsWeightField(),
particleCloud.regionM().inRegion()
);
runTime.write();
count++; // proceed loading new data
Info<< "ExecutionTime = " << runTime.elapsedCpuTime() << " s"
<< " ClockTime = " << runTime.elapsedClockTime() << " s"
<< nl << endl;
}
delete positions_;
delete velocities_;
delete radii_;
delete voidfractions_;
delete particleWeights_;
delete particleVolumes_;
delete cellIDs_;
Info<< "End\n" << endl;
return 0;
}
// ************************************************************************* //

70
applications/utilities/vizClock/matPlot.py Normal file
View File

@ -0,0 +1,70 @@
#!/usr/bin/env python
import csv, sys
import numpy as np
import matplotlib.pyplot as plt
# Open the data
datafile = "timeEvalFull.txt"
f = open(datafile, 'r')
reader = csv.reader(f, dialect='excel-tab')
reader.next()
header = []
identifier = []
deltaT = []
maxdeltaT = []
nOfRuns = []
level = []
parentNr = []
parentName = []
i = 0
for row in reader:
if i == 0:
for column in row:
header.append(column)
print header
else:
identifier.append(row[0])
deltaT.append(float(row[1]))
maxdeltaT.append(float(row[2]))
nOfRuns.append(int(row[3]))
level.append(int(row[4]))
parentNr.append(int(row[5]))
parentName.append(row[6])
i+=1
print identifier
print deltaT
print maxdeltaT
print nOfRuns
print level
print parentNr
print parentName
bottom = []
brotherheight = []
for i in range(len(identifier)):
bottom.append(0)
brotherheight.append(0)
for i in range(len(identifier)):
if i != 0:
if level[i]<level[i-1]:
brotherheight[level[i-1]]=0
if parentNr[i] != -1:
bottom[i] = bottom[parentNr[i]]
bottom[i] += brotherheight[level[i]]
brotherheight[level[i]] += deltaT[i]
for i in range(len(identifier)):
plt.bar(level[i],deltaT[i],width = 0.2, bottom=bottom[i])
plt.text(level[i]+0.22,bottom[i]+deltaT[i]/2,identifier[i]+" "+str(nOfRuns[i])+"x")
plt.xlabel('run level')
plt.ylabel('CPU time in s')
plt.title('time measurement')
plt.show()

13
applications/utilities/vizClock/timeEvalFull.txt Normal file
View File

@ -0,0 +1,13 @@
Parallel Measurements in CPU-seconds of all Processors:
Name avgdeltaT maxdeltaT nOfRuns level parentNr parentName
X 5.000000e-06 5.000000e-06 1 0 -1 none
A 3.240000e-04 3.240000e-04 1 0 -1 none
B 1.680000e-04 1.680000e-04 1 1 1 A
C 9.000000e-06 9.000000e-06 3 2 2 B
D 6.000000e-06 6.000000e-06 3 3 3 C
E 1.500000e-04 1.500000e-04 3 2 2 B
F 2.400000e-05 2.400000e-05 3 1 1 A
G 6.000000e-06 6.000000e-06 3 1 1 A
X 6.000000e-06 6.000000e-06 3 2 7 G
H 4.000000e-05 4.000000e-05 5 1 1 A
I 2.000000e-05 2.000000e-05 1 1 1 A

188
doc/CFDEMcoupling_Manual.html Normal file
View File

@ -0,0 +1,188 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A>
</CENTER>
<HR>
<H2><CENTER>CFDEMcoupling Documentation
</CENTER></H2>
<HR>
<CENTER><IMG SRC = "Portfolio_CFDEMcoupling.png">
</CENTER>
<HR>
<H3>1. Contents
</H3>
<P>The CFDEMcoupling documentation is organized into the following sections. If you find errors or omissions in this manual or have suggestions for useful information to add, please send an email to the developers so we can improve the CFDEMcoupling documentation.
</P>
1.1 <A HREF = "#1_1">About CFDEMcoupling</A><BR>
1.2 <A HREF = "#1_2">Installation</A><BR>
1.3 <A HREF = "#1_3">Tutorials</A><BR>
1.4 <A HREF = "#1_4">couplingProperties dictionary</A><BR>
1.5 <A HREF = "#1_5">liggghtsCommands dictionary</A><BR>
1.6 <A HREF = "#cmd_5">Models and solvers</A> <BR>
<HR>
<A NAME = "1_1"></A><H4>1.1 About CFDEMcoupling
</H4>
<P>CFDEM coupling provides an open source parallel coupled CFD-DEM framework combining the strengths of <A HREF = "http://www.cfdem.com">LIGGGHTS</A> DEM code and the Open Source CFD package <A HREF = "http://www.openfoam.com">OpenFOAM(R)(*)</A>. The CFDEMcoupling toolbox allows to expand standard CFD solvers of <A HREF = "http://www.openfoam.com">OpenFOAM(R)(*)</A> to include a coupling to the DEM code <A HREF = "http://www.cfdem.com">LIGGGHTS</A>. In this toolbox the particle representation within the CFD solver is organized by "cloud" classes. Key functionalities are organised in sub-models (e.g. force models, data exchange models, etc.) which can easily be selected and combined by dictionary settings.
</P>
<P>The coupled solvers run fully parallel on distributed-memory clusters. Features are:
</P>
<UL><LI>its modular approach allows users to easily implement new models
<LI>its MPI parallelization enables to use it for large scale problems
<LI>the <A HREF = "http://www.cfdem.com">forum</A> on CFD-DEM gives the possibility to exchange with other users / developers
<LI>the use of GIT allows to easily update to the latest version
</UL>
<P>Details on installation are given on the <A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> .
The functionality of this CFD-DEM framwork is described via <A HREF = "#_1_2">tutorial cases</A> showing how to use different solvers and models.
</P>
<P>CFDEMcoupling stands for Computational Fluid Dynamics (CFD) -Discrete Element Method (DEM) coupling.
</P>
<P>CFDEMcoupling is an open-source code, distributed freely under the terms of the GNU Public License (GPL).
</P>
<P>Core development of CFDEMcoupling is done by Christoph Goniva and Christoph Kloss, both at DCS Computing GmbH, 2012
</P>
<HR>
<P>(*) <A HREF = "http://www.openfoam.com">OpenFOAM(R)</A> is a registered trade mark of Silicon Graphics International Corp. This offering is not affiliated, approved or endorsed by Silicon Graphics International Corp., the producer of the OpenFOAM(R) software and owner of the OpenFOAM(R) trademark.
</P>
<HR>
<A NAME = "1_2"></A><H4>1.2 Installation
</H4>
<P>Please follow the installation routine provided at www.cfdem.com.
In order to get the latest code version, please use the git repository at http://github.com (<A HREF = "githubAccess_public.html">githubAccess</A>).
</P>
<HR>
<A NAME = "1_3"></A><H4>1.3 Tutorials
</H4>
<P><B>General:</B>
</P>
<P>Each solver of the CFDEMcoupling is comes with at least one tutorial example, showing its functionality and correct useage. Provided that the installation is correct, the tutorials can be run via "Allrun.sh" shell scripts. These scripts perform all necessary steps (preprocessing, run, postprocessing, visualization).
</P>
<P><B>Location:</B>
</P>
<P>The tutorials can be found in the directory $CFDEM_PROJECT_DIR/tutorials, which can be reached by typing "cfdemTut"
</P>
<P><B>Structure:</B>
</P>
<P>Each case is structured in a directory called "CFD" covering the CFD relevant settings and data, and a dirctory called "DEM" covering the DEM relevant settings and data. This allows to easily expand a pure CFD or DEM simulation case to a coupled case.
</P>
<P><B>Usage:</B>
</P>
<P>Provided that the installation is correct, the tutorials can be run via "Allrun.sh" shell script, executed by typing "./Allrun.sh". The successful run of the script might need some third party software (e.g. octave, evince, etc.).
</P>
<P><B>Settings:</B>
</P>
<P>The main settings of a simulation are done via dictionaries:
</P>
<P>The DEM setup of each case is defined by a <A HREF = "http://www.cfdem.com">LIGGGHTS</A> input file located in $caseDir/DEM (e.g. in.liggghts_init). For details on the <A HREF = "http://www.cfdem.com">LIGGGHTS</A> setup, please have a look in the <A HREF = "http://www.cfdem.com">LIGGGHTS</A> manual.
</P>
<P>Standard CFD settings are defined in $caseDir/CFD/constant (e.g. transportProperties, RASproperties, etc.) and $caseDir/CFD/system (e.g. fvSchemes, controlDict). You can find more information on that in <A HREF = "http://www.openfoam.com">OpenFOAM(R)(*)</A> documentations (www.openFoam.com)(*).
</P>
<P>Settings of the coupling routines are defined in $caseDir/CFD/constant/<A HREF = "#1_3">couplingProperies</A> (e.g. force models, data exchange model, etc.) and $caseDir/CFD/constant/<A HREF = "#1_3">liggghtsCommands</A> (allows to execute a LIGGGHTS command during a coupled simulation).
</P>
<HR>
<A NAME = "1_4"></A><H4>1.4 "couplingProperties" dictionary
</H4>
<P><B>General:</B>
</P>
<P>In the "couplingProperties" dictionary the setup of the coupling routines of the CFD-DEM simulation are defined.
</P>
<P><B>Location:</B> $caseDir/CFD/constant
</P>
<P><B>Structure:</B>
</P>
<P>The dictionary is divided into two parts, "sub-models & settings" and "sub-model properties".
</P>
<P>In "sub-models & settings" the following routines must be specified:
</P>
<UL><LI>modelType
<LI>couplingInterval
<LI>voidFractionModel
<LI>locateModel
<LI>meshMotionModel
<LI>regionModel
<LI>IOModel
<LI>dataExchangeModel
<LI>averagingModel
<LI>forceModels
<LI>momCoupleModels
<LI>turbulenceModelType
</UL>
<P>In "sub-model properties" sub-dictionaries might be defined to specify model specific parameters.
</P>
<P><B>Settings:</B>
</P>
<P>Reasonable example settings for the "couplingProperties" dictionary are given in the tutorial cases.
</P>
<HR>
<H4><A NAME = "1_5"></A>1.5 "liggghtsCommands" dictionary
</H4>
<P><B>General:</B>
</P>
<P>In the "liggghtsCommands" dictionary liggghts commands being executed during a coupled CFD-DEM simulation are specified.
</P>
<P><B>Location:</B> $caseDir/CFD/constant
</P>
<P><B>Structure:</B>
</P>
<P>The dictionary is divided into two parts, first a list of "liggghtsCommandModels" is defined, then the settings for each model must be specified.
</P>
<P><B>Settings:</B>
</P>
<P>Reasonable example settings for the "liggghtsCommands" dictionary are given in the tutorial cases.
</P>
<HR>
<H4><A NAME = "cmd_5"></A><A NAME = "comm"></A>1.6 Models/Solvers
</H4>
<P>This section lists all CFDEMcoupling sub-models and solvers alphabetically, with a separate
listing below of styles within certain commands.
</P>
<DIV ALIGN=center><TABLE BORDER=1 >
<TR ALIGN="center"><TD ><A HREF = "IOModel.html">IOModel</A></TD><TD ><A HREF = "IOModel_basicIO.html">IOModel_basicIO</A></TD><TD ><A HREF = "IOModel_noIO.html">IOModel_noIO</A></TD><TD ><A HREF = "averagingModel.html">averagingModel</A></TD><TD ><A HREF = "averagingModel_dilute.html">averagingModel_dilute</A></TD><TD ><A HREF = "cfdemSolverIB.html">cfdemSolverIB</A></TD></TR>
<TR ALIGN="center"><TD ><A HREF = "cfdemSolverPiso.html">cfdemSolverPiso</A></TD><TD ><A HREF = "cfdemSolverPisoScalar.html">cfdemSolverPisoScalar</A></TD><TD ><A HREF = "clockModel.html">clockModel</A></TD><TD ><A HREF = "clockModel_noClock.html">clockModel_noClock</A></TD><TD ><A HREF = "clockModel_standardClock.html">clockModel_standardClock</A></TD><TD ><A HREF = "dataExchangeModel.html">dataExchangeModel</A></TD></TR>
<TR ALIGN="center"><TD ><A HREF = "dataExchangeModel_noDataExchange.html">dataExchangeModel_noDataExchange</A></TD><TD ><A HREF = "dataExchangeModel_oneWayVTK.html">dataExchangeModel_oneWayVTK</A></TD><TD ><A HREF = "dataExchangeModel_twoWayFiles.html">dataExchangeModel_twoWayFiles</A></TD><TD ><A HREF = "dataExchangeModel_twoWayMPI.html">dataExchangeModel_twoWayMPI</A></TD><TD ><A HREF = "forceModel.html">forceModel</A></TD><TD ><A HREF = "forceModelMS.html">forceModelMS</A></TD></TR>
<TR ALIGN="center"><TD ><A HREF = "forceModelMS_DiFeliceDragMS.html">forceModelMS_DiFeliceDragMS</A></TD><TD ><A HREF = "forceModel_Archimedes.html">forceModel_Archimedes</A></TD><TD ><A HREF = "forceModel_ArchimedesIB.html">forceModel_ArchimedesIB</A></TD><TD ><A HREF = "forceModel_DiFeliceDrag.html">forceModel_DiFeliceDrag</A></TD><TD ><A HREF = "forceModel_GidaspowDrag.html">forceModel_GidaspowDrag</A></TD><TD ><A HREF = "forceModel_KochHillDrag.html">forceModel_KochHillDrag</A></TD></TR>
<TR ALIGN="center"><TD ><A HREF = "forceModel_LaEuScalarDust.html">forceModel_LaEuScalarDust</A></TD><TD ><A HREF = "forceModel_LaEuScalarTemp.html">forceModel_LaEuScalarTemp</A></TD><TD ><A HREF = "forceModel_MeiLift.html">forceModel_MeiLift</A></TD><TD ><A HREF = "forceModel_SchillerNaumannDrag.html">forceModel_SchillerNaumannDrag</A></TD><TD ><A HREF = "forceModel_ShirgaonkarIB.html">forceModel_SchirgaonkarIB</A></TD><TD ><A HREF = "forceModel_fieldTimeAverage.html">forceModel_fieldTimeAverage</A></TD></TR>
<TR ALIGN="center"><TD ><A HREF = "forceModel_gradPForce.html">forceModel_gradPForce</A></TD><TD ><A HREF = "forceModel_interface.html">forceModel_interface</A></TD><TD ><A HREF = "forceModel_noDrag.html">forceModel_noDrag</A></TD><TD ><A HREF = "forceModel_totalMomentumExchange.html">forceModel_totalMomentumExchange</A></TD><TD ><A HREF = "forceModel_virtualMassForce.html">forceModel_virtualMassForce</A></TD><TD ><A HREF = "forceModel_viscForce.html">forceModel_viscForce</A></TD></TR>
<TR ALIGN="center"><TD ><A HREF = "forceModel_volWeightedAverage.html">forceModel_volWeightedAverage</A></TD><TD ><A HREF = "liggghtsCommandModel.html">liggghtsCommandModel</A></TD><TD ><A HREF = "liggghtsCommandModel_execute.html">liggghtsCommandModel_execute</A></TD><TD ><A HREF = "liggghtsCommandModel_readLiggghtsData.html">liggghtsCommandModel_readLiggghtsData</A></TD><TD ><A HREF = "liggghtsCommandModel_runLiggghts.html">liggghtsCommandModel_runLiggghts</A></TD><TD ><A HREF = "liggghtsCommandModel_writeLiggghts.html">liggghtsCommandModel_writeLiggghts</A></TD></TR>
<TR ALIGN="center"><TD ><A HREF = "locateModel.html">locateModel</A></TD><TD ><A HREF = "locateModel_engineSearch.html">locateModel_engineSearch</A></TD><TD ><A HREF = "locateModel_engineSearchIB.html">locateModel_engineSearchIB</A></TD><TD ><A HREF = "locateModel_standardSearch.html">locateModel_standardSearch</A></TD><TD ><A HREF = "locateModel_turboEngineSearch.html">locateModel_turboEngineSearch</A></TD><TD ><A HREF = "meshMotionModel.html">meshMotionModel</A></TD></TR>
<TR ALIGN="center"><TD ><A HREF = "meshMotionModel_DEMdrivenMeshMotion.html">meshMotionModel_DEMdrivenMeshMotion</A></TD><TD ><A HREF = "meshMotionModel_noMeshMotion.html">meshMotionModel_noMeshMotion</A></TD><TD ><A HREF = "momCoupleModel.html">momCoupleModel</A></TD><TD ><A HREF = "momCoupleModel_explicitCouple.html">momCoupleModel_explicitCouple</A></TD><TD ><A HREF = "momCoupleModel_implicitCouple.html">momCoupleModel_implicitCouple</A></TD><TD ><A HREF = "momCoupleModel_noCouple.html">momCoupleModel_noCouple</A></TD></TR>
<TR ALIGN="center"><TD ><A HREF = "regionModel.html">regionModel</A></TD><TD ><A HREF = "regionModel_allRegion.html">regionModel_allRegion</A></TD><TD ><A HREF = "regionModel_differentialRegion.html">regionModel_differentialRegion</A></TD><TD ><A HREF = "voidFractionModel.html">voidfractionModel</A></TD><TD ><A HREF = "voidFractionModel_GaussVoidFraction.html">voidfractionModel_GaussVoidFraction</A></TD><TD ><A HREF = "voidFractionModel_bigParticleVoidFraction.html">voidfractionModel_bigParticleVoidFraction</A></TD></TR>
<TR ALIGN="center"><TD ><A HREF = "voidFractionModel_centreVoidFraction.html">voidfractionModel_centreVoidFraction</A></TD><TD ><A HREF = "voidFractionModel_dividedVoidFractionMS.html">voidfractionModel_dividedMSVoidFractionMS</A></TD><TD ><A HREF = "voidFractionModel_dividedVoidFraction.html">voidfractionModel_dividedVoidFraction</A>
</TD></TR></TABLE></DIV>
</HTML>

373
doc/CFDEMcoupling_Manual.txt Normal file
View File

@ -0,0 +1,373 @@
"CFDEMproject WWW Site"_lws :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:link(of,http://www.openfoam.com)
:link(lig,http://www.cfdem.com)
:line
CFDEMcoupling Documentation :h2,c
:line
:c,image(Portfolio_CFDEMcoupling.png)
:line
1. Contents :h3
The CFDEMcoupling documentation is organized into the following sections. If you find errors or omissions in this manual or have suggestions for useful information to add, please send an email to the developers so we can improve the CFDEMcoupling documentation.
1.1 "About CFDEMcoupling"_#1_1
1.2 "Installation"_#1_2
1.3 "Tutorials"_#1_3
1.4 "couplingProperties dictionary"_#1_4
1.5 "liggghtsCommands dictionary"_#1_5
1.6 "Models and solvers"_#cmd_5 :all(b)
:line
1.1 About CFDEMcoupling :link(1_1),h4
CFDEM coupling provides an open source parallel coupled CFD-DEM framework combining the strengths of "LIGGGHTS"_lig DEM code and the Open Source CFD package "OpenFOAM(R)(*)"_of. The CFDEMcoupling toolbox allows to expand standard CFD solvers of "OpenFOAM(R)(*)"_of to include a coupling to the DEM code "LIGGGHTS"_lig. In this toolbox the particle representation within the CFD solver is organized by "cloud" classes. Key functionalities are organised in sub-models (e.g. force models, data exchange models, etc.) which can easily be selected and combined by dictionary settings.
The coupled solvers run fully parallel on distributed-memory clusters. Features are:
its modular approach allows users to easily implement new models :ulb,l
its MPI parallelization enables to use it for large scale problems :l
the "forum"_lws on CFD-DEM gives the possibility to exchange with other users / developers :l
the use of GIT allows to easily update to the latest version :l
:ule
Details on installation are given on the "CFDEMproject WWW Site"_lws .
The functionality of this CFD-DEM framwork is described via "tutorial cases"_#_1_2 showing how to use different solvers and models.
CFDEMcoupling stands for Computational Fluid Dynamics (CFD) -Discrete Element Method (DEM) coupling.
CFDEMcoupling is an open-source code, distributed freely under the terms of the GNU Public License (GPL).
Core development of CFDEMcoupling is done by Christoph Goniva and Christoph Kloss, both at DCS Computing GmbH, 2012
:line
(*) "OpenFOAM(R)"_of is a registered trade mark of Silicon Graphics International Corp. This offering is not affiliated, approved or endorsed by Silicon Graphics International Corp., the producer of the OpenFOAM(R) software and owner of the OpenFOAM(R) trademark.
:line
1.2 Installation :link(1_2),h4
Please follow the installation routine provided at www.cfdem.com.
In order to get the latest code version, please use the git repository at http://github.com ("githubAccess"_githubAccess_public.html).
:line
1.3 Tutorials :link(1_3),h4
[General:]
Each solver of the CFDEMcoupling is comes with at least one tutorial example, showing its functionality and correct useage. Provided that the installation is correct, the tutorials can be run via "Allrun.sh" shell scripts. These scripts perform all necessary steps (preprocessing, run, postprocessing, visualization).
[Location:]
The tutorials can be found in the directory $CFDEM_PROJECT_DIR/tutorials, which can be reached by typing "cfdemTut"
[Structure:]
Each case is structured in a directory called "CFD" covering the CFD relevant settings and data, and a dirctory called "DEM" covering the DEM relevant settings and data. This allows to easily expand a pure CFD or DEM simulation case to a coupled case.
[Usage:]
Provided that the installation is correct, the tutorials can be run via "Allrun.sh" shell script, executed by typing "./Allrun.sh". The successful run of the script might need some third party software (e.g. octave, evince, etc.).
[Settings:]
The main settings of a simulation are done via dictionaries:
The DEM setup of each case is defined by a "LIGGGHTS"_lig input file located in $caseDir/DEM (e.g. in.liggghts_init). For details on the "LIGGGHTS"_lig setup, please have a look in the "LIGGGHTS"_lig manual.
Standard CFD settings are defined in $caseDir/CFD/constant (e.g. transportProperties, RASproperties, etc.) and $caseDir/CFD/system (e.g. fvSchemes, controlDict). You can find more information on that in "OpenFOAM(R)(*)"_of documentations (www.openFoam.com)(*).
Settings of the coupling routines are defined in $caseDir/CFD/constant/"couplingProperies"_#1_3 (e.g. force models, data exchange model, etc.) and $caseDir/CFD/constant/"liggghtsCommands"_#1_3 (allows to execute a LIGGGHTS command during a coupled simulation).
:line
1.4 "couplingProperties" dictionary :link(1_4),h4
[General:]
In the "couplingProperties" dictionary the setup of the coupling routines of the CFD-DEM simulation are defined.
[Location:] $caseDir/CFD/constant
[Structure:]
The dictionary is divided into two parts, "sub-models & settings" and "sub-model properties".
In "sub-models & settings" the following routines must be specified:
modelType :ulb,l
couplingInterval :l
voidFractionModel :l
locateModel :l
meshMotionModel :l
regionModel :l
IOModel :l
dataExchangeModel :l
averagingModel :l
forceModels :l
momCoupleModels :l
turbulenceModelType :l
:ule
In "sub-model properties" sub-dictionaries might be defined to specify model specific parameters.
[Settings:]
Reasonable example settings for the "couplingProperties" dictionary are given in the tutorial cases.
:line
1.5 "liggghtsCommands" dictionary :h4,link(1_5)
[General:]
In the "liggghtsCommands" dictionary liggghts commands being executed during a coupled CFD-DEM simulation are specified.
[Location:] $caseDir/CFD/constant
[Structure:]
The dictionary is divided into two parts, first a list of "liggghtsCommandModels" is defined, then the settings for each model must be specified.
[Settings:]
Reasonable example settings for the "liggghtsCommands" dictionary are given in the tutorial cases.
:line
1.6 Models/Solvers :h4,link(cmd_5),link(comm)
This section lists all CFDEMcoupling sub-models and solvers alphabetically, with a separate
listing below of styles within certain commands.
"IOModel"_IOModel.html,
"IOModel_basicIO"_IOModel_basicIO.html,
"IOModel_noIO"_IOModel_noIO.html,
"averagingModel"_averagingModel.html,
"averagingModel_dilute"_averagingModel_dilute.html,
"cfdemSolverIB"_cfdemSolverIB.html,
"cfdemSolverPiso"_cfdemSolverPiso.html,
"cfdemSolverPisoScalar"_cfdemSolverPisoScalar.html,
"clockModel"_clockModel.html,
"clockModel_noClock"_clockModel_noClock.html,
"clockModel_standardClock"_clockModel_standardClock.html,
"dataExchangeModel"_dataExchangeModel.html,
"dataExchangeModel_noDataExchange"_dataExchangeModel_noDataExchange.html,
"dataExchangeModel_oneWayVTK"_dataExchangeModel_oneWayVTK.html,
"dataExchangeModel_twoWayFiles"_dataExchangeModel_twoWayFiles.html,
"dataExchangeModel_twoWayMPI"_dataExchangeModel_twoWayMPI.html,
"forceModel"_forceModel.html,
"forceModelMS"_forceModelMS.html,
"forceModelMS_DiFeliceDragMS"_forceModelMS_DiFeliceDragMS.html,
"forceModel_Archimedes"_forceModel_Archimedes.html,
"forceModel_ArchimedesIB"_forceModel_ArchimedesIB.html,
"forceModel_DiFeliceDrag"_forceModel_DiFeliceDrag.html,
"forceModel_GidaspowDrag"_forceModel_GidaspowDrag.html,
"forceModel_KochHillDrag"_forceModel_KochHillDrag.html,
"forceModel_LaEuScalarDust"_forceModel_LaEuScalarDust.html,
"forceModel_LaEuScalarTemp"_forceModel_LaEuScalarTemp.html,
"forceModel_MeiLift"_forceModel_MeiLift.html,
"forceModel_SchillerNaumannDrag"_forceModel_SchillerNaumannDrag.html,
"forceModel_SchirgaonkarIB"_forceModel_ShirgaonkarIB.html,
"forceModel_fieldTimeAverage"_forceModel_fieldTimeAverage.html,
"forceModel_gradPForce"_forceModel_gradPForce.html,
"forceModel_interface"_forceModel_interface.html,
"forceModel_noDrag"_forceModel_noDrag.html,
"forceModel_totalMomentumExchange"_forceModel_totalMomentumExchange.html,
"forceModel_virtualMassForce"_forceModel_virtualMassForce.html,
"forceModel_viscForce"_forceModel_viscForce.html,
"forceModel_volWeightedAverage"_forceModel_volWeightedAverage.html,
"liggghtsCommandModel"_liggghtsCommandModel.html,
"liggghtsCommandModel_execute"_liggghtsCommandModel_execute.html,
"liggghtsCommandModel_readLiggghtsData"_liggghtsCommandModel_readLiggghtsData.html,
"liggghtsCommandModel_runLiggghts"_liggghtsCommandModel_runLiggghts.html,
"liggghtsCommandModel_writeLiggghts"_liggghtsCommandModel_writeLiggghts.html,
"locateModel"_locateModel.html,
"locateModel_engineSearch"_locateModel_engineSearch.html,
"locateModel_engineSearchIB"_locateModel_engineSearchIB.html,
"locateModel_standardSearch"_locateModel_standardSearch.html,
"locateModel_turboEngineSearch"_locateModel_turboEngineSearch.html,
"meshMotionModel"_meshMotionModel.html,
"meshMotionModel_DEMdrivenMeshMotion"_meshMotionModel_DEMdrivenMeshMotion.html,
"meshMotionModel_noMeshMotion"_meshMotionModel_noMeshMotion.html,
"momCoupleModel"_momCoupleModel.html,
"momCoupleModel_explicitCouple"_momCoupleModel_explicitCouple.html,
"momCoupleModel_implicitCouple"_momCoupleModel_implicitCouple.html,
"momCoupleModel_noCouple"_momCoupleModel_noCouple.html,
"regionModel"_regionModel.html,
"regionModel_allRegion"_regionModel_allRegion.html,
"regionModel_differentialRegion"_regionModel_differentialRegion.html,
"voidfractionModel"_voidFractionModel.html,
"voidfractionModel_GaussVoidFraction"_voidFractionModel_GaussVoidFraction.html,
"voidfractionModel_bigParticleVoidFraction"_voidFractionModel_bigParticleVoidFraction.html,
"voidfractionModel_centreVoidFraction"_voidFractionModel_centreVoidFraction.html,
"voidfractionModel_dividedMSVoidFractionMS"_voidFractionModel_dividedVoidFractionMS.html,
"voidfractionModel_dividedVoidFraction"_voidFractionModel_dividedVoidFraction.html :tb(c=6,ea=c)

678
doc/COPYING Normal file
View File

@ -0,0 +1,678 @@
-------------------------------------------------------------------------
GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The GNU General Public License is a free, copyleft license for
software and other kinds of works.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
software for all its users. We, the Free Software Foundation, use the
GNU General Public License for most of our software; it applies also to
any other work released this way by its authors. You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you have
certain responsibilities if you distribute copies of the software, or if
you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code. And you must show them these terms so they
know their rights.
Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the manufacturer
can do so. This is fundamentally incompatible with the aim of
protecting users' freedom to change the software. The systematic
pattern of such abuse occurs in the area of products for individuals to
use, which is precisely where it is most unacceptable. Therefore, we
have designed this version of the GPL to prohibit the practice for those
products. If such problems arise substantially in other domains, we
stand ready to extend this provision to those domains in future versions
of the GPL, as needed to protect the freedom of users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish to
avoid the special danger that patents applied to a free program could
make it effectively proprietary. To prevent this, the GPL assures that
patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and
modification follow.
TERMS AND CONDITIONS
0. Definitions.
"This License" refers to version 3 of the GNU General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this
License. Each licensee is addressed as "you". "Licensees" and
"recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy. The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based
on the Program.
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user through
a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices"
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.
1. Source Code.
The "source code" for a work means the preferred form of the work
for making modifications to it. "Object code" means any non-source
form of a work.
A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.
The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding
Source.
The Corresponding Source for a work in source code form is that
same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise remains
in force. You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide you
with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do
not control copyright. Those thus making or running the covered works
for you must do so exclusively on your behalf, under your direction
and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section 10
makes it unnecessary.
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect to
the covered work, and you disclaim any intention to limit operation or
modification of the work as a means of enforcing, against the work's
users, your or third parties' legal rights to forbid circumvention of
technological measures.
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.
b) The work must carry prominent notices stating that it is
released under this License and any conditions added under section
7. This requirement modifies the requirement in section 4 to
"keep intact all notices".
c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.
A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:
a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.
d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.
A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,
or household purposes, or (2) anything designed or sold for incorporation
into a dwelling. In determining whether a product is a consumer product,
doubtful cases shall be resolved in favor of coverage. For a particular
product received by a particular user, "normally used" refers to a
typical or common use of that class of product, regardless of the status
of the particular user or of the way in which the particular user
actually uses, or expects or is expected to use, the product. A product
is a consumer product regardless of whether the product has substantial
commercial, industrial or non-consumer uses, unless such uses represent
the only significant mode of use of the product.
"Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to install
and execute modified versions of a covered work in that User Product from
a modified version of its Corresponding Source. The information must
suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because
modification has been made.
If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).
The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates
for a work that has been modified or installed by the recipient, or for
the User Product in which it has been modified or installed. Access to a
network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders of
that material) supplement the terms of this License with terms:
a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or
authors of the material; or
e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions of
it) with contractual assumptions of liability to the recipient, for
any liability that these contractual assumptions directly impose on
those licensors and authors.
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.
8. Termination.
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or
run a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.
10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.
11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims
owned or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.
If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.
A patent license is "discriminatory" if it does not include within
the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are
specifically granted under this License. You may not convey a covered
work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment
to the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all. For example, if you agree to terms that obligate you
to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.
13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of
the GNU General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:
<program> Copyright (C) <year> <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, your program's commands
might be different; for a GUI interface, you would use an "about box".
You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see
<http://www.gnu.org/licenses/>.
The GNU General Public License does not permit incorporating your program
into proprietary programs. If your program is a subroutine library, you
may consider it more useful to permit linking proprietary applications with
the library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License. But first, please read
<http://www.gnu.org/philosophy/why-not-lgpl.html>.
-------------------------------------------------------------------------

10
doc/DISCLAIMER Normal file
View File

@ -0,0 +1,10 @@
This software is not approved or endorsed by Silicon Graphics International Corp. or the OpenFOAM® Foundation, the producer of the OpenFOAM® software and owner of the OpenFOAM® trade mark.
Detailed information on the OpenFOAM trademark can be found at
- http://www.openfoam.com/legal/trademark-policy.php
- http://www.openfoam.com/legal/trademark-guidelines.php
For further information on OpenCFD and OpenFOAM, please refer to
- http://www.openfoam.com

40
doc/IOModel.html Normal file
View File

@ -0,0 +1,40 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>IOModel command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>IOModel "model";
</PRE>
<UL><LI>model = name of IO-model to be applied
</UL>
<P><B>Examples:</B>
</P>
<P>IOModel "off";
</P>
<P>Note: This examples list might not be complete - please look for other models (IOModel_XY) in this documentation.
</P>
<P><B>Description:</B>
</P>
<P>The IO-model is the base class to write data (e.g. particle properties) to files.
</P>
<P><B>Restrictions:</B>
</P>
<P>none.
</P>
<P><B>Related commands:</B>
</P>
<P>Note: This examples list may be incomplete - please look for other models (IOModel_XY) in this documentation.
</P>
<P><B>Default:</B> none.
</P>
</HTML>

36
doc/IOModel.txt Normal file
View File

@ -0,0 +1,36 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
IOModel command :h3
[Syntax:]
Defined in couplingProperties dictionary.
IOModel "model"; :pre
model = name of IO-model to be applied :ul
[Examples:]
IOModel "off";
Note: This examples list might not be complete - please look for other models (IOModel_XY) in this documentation.
[Description:]
The IO-model is the base class to write data (e.g. particle properties) to files.
[Restrictions:]
none.
[Related commands:]
Note: This examples list may be incomplete - please look for other models (IOModel_XY) in this documentation.
[Default:] none.

32
doc/IOModel_basicIO.html Normal file
View File

@ -0,0 +1,32 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>IOModel_basicIO command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>IOModel "basicIO";
</PRE>
<P><B>Examples:</B>
</P>
<PRE>IOModel "basicIO";
</PRE>
<P><B>Description:</B>
</P>
<P>The basic IO-model writes particle positions velocities and radii to files. The output directory ($casePath/CFD/particles) is created automatically. Data is written every write time of the CFD simulation.
</P>
<P><B>Restrictions:</B> None.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "IOModel.html">IOModel</A>
</P>
</HTML>

29
doc/IOModel_basicIO.txt Normal file
View File

@ -0,0 +1,29 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
IOModel_basicIO command :h3
[Syntax:]
Defined in couplingProperties dictionary.
IOModel "basicIO"; :pre
[Examples:]
IOModel "basicIO"; :pre
[Description:]
The basic IO-model writes particle positions velocities and radii to files. The output directory ($casePath/CFD/particles) is created automatically. Data is written every write time of the CFD simulation.
[Restrictions:] None.
[Related commands:]
"IOModel"_IOModel.html

32
doc/IOModel_noIO.html Normal file
View File

@ -0,0 +1,32 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>IOModel_noIO command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>IOModel "off";
</PRE>
<P><B>Examples:</B>
</P>
<PRE>IOModel "off";
</PRE>
<P><B>Description:</B>
</P>
<P>The noIO-model is a dummy IO model.
</P>
<P><B>Restrictions:</B> None.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "IOModel.html">IOModel</A>
</P>
</HTML>

29
doc/IOModel_noIO.txt Normal file
View File

@ -0,0 +1,29 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
IOModel_noIO command :h3
[Syntax:]
Defined in couplingProperties dictionary.
IOModel "off"; :pre
[Examples:]
IOModel "off"; :pre
[Description:]
The noIO-model is a dummy IO model.
[Restrictions:] None.
[Related commands:]
"IOModel"_IOModel.html

BIN
doc/Portfolio_CFDEMcoupling.png Executable file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 28 KiB

4
doc/SCcontent/individual_commands.txt Normal file
View File

@ -0,0 +1,4 @@
1.6 Models/Solvers :h4,link(cmd_5),link(comm)
This section lists all CFDEMcoupling sub-models and solvers alphabetically, with a separate
listing below of styles within certain commands.

41
doc/averagingModel.html Normal file
View File

@ -0,0 +1,41 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>averagingModel command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>averagingModel model;
</PRE>
<UL><LI>model = name of averaging model to be applied
</UL>
<P><B>Examples:</B>
</P>
<PRE>averagingModel dense;
averagingModel dilute;
</PRE>
<P>Note: This examples list might not be complete - please look for other averagin models (averagingModel_XY) in this documentation.
</P>
<P><B>Description:</B>
</P>
<P>The averaging model performs the Lagrangian->Eulerian mapping of data (e.g. particle velocities).
</P>
<P><B>Restrictions:</B>
</P>
<P>None.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "averagingModel_dense.html">dense</A>, <A HREF = "averagingModel_dilute.html">dilute</A>
</P>
<P><B>Default:</B> none
</P>
</HTML>

37
doc/averagingModel.txt Normal file
View File

@ -0,0 +1,37 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
averagingModel command :h3
[Syntax:]
Defined in couplingProperties dictionary.
averagingModel model; :pre
model = name of averaging model to be applied :ul
[Examples:]
averagingModel dense;
averagingModel dilute; :pre
Note: This examples list might not be complete - please look for other averagin models (averagingModel_XY) in this documentation.
[Description:]
The averaging model performs the Lagrangian->Eulerian mapping of data (e.g. particle velocities).
[Restrictions:]
None.
[Related commands:]
"dense"_averagingModel_dense.html, "dilute"_averagingModel_dilute.html
[Default:] none

37
doc/averagingModel_dense.html Normal file
View File

@ -0,0 +1,37 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>averagingModel_dense command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>averagingModel dense;
</PRE>
<P><B>Examples:</B>
</P>
<PRE>averagingModel dense;
</PRE>
<P><B>Description:</B>
</P>
<P>The averaging model performs the Lagrangian->Eulerian mapping of data (e.g. particle velocities).
In the "cfdemParticle cloud" this averaging model is used to calculate the average particle velocity inside a CFD cell. The "dense" model is supposed to be applied to cases where the granular regime is rather dense. The particle velocity inside a CFD cell is evaluated as an ensemble average of the particle velocities.
</P>
<P><B>Restrictions:</B>
</P>
<P>None.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "averagingModel.html">averagingModel</A>, <A HREF = "averagingModel_dilute.html">dilute</A>
</P>
<P><B>Default:</B> none
</P>
</HTML>

35
doc/averagingModel_dilute.html Normal file
View File

@ -0,0 +1,35 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>averagingModel_dilute command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>averagingModel dilute;
</PRE>
<P><B>Examples:</B>
</P>
<PRE>averagingModel dilute;
</PRE>
<P><B>Description:</B>
</P>
<P>The averaging model performs the Lagrangian->Eulerian mapping of data (e.g. particle velocities).
In the "cfdemParticle cloud" this averaging model is used to calculate the average particle velocity inside a CFD cell. The "dilute" model is supposed to be applied to cases where the granular regime is rather dilute. The particle velocity inside a CFD cell is evaluated from a single particle in a cell (no averaging).
</P>
<P><B>Restrictions:</B>
</P>
<P>This model is computationally efficient, but should only be used when only one particle is inside one CFD cell.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "averagingModel.html">averagingModel</A>, <A HREF = "averagingModel_dense.html">dense</A>
</P>
</HTML>

32
doc/averagingModel_dilute.txt Normal file
View File

@ -0,0 +1,32 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
averagingModel_dilute command :h3
[Syntax:]
Defined in couplingProperties dictionary.
averagingModel dilute; :pre
[Examples:]
averagingModel dilute; :pre
[Description:]
The averaging model performs the Lagrangian->Eulerian mapping of data (e.g. particle velocities).
In the "cfdemParticle cloud" this averaging model is used to calculate the average particle velocity inside a CFD cell. The "dilute" model is supposed to be applied to cases where the granular regime is rather dilute. The particle velocity inside a CFD cell is evaluated from a single particle in a cell (no averaging).
[Restrictions:]
This model is computationally efficient, but should only be used when only one particle is inside one CFD cell.
[Related commands:]
"averagingModel"_averagingModel.html, "dense"_averagingModel_dense.html

31
doc/cfdemSolverIB.html Normal file
View File

@ -0,0 +1,31 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>cfdemSolverIB command
</H3>
<P><B>Description:</B>
</P>
<P>"cfdemSolverIB" is a coupled CFD-DEM solver using CFDEMcoupling, an open source parallel coupled CFD-DEM framework, for calculating
the dynamics between immersed bodies and the surrounding fluid. Being an implementation of an immersed boundary method it allows tackling problems where the body diameter exceeds the maximal size of a fluid cell. Usung the toolbox of OpenFOAM(R)(*) the governing equations of the fluid are computed and the corrections of velocity and pressure field with respect to the body-movement information, gained from LIGGGHTS, are incorporated.
</P>
<P>see:
</P>
<P>GONIVA, C., KLOSS, C., HAGER,A., WIERINK, G. and PIRKER, S. (2011): "A MULTI-PURPOSE OPEN SOURCE CFD-DEM APPROACH", Proc. of the 8th Int. Conf. on CFD in Oil and Gas, Metallurgical and Process Industries, Trondheim, Norway
</P>
<P>and
</P>
<P>HAGER, A., KLOSS, C. and GONIVA, C. (2011): "TOWARDS AN EFFICIENT IMMERSED BOUNDARY METHOD WITHIN AN OPEN SOURCE FRAMEWORK", Proc. of the 8th Int. Conf. on CFD in Oil and Gas, Metallurgical and Process Industries, Trondheim, Norway
</P>
<HR>
<P>(*) <A HREF = "of">OpenFOAM(R)</A> is a registered trade mark of Silicon Graphics International Corp. This offering is not affiliated, approved or endorsed by Silicon Graphics International Corp., the producer of the OpenFOAM(R) software and owner of the OpenFOAM(R) trademark.
</P>
<HR>
</HTML>

26
doc/cfdemSolverIB.txt Normal file
View File

@ -0,0 +1,26 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
cfdemSolverIB command :h3
[Description:]
"cfdemSolverIB" is a coupled CFD-DEM solver using CFDEMcoupling, an open source parallel coupled CFD-DEM framework, for calculating
the dynamics between immersed bodies and the surrounding fluid. Being an implementation of an immersed boundary method it allows tackling problems where the body diameter exceeds the maximal size of a fluid cell. Usung the toolbox of OpenFOAM(R)(*) the governing equations of the fluid are computed and the corrections of velocity and pressure field with respect to the body-movement information, gained from LIGGGHTS, are incorporated.
see:
GONIVA, C., KLOSS, C., HAGER,A., WIERINK, G. and PIRKER, S. (2011): "A MULTI-PURPOSE OPEN SOURCE CFD-DEM APPROACH", Proc. of the 8th Int. Conf. on CFD in Oil and Gas, Metallurgical and Process Industries, Trondheim, Norway
and
HAGER, A., KLOSS, C. and GONIVA, C. (2011): "TOWARDS AN EFFICIENT IMMERSED BOUNDARY METHOD WITHIN AN OPEN SOURCE FRAMEWORK", Proc. of the 8th Int. Conf. on CFD in Oil and Gas, Metallurgical and Process Industries, Trondheim, Norway
:line
(*) "OpenFOAM(R)"_of is a registered trade mark of Silicon Graphics International Corp. This offering is not affiliated, approved or endorsed by Silicon Graphics International Corp., the producer of the OpenFOAM(R) software and owner of the OpenFOAM(R) trademark.
:line

26
doc/cfdemSolverPiso.html Normal file
View File

@ -0,0 +1,26 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>cfdemSolverPiso command
</H3>
<P><B>Description:</B>
</P>
<P>"cfdemSolverPiso" is a coupled CFD-DEM solver using CFDEMcoupling, an open source parallel coupled CFD-DEM framework. Based on pisoFoam(R)(*), a finite volume based solver for turbulent Navier-Stokes equations applying PISO algorithm, "cfdemSolverPiso" has additional functionality for a coupling to the DEM code "LIGGGHTS". The volume averaged Navier-Stokes Equations are solved accounting for momentum exchange and volume displacement of discrete particles whose trajectories are calculated in the DEM code LIGGGHTS.
</P>
<P>see:
</P>
<P>GONIVA, C., KLOSS, C., HAGER,A. and PIRKER, S. (2010): "An Open Source CFD-DEM Perspective", Proc. of OpenFOAM Workshop, Göteborg, June 22.-24.
</P>
<HR>
<P>(*) <A HREF = "of">OpenFOAM(R)</A> is a registered trade mark of Silicon Graphics International Corp. This offering is not affiliated, approved or endorsed by Silicon Graphics International Corp., the producer of the OpenFOAM(R) software and owner of the OpenFOAM(R) trademark.
</P>
<HR>
</HTML>

24
doc/cfdemSolverPiso.txt Normal file
View File

@ -0,0 +1,24 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
cfdemSolverPiso command :h3
[Description:]
"cfdemSolverPiso" is a coupled CFD-DEM solver using CFDEMcoupling, an open source parallel coupled CFD-DEM framework. Based on pisoFoam(R)(*), a finite volume based solver for turbulent Navier-Stokes equations applying PISO algorithm, "cfdemSolverPiso" has additional functionality for a coupling to the DEM code "LIGGGHTS". The volume averaged Navier-Stokes Equations are solved accounting for momentum exchange and volume displacement of discrete particles whose trajectories are calculated in the DEM code LIGGGHTS.
see:
GONIVA, C., KLOSS, C., HAGER,A. and PIRKER, S. (2010): "An Open Source CFD-DEM Perspective", Proc. of OpenFOAM Workshop, Göteborg, June 22.-24.
:line
(*) "OpenFOAM(R)"_of is a registered trade mark of Silicon Graphics International Corp. This offering is not affiliated, approved or endorsed by Silicon Graphics International Corp., the producer of the OpenFOAM(R) software and owner of the OpenFOAM(R) trademark.
:line

26
doc/cfdemSolverPisoScalar.html Normal file
View File

@ -0,0 +1,26 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>cfdemSolverPisoScalar command
</H3>
<P><B>Description:</B>
</P>
<P>"cfdemSolverPisoScalar" is a coupled CFD-DEM solver using CFDEMcoupling, an open source parallel coupled CFD-DEM framework. Based on pisoFoam(R)(*), a finite volume based solver for turbulent Navier-Stokes equations applying PISO algorithm, "cfdemSolverPisoScalar" has additional functionality for a coupling to the DEM code "LIGGGHTS" as well as a scalar transport equation. The volume averaged Navier-Stokes Equations are solved accounting for momentum exchange and volume displacement of discrete particles whose trajectories are calculated in the DEM code LIGGGHTS. The scalar transport equation is coupled to scalar properties of the particle phase, thus convective heat transfer in a fluid granular system can be modeled with "cfdemSolverPisoScalar".
</P>
<P>see:
</P>
<P>GONIVA, C., KLOSS, C., HAGER,A. and PIRKER, S. (2010): "An Open Source CFD-DEM Perspective", Proc. of OpenFOAM Workshop, Göteborg, June 22.-24.
</P>
<HR>
<P>(*) <A HREF = "of">OpenFOAM(R)</A> is a registered trade mark of Silicon Graphics International Corp. This offering is not affiliated, approved or endorsed by Silicon Graphics International Corp., the producer of the OpenFOAM(R) software and owner of the OpenFOAM(R) trademark.
</P>
<HR>
</HTML>

22
doc/cfdemSolverPisoScalar.txt Normal file
View File

@ -0,0 +1,22 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
cfdemSolverPisoScalar command :h3
[Description:]
"cfdemSolverPisoScalar" is a coupled CFD-DEM solver using CFDEMcoupling, an open source parallel coupled CFD-DEM framework. Based on pisoFoam(R)(*), a finite volume based solver for turbulent Navier-Stokes equations applying PISO algorithm, "cfdemSolverPisoScalar" has additional functionality for a coupling to the DEM code "LIGGGHTS" as well as a scalar transport equation. The volume averaged Navier-Stokes Equations are solved accounting for momentum exchange and volume displacement of discrete particles whose trajectories are calculated in the DEM code LIGGGHTS. The scalar transport equation is coupled to scalar properties of the particle phase, thus convective heat transfer in a fluid granular system can be modeled with "cfdemSolverPisoScalar".
see:
GONIVA, C., KLOSS, C., HAGER,A. and PIRKER, S. (2010): "An Open Source CFD-DEM Perspective", Proc. of OpenFOAM Workshop, Göteborg, June 22.-24.
:line
(*) "OpenFOAM(R)"_of is a registered trade mark of Silicon Graphics International Corp. This offering is not affiliated, approved or endorsed by Silicon Graphics International Corp., the producer of the OpenFOAM(R) software and owner of the OpenFOAM(R) trademark.
:line

34
doc/clockModel.html Normal file
View File

@ -0,0 +1,34 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>clockModel command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>clockModel model;
</PRE>
<UL><LI>model = name of the clockModel to be applied
</UL>
<P><B>Examples:</B>
</P>
<PRE>clockModel standardClock;
</PRE>
<P>Note: This examples list might not be complete - please look for other models (clockModel_XY) in this documentation.
</P>
<P><B>Description:</B>
</P>
<P>The clockModel is the base class for models to examine the code/algorithm with respect to run time.
</P>
<P><B>Restrictions:</B> none.
</P>
<P><B>Default:</B> none.
</P>
</HTML>

30
doc/clockModel.txt Normal file
View File

@ -0,0 +1,30 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
clockModel command :h3
[Syntax:]
Defined in couplingProperties dictionary.
clockModel model; :pre
model = name of the clockModel to be applied :ul
[Examples:]
clockModel standardClock; :pre
Note: This examples list might not be complete - please look for other models (clockModel_XY) in this documentation.
[Description:]
The clockModel is the base class for models to examine the code/algorithm with respect to run time.
[Restrictions:] none.
[Default:] none.

32
doc/clockModel_noClock.html Normal file
View File

@ -0,0 +1,32 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>clockModel_noClock command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>clockModel off;
</PRE>
<P><B>Examples:</B>
</P>
<PRE>clockModel off;
</PRE>
<P><B>Description:</B>
</P>
<P>The "noClock" model is a dummy clockModel model which does not measure/evaluate the run time.
</P>
<P><B>Restrictions:</B> none.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "clockModel.html">clockModel</A>
</P>
</HTML>

29
doc/clockModel_noClock.txt Normal file
View File

@ -0,0 +1,29 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
clockModel_noClock command :h3
[Syntax:]
Defined in couplingProperties dictionary.
clockModel off; :pre
[Examples:]
clockModel off; :pre
[Description:]
The "noClock" model is a dummy clockModel model which does not measure/evaluate the run time.
[Restrictions:] none.
[Related commands:]
"clockModel"_clockModel.html

32
doc/clockModel_standardClock.html Normal file
View File

@ -0,0 +1,32 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>clockModel_standardClock command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>clockModel standardClock;
</PRE>
<P><B>Examples:</B>
</P>
<PRE>clockModel standardClock;
</PRE>
<P><B>Description:</B>
</P>
<P>The "standardClock" model is a basic clockModel model which measures the run time between every ".start(name)" and ".stop()" statement placed in the code. If a ".start(name)" is called more than once (e.g. in a loop) the accumulated times are calculated. After the simulation has finished, the data is stored in $caseDir/CFD/clockData/$startTime/*.txt .
</P>
<P><B>Restrictions:</B> none.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "clockModel.html">clockModel</A>
</P>
</HTML>

29
doc/clockModel_standardClock.txt Normal file
View File

@ -0,0 +1,29 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
clockModel_standardClock command :h3
[Syntax:]
Defined in couplingProperties dictionary.
clockModel standardClock; :pre
[Examples:]
clockModel standardClock; :pre
[Description:]
The "standardClock" model is a basic clockModel model which measures the run time between every ".start(name)" and ".stop()" statement placed in the code. If a ".start(name)" is called more than once (e.g. in a loop) the accumulated times are calculated. After the simulation has finished, the data is stored in $caseDir/CFD/clockData/$startTime/*.txt .
[Restrictions:] none.
[Related commands:]
"clockModel"_clockModel.html

41
doc/dataExchangeModel.html Normal file
View File

@ -0,0 +1,41 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>dataExchangeModel command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>dataExchangeModel model;
</PRE>
<UL><LI>model = name of data exchange model to be applied
</UL>
<P><B>Examples:</B>
</P>
<PRE>dataExchangeModel twoWayFiles;
dataExchangeModel twoWayMPI;
</PRE>
<P>Note: This examples list might not be complete - please look for other models (dataExchangeModel_XY) in this documentation.
</P>
<P><B>Description:</B>
</P>
<P>The data exchange model performs the data exchange between the DEM code and the CFD code.
</P>
<P><B>Restrictions:</B>
</P>
<P>None.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "dataExchangeModel_noDataExchange.html">noDataExchange</A>, <A HREF = "dataExchangeModel_oneWayVTK.html">oneWayVTK</A>, <A HREF = "dataExchangeModel_twoWayFiles.html">twoWayFiles</A>, <A HREF = "dataExchangeModel_twoWayMPI.html">twoWayMPI</A>
</P>
<P><B>Default:</B> none
</P>
</HTML>

37
doc/dataExchangeModel.txt Normal file
View File

@ -0,0 +1,37 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
dataExchangeModel command :h3
[Syntax:]
Defined in couplingProperties dictionary.
dataExchangeModel model; :pre
model = name of data exchange model to be applied :ul
[Examples:]
dataExchangeModel twoWayFiles;
dataExchangeModel twoWayMPI; :pre
Note: This examples list might not be complete - please look for other models (dataExchangeModel_XY) in this documentation.
[Description:]
The data exchange model performs the data exchange between the DEM code and the CFD code.
[Restrictions:]
None.
[Related commands:]
"noDataExchange"_dataExchangeModel_noDataExchange.html, "oneWayVTK"_dataExchangeModel_oneWayVTK.html, "twoWayFiles"_dataExchangeModel_twoWayFiles.html, "twoWayMPI"_dataExchangeModel_twoWayMPI.html
[Default:] none

34
doc/dataExchangeModel_noDataExchange.html Normal file
View File

@ -0,0 +1,34 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>dataExchangeModel_noDataExchange command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>dataExchangeModel noDataExchange;
</PRE>
<P><B>Examples:</B>
</P>
<PRE>dataExchangeModel noDataExchange;
</PRE>
<P><B>Description:</B>
</P>
<P>The data exchange model performs the data exchange between the DEM code and the CFD code. The noDataExchange model is a dummy model where no data is exchanged.
</P>
<P><B>Restrictions:</B>
</P>
<P>None.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "dataExchangeModel.html">dataExchangeModel</A>
</P>
</HTML>

31
doc/dataExchangeModel_noDataExchange.txt Normal file
View File

@ -0,0 +1,31 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
dataExchangeModel_noDataExchange command :h3
[Syntax:]
Defined in couplingProperties dictionary.
dataExchangeModel noDataExchange; :pre
[Examples:]
dataExchangeModel noDataExchange; :pre
[Description:]
The data exchange model performs the data exchange between the DEM code and the CFD code. The noDataExchange model is a dummy model where no data is exchanged.
[Restrictions:]
None.
[Related commands:]
"dataExchangeModel"_dataExchangeModel.html

58
doc/dataExchangeModel_oneWayVTK.html Normal file
View File

@ -0,0 +1,58 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>dataExchangeModel_oneWayVTK command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>dataExchangeModel oneWayVTK;
oneWayVTKProps
{
DEMts timeStep;
relativePath "path";
couplingFilename "filename";
maxNumberOfParticles number;
};
</PRE>
<UL><LI><I>timeStep</I> = time step size of stored DEM data
<LI><I>path</I> = path to the VTK data files relative do simulation directory
<LI><I>filename</I> = filename of the VTK file series
<LI><I>number</I> = maximum nuber of particles in DEM simulation
</UL>
<P><B>Examples:</B>
</P>
<PRE>dataExchangeModel oneWayVTK;
oneWayVTKProps
{
DEMts 0.0001;
relativePath "../DEM/post";
couplingFilename "vtk_out%4.4d.vtk";
maxNumberOfParticles 30000;
}
</PRE>
<P><B>Description:</B>
</P>
<P>The data exchange model performs the data exchange between the DEM code and the CFD code. The oneWayVTK model is a model that can exchange particle properties from DEM to CFD based on previously stored VTK data.
</P>
<P><B>Restrictions:</B>
</P>
<P>None.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "dataExchangeModel.html">dataExchangeModel</A>
</P>
</HTML>

51
doc/dataExchangeModel_oneWayVTK.txt Normal file
View File

@ -0,0 +1,51 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
dataExchangeModel_oneWayVTK command :h3
[Syntax:]
Defined in couplingProperties dictionary.
dataExchangeModel oneWayVTK;
oneWayVTKProps
\{
DEMts timeStep;
relativePath "path";
couplingFilename "filename";
maxNumberOfParticles number;
\}; :pre
{timeStep} = time step size of stored DEM data :ulb,l
{path} = path to the VTK data files relative do simulation directory :l
{filename} = filename of the VTK file series :l
{number} = maximum nuber of particles in DEM simulation :l
:ule
[Examples:]
dataExchangeModel oneWayVTK;
oneWayVTKProps
\{
DEMts 0.0001;
relativePath "../DEM/post";
couplingFilename "vtk_out%4.4d.vtk";
maxNumberOfParticles 30000;
\} :pre
[Description:]
The data exchange model performs the data exchange between the DEM code and the CFD code. The oneWayVTK model is a model that can exchange particle properties from DEM to CFD based on previously stored VTK data.
[Restrictions:]
None.
[Related commands:]
"dataExchangeModel"_dataExchangeModel.html

50
doc/dataExchangeModel_twoWayFiles.html Normal file
View File

@ -0,0 +1,50 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>dataExchangeModel_twoWayFiles command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>dataExchangeModel twoWayFiles;
twoWayFilesProps
{
couplingFilename "filename";
maxNumberOfParticles number;
};
</PRE>
<UL><LI><I>filename</I> = filename of the VTK file series
<LI><I>number</I> = maximum nuber of particles in DEM simulation
</UL>
<P><B>Examples:</B>
</P>
<PRE>dataExchangeModel twoWayFiles;
twoWayFilesProps
{
couplingFilename "vtk_out%4.4d.vtk";
maxNumberOfParticles 30000;
}
</PRE>
<P><B>Description:</B>
</P>
<P>The data exchange model performs the data exchange between the DEM code and the CFD code. The twoWayFiles model is a model that can exchange particle properties from DEM to CFD and from CFD to DEM. Data is exchanged via files that are sequentially written/read by the codes.
</P>
<P><B>Restrictions:</B>
</P>
<P>Developed only for two processors, one for DEM and on for CFD run.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "dataExchangeModel.html">dataExchangeModel</A>
</P>
</HTML>

45
doc/dataExchangeModel_twoWayFiles.txt Normal file
View File

@ -0,0 +1,45 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
dataExchangeModel_twoWayFiles command :h3
[Syntax:]
Defined in couplingProperties dictionary.
dataExchangeModel twoWayFiles;
twoWayFilesProps
\{
couplingFilename "filename";
maxNumberOfParticles number;
\}; :pre
{filename} = filename of the VTK file series :ulb,l
{number} = maximum nuber of particles in DEM simulation :l
:ule
[Examples:]
dataExchangeModel twoWayFiles;
twoWayFilesProps
\{
couplingFilename "vtk_out%4.4d.vtk";
maxNumberOfParticles 30000;
\} :pre
[Description:]
The data exchange model performs the data exchange between the DEM code and the CFD code. The twoWayFiles model is a model that can exchange particle properties from DEM to CFD and from CFD to DEM. Data is exchanged via files that are sequentially written/read by the codes.
[Restrictions:]
Developed only for two processors, one for DEM and on for CFD run.
[Related commands:]
"dataExchangeModel"_dataExchangeModel.html

46
doc/dataExchangeModel_twoWayMPI.html Normal file
View File

@ -0,0 +1,46 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>dataExchangeModel_twoWayMPI command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>dataExchangeModel twoWayMPI;
twoWayMPIProps
{
liggghtsPath "path";
};
</PRE>
<UL><LI><I>path</I> = path to the DEM simulation input file
</UL>
<P><B>Examples:</B>
</P>
<PRE>dataExchangeModel twoWayMPI;
twoWayMPIProps
{
liggghtsPath "../DEM/in.liggghts_init";
}
</PRE>
<P><B>Description:</B>
</P>
<P>The data exchange model performs the data exchange between the DEM code and the CFD code. The twoWayMPI model is a model that can exchange particle properties from DEM to CFD and from CFD to DEM. Data is exchanged via MPI technique. The DEM run is executed by the coupling model, via a liggghtsCommandModel object.
</P>
<P><B>Restrictions:</B>
</P>
<P>none.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "dataExchangeModel.html">dataExchangeModel</A>
</P>
</HTML>

42
doc/dataExchangeModel_twoWayMPI.txt Normal file
View File

@ -0,0 +1,42 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
dataExchangeModel_twoWayMPI command :h3
[Syntax:]
Defined in couplingProperties dictionary.
dataExchangeModel twoWayMPI;
twoWayMPIProps
\{
liggghtsPath "path";
\}; :pre
{path} = path to the DEM simulation input file :ulb,l
:ule
[Examples:]
dataExchangeModel twoWayMPI;
twoWayMPIProps
\{
liggghtsPath "../DEM/in.liggghts_init";
\} :pre
[Description:]
The data exchange model performs the data exchange between the DEM code and the CFD code. The twoWayMPI model is a model that can exchange particle properties from DEM to CFD and from CFD to DEM. Data is exchanged via MPI technique. The DEM run is executed by the coupling model, via a liggghtsCommandModel object.
[Restrictions:]
none.
[Related commands:]
"dataExchangeModel"_dataExchangeModel.html

50
doc/forceModel.html Normal file
View File

@ -0,0 +1,50 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>forceModel command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>forceModels
(
model_x
model_y
);
</PRE>
<UL><LI>model = name of force model to be applied
</UL>
<P><B>Examples:</B>
</P>
<PRE>forceModels
(
Archimedes
DiFeliceDrag
);
</PRE>
<P>Note: This examples list might not be complete - please look for other models (forceModel_XY) in this documentation.
</P>
<P><B>Description:</B>
</P>
<P>The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. All force models selected are executed sequentially and the forces on the particles are superposed.
</P>
<P><B>Restrictions:</B>
</P>
<P>None.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "forceModel_Archimedes.html">Archimedes</A>, <A HREF = "forceModel_DiFeliceDrag.html">DiFeliceDrag</A>, <A HREF = "forceModel_gradPForce.html">gradPForce</A>, <A HREF = "forceModel_viscForce.html">viscForce</A>
</P>
<P>Note: This examples list may be incomplete - please look for other models (forceModel_XY) in this documentation.
</P>
<P><B>Default:</B> none.
</P>
</HTML>

46
doc/forceModel.txt Normal file
View File

@ -0,0 +1,46 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
forceModel command :h3
[Syntax:]
Defined in couplingProperties dictionary.
forceModels
(
model_x
model_y
); :pre
model = name of force model to be applied :ul
[Examples:]
forceModels
(
Archimedes
DiFeliceDrag
); :pre
Note: This examples list might not be complete - please look for other models (forceModel_XY) in this documentation.
[Description:]
The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. All force models selected are executed sequentially and the forces on the particles are superposed.
[Restrictions:]
None.
[Related commands:]
"Archimedes"_forceModel_Archimedes.html, "DiFeliceDrag"_forceModel_DiFeliceDrag.html, "gradPForce"_forceModel_gradPForce.html, "viscForce"_forceModel_viscForce.html
Note: This examples list may be incomplete - please look for other models (forceModel_XY) in this documentation.
[Default:] none.

56
doc/forceModel_Archimedes.html Normal file
View File

@ -0,0 +1,56 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>forceModel_Archimedes command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>forceModels
(
Archimedes
);
ArchimedesProps
{
densityFieldName "density";
gravityFieldName "gravity";
};
</PRE>
<UL><LI><I>density</I> = name of the finite volume density field
<LI><I>gravity</I> = name of the finite volume gravity field
</UL>
<P><B>Examples:</B>
</P>
<PRE>forceModels
(
Archimedes
);
ArchimedesProps
{
densityFieldName "rho";
gravityFieldName "g";
}
</PRE>
<P><B>Description:</B>
</P>
<P>The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The Archimedes model is a model that calculates the Archimedes' volumetric lift force stemming from density difference of fluid and particle.
</P>
<P><B>Restrictions:</B>
</P>
<P>none.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "forceModel.html">forceModel</A>
</P>
</HTML>

51
doc/forceModel_Archimedes.txt Normal file
View File

@ -0,0 +1,51 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
forceModel_Archimedes command :h3
[Syntax:]
Defined in couplingProperties dictionary.
forceModels
(
Archimedes
);
ArchimedesProps
\{
densityFieldName "density";
gravityFieldName "gravity";
\}; :pre
{density} = name of the finite volume density field :ulb,l
{gravity} = name of the finite volume gravity field :l
:ule
[Examples:]
forceModels
(
Archimedes
);
ArchimedesProps
\{
densityFieldName "rho";
gravityFieldName "g";
\} :pre
[Description:]
The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The Archimedes model is a model that calculates the Archimedes' volumetric lift force stemming from density difference of fluid and particle.
[Restrictions:]
none.
[Related commands:]
"forceModel"_forceModel.html

56
doc/forceModel_ArchimedesIB.html Normal file
View File

@ -0,0 +1,56 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>forceModel_ArchimedesIB command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>forceModels
(
ArchimedesIB
);
ArchimedesIBProps
{
densityFieldName "density";
gravityFieldName "gravity";
};
</PRE>
<UL><LI><I>density</I> = name of the finite volume density field
<LI><I>gravity</I> = name of the finite volume gravity field
</UL>
<P><B>Examples:</B>
</P>
<PRE>forceModels
(
ArchimedesIB
);
ArchimedesIBProps
{
densityFieldName "rho";
gravityFieldName "g";
}
</PRE>
<P><B>Description:</B>
</P>
<P>The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The ArchimedesIB model is a model that calculates the ArchimedesIB' volumetric lift force stemming from density difference of fluid and particle. This model is especially suited for resolved CFD-DEM simulations where the particle is represented by immersed boundrary method.
</P>
<P><B>Restrictions:</B>
</P>
<P>Only for immersed boundary solvers.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "forceModel.html">forceModel</A>
</P>
</HTML>

51
doc/forceModel_ArchimedesIB.txt Normal file
View File

@ -0,0 +1,51 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
forceModel_ArchimedesIB command :h3
[Syntax:]
Defined in couplingProperties dictionary.
forceModels
(
ArchimedesIB
);
ArchimedesIBProps
\{
densityFieldName "density";
gravityFieldName "gravity";
\}; :pre
{density} = name of the finite volume density field :ulb,l
{gravity} = name of the finite volume gravity field :l
:ule
[Examples:]
forceModels
(
ArchimedesIB
);
ArchimedesIBProps
\{
densityFieldName "rho";
gravityFieldName "g";
\} :pre
[Description:]
The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The ArchimedesIB model is a model that calculates the ArchimedesIB' volumetric lift force stemming from density difference of fluid and particle. This model is especially suited for resolved CFD-DEM simulations where the particle is represented by immersed boundrary method.
[Restrictions:]
Only for immersed boundary solvers.
[Related commands:]
"forceModel"_forceModel.html

60
doc/forceModel_DiFeliceDrag.html Normal file
View File

@ -0,0 +1,60 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>forceModel_DiFeliceDrag command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>forceModels
(
DiFeliceDrag
);
DiFeliceDragProps
{
velFieldName "U";
densityFieldName "density";
interpolation;
};
</PRE>
<UL><LI><I>U</I> = name of the finite volume fluid velocity field
<LI><I>density</I> = name of the finite volume gravity field
<LI><I>interpolation</I> = flag to use interolate interpolated voidfraction and velocity values (normally off)
</UL>
<P><B>Examples:</B>
</P>
<PRE>forceModels
(
DiFeliceDrag
);
DiFeliceDragProps
{
velFieldName "U";
densityFieldName "rho";
interpolation;
}
</PRE>
<P><B>Description:</B>
</P>
<P>The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The DiFeliceDrag model is a model that calculates the particle based drag force following the correlation of Di Felice (see Zhou et al. (2010), JFM).
</P>
<P><B>Restrictions:</B>
</P>
<P>none.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "forceModel.html">forceModel</A>
</P>
</HTML>

54
doc/forceModel_DiFeliceDrag.txt Normal file
View File

@ -0,0 +1,54 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
forceModel_DiFeliceDrag command :h3
[Syntax:]
Defined in couplingProperties dictionary.
forceModels
(
DiFeliceDrag
);
DiFeliceDragProps
\{
velFieldName "U";
densityFieldName "density";
interpolation;
\}; :pre
{U} = name of the finite volume fluid velocity field :ulb,l
{density} = name of the finite volume gravity field :l
{interpolation} = flag to use interolate interpolated voidfraction and velocity values (normally off) :l
:ule
[Examples:]
forceModels
(
DiFeliceDrag
);
DiFeliceDragProps
\{
velFieldName "U";
densityFieldName "rho";
interpolation;
\} :pre
[Description:]
The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The DiFeliceDrag model is a model that calculates the particle based drag force following the correlation of Di Felice (see Zhou et al. (2010), JFM).
[Restrictions:]
none.
[Related commands:]
"forceModel"_forceModel.html

56
doc/forceModel_GidaspowDrag.html Normal file
View File

@ -0,0 +1,56 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>forceModel_GidaspowDrag command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>forceModels
(
GidaspowDrag
);
GidaspowDragProps
{
velFieldName "U";
densityFieldName "density";
};
</PRE>
<UL><LI><I>U</I> = name of the finite volume fluid velocity field
<LI><I>density</I> = name of the finite volume gravity field
</UL>
<P><B>Examples:</B>
</P>
<PRE>forceModels
(
GidaspowDrag
);
GidaspowDragProps
{
velFieldName "U";
densityFieldName "rho";
}
</PRE>
<P><B>Description:</B>
</P>
<P>The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The GidaspowDrag model is a model that calculates the particle based drag force following the correlation of Gidaspow which is a combination of Egrun (1952) and Wen & Yu (1966) (see Zhu et al. (2007): "Discrete particle simulation of particulate systems: Theoretical developments" ,ChemEngScience).
</P>
<P><B>Restrictions:</B>
</P>
<P>none.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "forceModel.html">forceModel</A>
</P>
</HTML>

51
doc/forceModel_GidaspowDrag.txt Normal file
View File

@ -0,0 +1,51 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
forceModel_GidaspowDrag command :h3
[Syntax:]
Defined in couplingProperties dictionary.
forceModels
(
GidaspowDrag
);
GidaspowDragProps
\{
velFieldName "U";
densityFieldName "density";
\}; :pre
{U} = name of the finite volume fluid velocity field :ulb,l
{density} = name of the finite volume gravity field :l
:ule
[Examples:]
forceModels
(
GidaspowDrag
);
GidaspowDragProps
\{
velFieldName "U";
densityFieldName "rho";
\} :pre
[Description:]
The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The GidaspowDrag model is a model that calculates the particle based drag force following the correlation of Gidaspow which is a combination of Egrun (1952) and Wen & Yu (1966) (see Zhu et al. (2007): "Discrete particle simulation of particulate systems: Theoretical developments" ,ChemEngScience).
[Restrictions:]
none.
[Related commands:]
"forceModel"_forceModel.html

63
doc/forceModel_KochHillDrag.html Normal file
View File

@ -0,0 +1,63 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>forceModel_KochHillDrag command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>forceModels
(
KochHillDrag
);
KochHillDragProps
{
velFieldName "U";
densityFieldName "density";
voidfractionFieldName "voidfraction";
interpolation;
};
</PRE>
<UL><LI><I>U</I> = name of the finite volume fluid velocity field
<LI><I>density</I> = name of the finite volume gravity field
<LI><I>voidfraction</I> = name of the finite volume voidfraction field
<LI><I>interpolation</I> = flag to use interolate interpolated voidfraction and fluid velocity values (normally off)
</UL>
<P><B>Examples:</B>
</P>
<PRE>forceModels
(
KochHillDrag
);
KochHillDragProps
{
velFieldName "U";
densityFieldName "rho";
voidfractionFieldName "voidfraction";
}
</PRE>
<P><B>Description:</B>
</P>
<P>The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The KochHillDrag model is a model that calculates the particle based drag force following the correlation of Koch & Hill (2001) (see van Buijtenen et al. (2011): "Numerical and experimental study on multiple-spout fluidized beds" ,ChemEngScience).
</P>
<P><B>Restrictions:</B>
</P>
<P>none.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "forceModel.html">forceModel</A>
</P>
</HTML>

56
doc/forceModel_KochHillDrag.txt Normal file
View File

@ -0,0 +1,56 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
forceModel_KochHillDrag command :h3
[Syntax:]
Defined in couplingProperties dictionary.
forceModels
(
KochHillDrag
);
KochHillDragProps
\{
velFieldName "U";
densityFieldName "density";
voidfractionFieldName "voidfraction";
interpolation;
\}; :pre
{U} = name of the finite volume fluid velocity field :ulb,l
{density} = name of the finite volume gravity field :l
{voidfraction} = name of the finite volume voidfraction field :l
{interpolation} = flag to use interolate interpolated voidfraction and fluid velocity values (normally off) :l
:ule
[Examples:]
forceModels
(
KochHillDrag
);
KochHillDragProps
\{
velFieldName "U";
densityFieldName "rho";
voidfractionFieldName "voidfraction";
\} :pre
[Description:]
The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The KochHillDrag model is a model that calculates the particle based drag force following the correlation of Koch & Hill (2001) (see van Buijtenen et al. (2011): "Numerical and experimental study on multiple-spout fluidized beds" ,ChemEngScience).
[Restrictions:]
none.
[Related commands:]
"forceModel"_forceModel.html

84
doc/forceModel_LaEuScalarTemp.html Normal file
View File

@ -0,0 +1,84 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>forceModel_LaEuScalarTemp command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>forceModels
(
LaEuScalarTemp
);
LaEuScalarTempProps
{
velFieldName "U";
tempFieldName "T";
tempSourceFieldName "Tsource";
voidfractionFieldName "voidfraction";
partTempName "Temp";
partHeatFluxName "convectiveHeatFlux";
lambda value;
Cp value1;
densityFieldName "density";
};
</PRE>
<UL><LI><I>U</I> = name of the finite volume fluid velocity field
<LI><I>T</I> = name of the finite volume scalar temperature field
<LI><I>Tsource</I> = name of the finite volume scalar temperature source field
<LI><I>voidfraction</I> = name of the finite volume voidfraction field
<LI><I>Temp</I> = name of the DEM data representing the particles temperature
<LI><I>convectiveHeatFlux</I> = name of the DEM data representing the particle-fluid convective heat flux
<LI><I>value</I> = fluid thermal conductivity [W/(m*K)]
<LI><I>value1</I> = fluid specific heat capacity [W*s/(kg*K)]
<LI><I>density</I> = name of the finite volume fluid density field
</UL>
<P><B>Examples:</B>
</P>
<PRE>forceModels
(
LaEuScalarTemp
);
LaEuScalarTempProps
{
velFieldName "U";
tempFieldName "T";
tempSourceFieldName "Tsource";
voidfractionFieldName "voidfraction";
partTempName "Temp";
partHeatFluxName "convectiveHeatFlux";
lambda 0.0256;
Cp 1007;
densityFieldName "rho";
}
</PRE>
<P><B>Description:</B>
</P>
<P>This "forceModel" does not influence the particles or the fluid flow! Using the particles' temperature a scalar field representing "particle-fluid heatflux" is calculated. The solver then uses this source field in the scalar transport equation for the temperature. The model for convective heat transfer is based on Li and Mason (2000), A computational investigation of transient heat transfer in pneumatic transport of granular particles, Pow.Tech 112
</P>
<P><B>Restrictions:</B>
</P>
<P>Goes only with cfdemSolverScalar.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "forceModel.html">forceModel</A>
</P>
</HTML>

72
doc/forceModel_LaEuScalarTemp.txt Normal file
View File

@ -0,0 +1,72 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
forceModel_LaEuScalarTemp command :h3
[Syntax:]
Defined in couplingProperties dictionary.
forceModels
(
LaEuScalarTemp
);
LaEuScalarTempProps
\{
velFieldName "U";
tempFieldName "T";
tempSourceFieldName "Tsource";
voidfractionFieldName "voidfraction";
partTempName "Temp";
partHeatFluxName "convectiveHeatFlux";
lambda value;
Cp value1;
densityFieldName "density";
\}; :pre
{U} = name of the finite volume fluid velocity field :ulb,l
{T} = name of the finite volume scalar temperature field :l
{Tsource} = name of the finite volume scalar temperature source field :l
{voidfraction} = name of the finite volume voidfraction field :l
{Temp} = name of the DEM data representing the particles temperature :l
{convectiveHeatFlux} = name of the DEM data representing the particle-fluid convective heat flux :l
{value} = fluid thermal conductivity \[W/(m*K)\] :l
{value1} = fluid specific heat capacity \[W*s/(kg*K)\] :l
{density} = name of the finite volume fluid density field :l
:ule
[Examples:]
forceModels
(
LaEuScalarTemp
);
LaEuScalarTempProps
\{
velFieldName "U";
tempFieldName "T";
tempSourceFieldName "Tsource";
voidfractionFieldName "voidfraction";
partTempName "Temp";
partHeatFluxName "convectiveHeatFlux";
lambda 0.0256;
Cp 1007;
densityFieldName "rho";
\} :pre
[Description:]
This "forceModel" does not influence the particles or the fluid flow! Using the particles' temperature a scalar field representing "particle-fluid heatflux" is calculated. The solver then uses this source field in the scalar transport equation for the temperature. The model for convective heat transfer is based on Li and Mason (2000), A computational investigation of transient heat transfer in pneumatic transport of granular particles, Pow.Tech 112
[Restrictions:]
Goes only with cfdemSolverScalar.
[Related commands:]
"forceModel"_forceModel.html

56
doc/forceModel_MeiLift.html Normal file
View File

@ -0,0 +1,56 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>forceModel_MeiLift command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>forceModels
(
MeiLift
);
MeiLiftProps
{
velFieldName "U";
densityFieldName "density";
};
</PRE>
<UL><LI><I>U</I> = name of the finite volume fluid velocity field
<LI><I>density</I> = name of the finite volume fluid density field
</UL>
<P><B>Examples:</B>
</P>
<PRE>forceModels
(
MeiLift
);
MeiLiftProps
{
velFieldName "U";
densityFieldName "rho";
}
</PRE>
<P><B>Description:</B>
</P>
<P>The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The MeiLift model calculates the lift force for each particle based on Loth and Dorgan (2009)
</P>
<P><B>Restrictions:</B>
</P>
<P>None.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "forceModel.html">forceModel</A>
</P>
</HTML>

51
doc/forceModel_MeiLift.txt Normal file
View File

@ -0,0 +1,51 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
forceModel_MeiLift command :h3
[Syntax:]
Defined in couplingProperties dictionary.
forceModels
(
MeiLift
);
MeiLiftProps
\{
velFieldName "U";
densityFieldName "density";
\}; :pre
{U} = name of the finite volume fluid velocity field :ulb,l
{density} = name of the finite volume fluid density field :l
:ule
[Examples:]
forceModels
(
MeiLift
);
MeiLiftProps
\{
velFieldName "U";
densityFieldName "rho";
\} :pre
[Description:]
The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The MeiLift model calculates the lift force for each particle based on Loth and Dorgan (2009)
[Restrictions:]
None.
[Related commands:]
"forceModel"_forceModel.html

56
doc/forceModel_SchillerNaumannDrag.html Normal file
View File

@ -0,0 +1,56 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>forceModel_SchillerNaumannDrag command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>forceModels
(
SchillerNaumannDrag
);
SchillerNaumannDragProps
{
velFieldName "U";
densityFieldName "density";
};
</PRE>
<UL><LI><I>U</I> = name of the finite volume fluid velocity field
<LI><I>density</I> = name of the finite volume gravity field
</UL>
<P><B>Examples:</B>
</P>
<PRE>forceModels
(
SchillerNaumannDrag
);
SchillerNaumannDragProps
{
velFieldName "U";
densityFieldName "rho";
}
</PRE>
<P><B>Description:</B>
</P>
<P>The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The SchillerNaumannDrag model is a model that calculates the particle based drag force following the correlation of Schiller and Naumann.
</P>
<P><B>Restrictions:</B>
</P>
<P>none.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "forceModel.html">forceModel</A>
</P>
</HTML>

51
doc/forceModel_SchillerNaumannDrag.txt Normal file
View File

@ -0,0 +1,51 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
forceModel_SchillerNaumannDrag command :h3
[Syntax:]
Defined in couplingProperties dictionary.
forceModels
(
SchillerNaumannDrag
);
SchillerNaumannDragProps
\{
velFieldName "U";
densityFieldName "density";
\}; :pre
{U} = name of the finite volume fluid velocity field :ulb,l
{density} = name of the finite volume gravity field :l
:ule
[Examples:]
forceModels
(
SchillerNaumannDrag
);
SchillerNaumannDragProps
\{
velFieldName "U";
densityFieldName "rho";
\} :pre
[Description:]
The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The SchillerNaumannDrag model is a model that calculates the particle based drag force following the correlation of Schiller and Naumann.
[Restrictions:]
none.
[Related commands:]
"forceModel"_forceModel.html

60
doc/forceModel_ShirgaonkarIB.html Normal file
View File

@ -0,0 +1,60 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>forceModel_SchirgaonkarIB command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>forceModels
(
SchirgaonkarIB
);
SchirgaonkarIBProps
{
velFieldName "U";
densityFieldName "density";
pressureFieldName "pressure";
};
</PRE>
<UL><LI><I>U</I> = name of the finite volume fluid velocity field
<LI><I>density</I> = name of the finite volume density field
<LI><I>pressure</I> = name of the finite volume pressure field
</UL>
<P><B>Examples:</B>
</P>
<PRE>forceModels
(
SchirgaonkarIB
);
SchirgaonkarIBProps
{
velFieldName "U";
densityFieldName "rho";
pressureFieldName "p";
}
</PRE>
<P><B>Description:</B>
</P>
<P>The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The SchirgaonkarIB model calculates the drag force (viscous and pressure force) acting on each particle in a resolved manner (see Shirgaonkar et al. (2009): "A new mathematical formulation and fast algorithm for fully resolved simulation of self-propulsion", Journal of Comp. Physics). This model is only suited for resolved CFD-DEM simulations where the particle is represented by immersed boundrary method.
</P>
<P><B>Restrictions:</B>
</P>
<P>Only for immersed boundary solvers.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "forceModel.html">forceModel</A>
</P>
</HTML>

54
doc/forceModel_ShirgaonkarIB.txt Normal file
View File

@ -0,0 +1,54 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
forceModel_SchirgaonkarIB command :h3
[Syntax:]
Defined in couplingProperties dictionary.
forceModels
(
SchirgaonkarIB
);
SchirgaonkarIBProps
\{
velFieldName "U";
densityFieldName "density";
pressureFieldName "pressure";
\}; :pre
{U} = name of the finite volume fluid velocity field :ulb,l
{density} = name of the finite volume density field :l
{pressure} = name of the finite volume pressure field :l
:ule
[Examples:]
forceModels
(
SchirgaonkarIB
);
SchirgaonkarIBProps
\{
velFieldName "U";
densityFieldName "rho";
pressureFieldName "p";
\} :pre
[Description:]
The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The SchirgaonkarIB model calculates the drag force (viscous and pressure force) acting on each particle in a resolved manner (see Shirgaonkar et al. (2009): "A new mathematical formulation and fast algorithm for fully resolved simulation of self-propulsion", Journal of Comp. Physics). This model is only suited for resolved CFD-DEM simulations where the particle is represented by immersed boundrary method.
[Restrictions:]
Only for immersed boundary solvers.
[Related commands:]
"forceModel"_forceModel.html

64
doc/forceModel_gradPForce.html Normal file
View File

@ -0,0 +1,64 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>forceModel_gradPForce command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>forceModels
(
gradPForce;
);
gradPForceProps
{
pFieldName "pressure";
densityFieldName "density";
velocityFieldName "U";
interpolation;
};
</PRE>
<UL><LI><I>pressure</I> = name of the finite volume fluid pressure field
<LI><I>density</I> = name of the finite volume gravity field
<LI><I>U</I> = name of the finite volume fluid velocity field
<LI><I>interpolation</I> = flag to use interolate interpolated pressure values (normally off)
</UL>
<P><B>Examples:</B>
</P>
<PRE>forceModels
(
gradPForce;
);
gradPForceProps
{
pFieldName "p";
densityFieldName "rho";
velocityFieldName "U";
interpolation;
}
</PRE>
<P><B>Description:</B>
</P>
<P>The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The gradPForce model is a model that calculates the particle based pressure gradient force -(grad(p)) * Vparticle (see Zhou et al. (2010): "Discrete particle simulation of particle-fluid flow: model formulations and their applicability" ,JFM).
</P>
<P><B>Restrictions:</B>
</P>
<P>none.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "forceModel.html">forceModel</A>
</P>
</HTML>

57
doc/forceModel_gradPForce.txt Normal file
View File

@ -0,0 +1,57 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
forceModel_gradPForce command :h3
[Syntax:]
Defined in couplingProperties dictionary.
forceModels
(
gradPForce;
);
gradPForceProps
\{
pFieldName "pressure";
densityFieldName "density";
velocityFieldName "U";
interpolation;
\}; :pre
{pressure} = name of the finite volume fluid pressure field :ulb,l
{density} = name of the finite volume gravity field :l
{U} = name of the finite volume fluid velocity field :l
{interpolation} = flag to use interolate interpolated pressure values (normally off) :l
:ule
[Examples:]
forceModels
(
gradPForce;
);
gradPForceProps
\{
pFieldName "p";
densityFieldName "rho";
velocityFieldName "U";
interpolation;
\} :pre
[Description:]
The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The gradPForce model is a model that calculates the particle based pressure gradient force -(grad(p)) * Vparticle (see Zhou et al. (2010): "Discrete particle simulation of particle-fluid flow: model formulations and their applicability" ,JFM).
[Restrictions:]
none.
[Related commands:]
"forceModel"_forceModel.html

40
doc/forceModel_noDrag.html Normal file
View File

@ -0,0 +1,40 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>forceModel_noDrag command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>forceModels
(
off
);
</PRE>
<P><B>Examples:</B>
</P>
<PRE>forceModels
(
off
);
</PRE>
<P><B>Description:</B>
</P>
<P>The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The noDrag model sets the forces acting on the particle to zero. If several force models are selected and noDrag is the last model being executed, the fluid particle force will be set to zero.
</P>
<P><B>Restrictions:</B>
</P>
<P>None.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "forceModel.html">forceModel</A>
</P>
</HTML>

37
doc/forceModel_noDrag.txt Normal file
View File

@ -0,0 +1,37 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
forceModel_noDrag command :h3
[Syntax:]
Defined in couplingProperties dictionary.
forceModels
(
off
); :pre
[Examples:]
forceModels
(
off
); :pre
[Description:]
The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The noDrag model sets the forces acting on the particle to zero. If several force models are selected and noDrag is the last model being executed, the fluid particle force will be set to zero.
[Restrictions:]
None.
[Related commands:]
"forceModel"_forceModel.html

56
doc/forceModel_virtualMassForce.html Normal file
View File

@ -0,0 +1,56 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>forceModel_virtualMassForce command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>forceModels
(
virtualMassForce
);
virtualMassForceProps
{
velFieldName "U";
densityFieldName "density";
};
</PRE>
<UL><LI><I>U</I> = name of the finite volume fluid velocity field
<LI><I>density</I> = name of the finite volume fluid density field
</UL>
<P><B>Examples:</B>
</P>
<PRE>forceModels
(
virtualMassForce
);
virtualMassForceProps
{
velFieldName "U";
densityFieldName "rho";
}
</PRE>
<P><B>Description:</B>
</P>
<P>The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The virtualMassForce model calculates the virtual mass force for each particle.
</P>
<P><B>Restrictions:</B>
</P>
<P>Model not validated!
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "forceModel.html">forceModel</A>
</P>
</HTML>

51
doc/forceModel_virtualMassForce.txt Normal file
View File

@ -0,0 +1,51 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
forceModel_virtualMassForce command :h3
[Syntax:]
Defined in couplingProperties dictionary.
forceModels
(
virtualMassForce
);
virtualMassForceProps
\{
velFieldName "U";
densityFieldName "density";
\}; :pre
{U} = name of the finite volume fluid velocity field :ulb,l
{density} = name of the finite volume fluid density field :l
:ule
[Examples:]
forceModels
(
virtualMassForce
);
virtualMassForceProps
\{
velFieldName "U";
densityFieldName "rho";
\} :pre
[Description:]
The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The virtualMassForce model calculates the virtual mass force for each particle.
[Restrictions:]
Model not validated!
[Related commands:]
"forceModel"_forceModel.html

59
doc/forceModel_viscForce.html Normal file
View File

@ -0,0 +1,59 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>forceModel_viscForce command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>forceModels
(
viscForce;
);
viscForceProps
{
velocityFieldName "U";
densityFieldName "density";
interpolation;
};
</PRE>
<UL><LI><I>U</I> = name of the finite volume fluid velocity field
<LI><I>density</I> = name of the finite volume gravity field
<LI><I>interpolation</I> = flag to use interolate interpolated stress values (normally off)
</UL>
<P><B>Examples:</B>
</P>
<PRE>forceModels
(
viscForce;
);
viscForceProps
{
velocityFieldName "U";
densityFieldName "density";
}
</PRE>
<P><B>Description:</B>
</P>
<P>The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The viscForce model calculates the particle based viscous force, -(grad(tau)) * Vparticle (see Zhou et al. (2010): "Discrete particle simulation of particle-fluid flow: model formulations and their applicability" ,JFM).
</P>
<P><B>Restrictions:</B>
</P>
<P>none.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "forceModel.html">forceModel</A>
</P>
</HTML>

53
doc/forceModel_viscForce.txt Normal file
View File

@ -0,0 +1,53 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
forceModel_viscForce command :h3
[Syntax:]
Defined in couplingProperties dictionary.
forceModels
(
viscForce;
);
viscForceProps
\{
velocityFieldName "U";
densityFieldName "density";
interpolation;
\}; :pre
{U} = name of the finite volume fluid velocity field :ulb,l
{density} = name of the finite volume gravity field :l
{interpolation} = flag to use interolate interpolated stress values (normally off) :l
:ule
[Examples:]
forceModels
(
viscForce;
);
viscForceProps
\{
velocityFieldName "U";
densityFieldName "density";
\} :pre
[Description:]
The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The viscForce model calculates the particle based viscous force, -(grad(tau)) * Vparticle (see Zhou et al. (2010): "Discrete particle simulation of particle-fluid flow: model formulations and their applicability" ,JFM).
[Restrictions:]
none.
[Related commands:]
"forceModel"_forceModel.html

142
doc/githubAccess_public.html Normal file
View File

@ -0,0 +1,142 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>githubAccess_public
</H3>
<HR>
<P><B>Description:</B>
</P>
<P>This routine describes how to setup a github account and pull repositories of the CFDEMproject.
After setting some environment variables LIGGGHTS and CFDEMcoupling can be compiled
</P>
<P><B>Procedure:</B>
</P>
<P>Basically the following steps have to be performed:
</P>
<UL><LI><I>git clone</I> the desired repository
<LI>update your repositories by <I>git pull</I>
<LI>set environment variables
<LI>compile LIGGGHTS and CFDEMcoupling
</UL>
<P><B><I>git clone</I> the desired repository:</B>
</P>
<P>If not allready done, open a terminal and create a directory for LIGGGHTS in $HOME:
</P>
<PRE>cd
</PRE>
<PRE>mkdir LIGGGHTS
</PRE>
<PRE>cd LIGGGHTS
</PRE>
<P>To clone the public LIGGGHTS repository, open a terminal and execute:
</P>
<PRE><H6>git clone git://cfdem.git.sourceforge.net/gitroot/cfdem/liggghtsdev LIGGGHTS-PUBLIC
</H6></PRE>
<P>If not allready done, open a terminal and create a directory for CFDEMcoupling in $HOME:
</P>
<PRE>cd
</PRE>
<PRE>mkdir CFDEM
</PRE>
<PRE>cd CFDEM
</PRE>
<P>Make sure that OpenFOAM(R)-2.1.x is allready set up correctly!
</P>
<P>To clone the public CFDEMcoupling repository, open a terminal and execute:
</P>
<PRE><H6>git clone git://github.com/CFDEMproject/CFDEMcoupling-PUBLIC.git CFDEMcoupling-PUBLIC-$WM_PROJECT_VERSION
</H6></PRE>
<P>Note: the git protocol will not work if your computer is behind a firewall which blocks the relevant TCP port, you can use alternatively:
</P>
<PRE>git clone https://github.com/CFDEMproject/CFDEMcoupling-PUBLIC.git
</PRE>
<P><B>Update your repositories by <I>git pull</I>:</B>
</P>
<P>To get the latest version, open a terminal, go to the location of your local installation and type:
</P>
<PRE>cd $HOME/CFDEM/CFDEMcoupling-PUBLIC-$WM_PROJECT_VERSION
git pull
</PRE>
<P><B>set environment variables:</B>
</P>
<P>Now you need to set some environment variables in ~/.bashrc (if you use c-shell, manipulate ~/.cshrc accordingly). Open ~/.bashrc
</P>
<PRE>gedit ~/.bashrc &
</PRE>
<P>add the lines:
</P>
<PRE>#================================================#
#- source cfdem env vars
export CFDEM_VERSION=PUBLIC
export CFDEM_PROJECT_DIR=$HOME/CFDEM/CFDEMcoupling-$CFDEM_VERSION-$WM_PROJECT_VERSION
export CFDEM_SRC_DIR=$CFDEM_PROJECT_DIR/src/lagrangian/cfdemParticle
export CFDEM_SOLVER_DIR=$CFDEM_PROJECT_DIR/applications/solvers
export CFDEM_DOC_DIR=$CFDEM_PROJECT_DIR/doc
export CFDEM_UT_DIR=$CFDEM_PROJECT_DIR/applications/utilities
export CFDEM_TUT_DIR=$CFDEM_PROJECT_DIR/tutorials
export CFDEM_PROJECT_USER_DIR=$HOME/CFDEM/$LOGNAME-$CFDEM_VERSION-$WM_PROJECT_VERSION
export CFDEM_bashrc=$CFDEM_SRC_DIR/etc/bashrc
export CFDEM_LIGGGHTS_SRC_DIR=$HOME/LIGGGHTS/LIGGGHTS-PUBLIC/src
export CFDEM_LIGGGHTS_MAKEFILE_NAME=fedora_fpic
. $CFDEM_bashrc
#================================================#
</PRE>
<P>Save the ~/.bashrc, open a new terminal and test the settings. The commands:
</P>
<PRE>$CFDEM_PROJECT_DIR
$CFDEM_SRC_DIR
$CFDEM_LIGGGHTS_SRC_DIR
</PRE>
<P>should give "...: is a directory" otherwise something went wrong and the environment variables in ~/bashrc are not set correctly.
</P>
<P>To specify the paths of pizza, please check the settings in $CFDEM_SRC_DIR/etc/bashrc.
</P>
<P>If $CFDEM_SRC_DIR is set correctly, you can type
</P>
<P>sdsd
cd
scds
cdsc
c
cds
c
</P>
<PRE>cfdemSysTest
</PRE>
<P>to get some information if the paths are set correctly.
</P>
<P>kacke
</P>
<P>If above settings were done correctly, you can compile LIGGGHTS by typing:
</P>
<PRE>cfdemCompLIG
</PRE>
<P>cdsc
sdc
sc
scv
v
cv
scv
sc
dsc
dssd
c
</P>
</HTML>

111
doc/githubAccess_public.txt Normal file
View File

@ -0,0 +1,111 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:link(github,http://github.com)
:link(gitHelp,http://help.github.com/linux-set-up-git)
:line
githubAccess_public :h3
:line
[Description:]
This routine describes how to setup a github account and pull repositories of the CFDEMproject.
After setting some environment variables LIGGGHTS and CFDEMcoupling can be compiled
[Procedure:]
Basically the following steps have to be performed:
{git clone} the desired repository :ulb,l
update your repositories by {git pull} :l
set environment variables :l
compile LIGGGHTS and CFDEMcoupling :l
:ule
[{git clone} the desired repository:]
If not allready done, open a terminal and create a directory for LIGGGHTS in $HOME:
cd :pre
mkdir LIGGGHTS :pre
cd LIGGGHTS :pre
To clone the public LIGGGHTS repository, open a terminal and execute:
git clone git://cfdem.git.sourceforge.net/gitroot/cfdem/liggghtsdev LIGGGHTS-PUBLIC :pre,h6
If not allready done, open a terminal and create a directory for CFDEMcoupling in $HOME:
cd :pre
mkdir CFDEM :pre
cd CFDEM :pre
Make sure that OpenFOAM(R)-2.1.x is allready set up correctly!
To clone the public CFDEMcoupling repository, open a terminal and execute:
git clone git://github.com/CFDEMproject/CFDEMcoupling-PUBLIC.git CFDEMcoupling-PUBLIC-$WM_PROJECT_VERSION :pre,h6
Note: the git protocol will not work if your computer is behind a firewall which blocks the relevant TCP port, you can use alternatively:
git clone https://github.com/CFDEMproject/CFDEMcoupling-PUBLIC.git :pre
[Update your repositories by {git pull}:]
To get the latest version, open a terminal, go to the location of your local installation and type:
cd $HOME/CFDEM/CFDEMcoupling-PUBLIC-$WM_PROJECT_VERSION
git pull :pre
[set environment variables:]
Now you need to set some environment variables in ~/.bashrc (if you use c-shell, manipulate ~/.cshrc accordingly). Open ~/.bashrc
gedit ~/.bashrc & :pre
add the lines:
#================================================#
#- source cfdem env vars
export CFDEM_VERSION=PUBLIC
export CFDEM_PROJECT_DIR=$HOME/CFDEM/CFDEMcoupling-$CFDEM_VERSION-$WM_PROJECT_VERSION
export CFDEM_SRC_DIR=$CFDEM_PROJECT_DIR/src/lagrangian/cfdemParticle
export CFDEM_SOLVER_DIR=$CFDEM_PROJECT_DIR/applications/solvers
export CFDEM_DOC_DIR=$CFDEM_PROJECT_DIR/doc
export CFDEM_UT_DIR=$CFDEM_PROJECT_DIR/applications/utilities
export CFDEM_TUT_DIR=$CFDEM_PROJECT_DIR/tutorials
export CFDEM_PROJECT_USER_DIR=$HOME/CFDEM/$LOGNAME-$CFDEM_VERSION-$WM_PROJECT_VERSION
export CFDEM_bashrc=$CFDEM_SRC_DIR/etc/bashrc
export CFDEM_LIGGGHTS_SRC_DIR=$HOME/LIGGGHTS/LIGGGHTS-PUBLIC/src
export CFDEM_LIGGGHTS_MAKEFILE_NAME=fedora_fpic
. $CFDEM_bashrc
#================================================# :pre
Save the ~/.bashrc, open a new terminal and test the settings. The commands:
$CFDEM_PROJECT_DIR
$CFDEM_SRC_DIR
$CFDEM_LIGGGHTS_SRC_DIR :pre
should give "...: is a directory" otherwise something went wrong and the environment variables in ~/bashrc are not set correctly.
To specify the paths of pizza, please check the settings in $CFDEM_SRC_DIR/etc/bashrc.
If $CFDEM_SRC_DIR is set correctly, you can type
cfdemSysTest :pre
to get some information if the paths are set correctly.
[compile LIGGGHTS and CFDEMcoupling:]
If above settings were done correctly, you can compile LIGGGHTS by typing:
cfdemCompLIG :pre
and you can then compile CFDEMcoupling by typing:
cfdemCompCFDEM :pre

44
doc/liggghtsCommandModel.html Normal file
View File

@ -0,0 +1,44 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>liggghtsCommandModel command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in liggghtsCommmands dictionary.
</P>
<PRE>liggghtsCommandModels
(
model_x
model_y
);
</PRE>
<UL><LI>model = name of the liggghtsCommandModel to be applied
</UL>
<P><B>Examples:</B>
</P>
<PRE>liggghtsCommandModels
(
runLiggghts
writeLiggghts
);
</PRE>
<P>Note: This examples list might not be complete - please look for other models (liggghtsCommandModel_XY) in this documentation.
</P>
<P><B>Description:</B>
</P>
<P>The liggghtsCommandModel is the base class to execute DEM commands within a CFD run.
</P>
<P><B>Restrictions:</B>
</P>
<P>Works only with MPI coupling.
</P>
<P><B>Default:</B> none.
</P>
</HTML>

40
doc/liggghtsCommandModel.txt Normal file
View File

@ -0,0 +1,40 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
liggghtsCommandModel command :h3
[Syntax:]
Defined in liggghtsCommmands dictionary.
liggghtsCommandModels
(
model_x
model_y
); :pre
model = name of the liggghtsCommandModel to be applied :ul
[Examples:]
liggghtsCommandModels
(
runLiggghts
writeLiggghts
); :pre
Note: This examples list might not be complete - please look for other models (liggghtsCommandModel_XY) in this documentation.
[Description:]
The liggghtsCommandModel is the base class to execute DEM commands within a CFD run.
[Restrictions:]
Works only with MPI coupling.
[Default:] none.

94
doc/liggghtsCommandModel_execute.html Normal file
View File

@ -0,0 +1,94 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>liggghtsCommandModel_execute command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in liggghtsCommmands dictionary.
</P>
<PRE>liggghtsCommandModels
(
execute
);
executeProps0
{
command
(
run
$couplingInterval
);
runFirst switch1;
runLast switch2;
runEveryCouplingStep switch3;
runEveryWriteStep switch4;
}
</PRE>
<UL><LI><I>command</I> = LIGGGHTS command to be executed. Each word in a new line, numbers and symbols need special treatment (e.g. $couplingInterval will be replaced by correct coupling interval in the simulation)
<LI><I>switch1</I> = switch (choose on/off) if the command is executed only at first time step
<LI><I>switch2</I> = switch (choose on/off) if the command is executed only at last time step
<LI><I>switch3</I> = switch (choose on/off) if the command is executed at every coupling step
<LI><I>switch4</I> = switch (choose on/off) if the command is executed at every writing step
</UL>
<P><B>Examples:</B>
</P>
<PRE>liggghtsCommandModels
(
execute
execute
);
executeProps0
{
command
(
run
$couplingInterval
);
runFirst off;
runLast off;
runEveryCouplingStep on;
}
executeProps1
{
command
(
write_restart
noBlanks
dotdot
slash
DEM
slash
liggghts.restart_
timeStamp
);
runFirst off;
runLast off;
runEveryCouplingStep off;
runEveryWriteStep on;
}
</PRE>
<P><B>Description:</B>
</P>
<P>The execute liggghtsCommand Model can be used to execute a LIGGGHTS command during a CFD run. In above example execute_0 for instance executes "run $couplingInterval" every coupling step. $couplingInterval is automatically replaced by the correct number of DEM steps. Additionally execute_1 executes "write_restart ../DEM/liggghts.restart_$timeStamp" every writing step, where $timeStamp is automatically set.
</P>
<H4>These rather complex execute commands can be replaced by the "readLiggghts" and "writeLiggghts" commands!
</H4>
<P><B>Restrictions:</B> None.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "liggghtsCommandModel.html">liggghtsCommandModel</A>
</P>
</HTML>

86
doc/liggghtsCommandModel_execute.txt Normal file
View File

@ -0,0 +1,86 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
liggghtsCommandModel_execute command :h3
[Syntax:]
Defined in liggghtsCommmands dictionary.
liggghtsCommandModels
(
execute
);
executeProps0
\{
command
(
run
$couplingInterval
);
runFirst switch1;
runLast switch2;
runEveryCouplingStep switch3;
runEveryWriteStep switch4;
\} :pre
{command} = LIGGGHTS command to be executed. Each word in a new line, numbers and symbols need special treatment (e.g. $couplingInterval will be replaced by correct coupling interval in the simulation) :ulb,l
{switch1} = switch (choose on/off) if the command is executed only at first time step :l
{switch2} = switch (choose on/off) if the command is executed only at last time step :l
{switch3} = switch (choose on/off) if the command is executed at every coupling step :l
{switch4} = switch (choose on/off) if the command is executed at every writing step :l
:ule
[Examples:]
liggghtsCommandModels
(
execute
execute
);
executeProps0
\{
command
(
run
$couplingInterval
);
runFirst off;
runLast off;
runEveryCouplingStep on;
\}
executeProps1
\{
command
(
write_restart
noBlanks
dotdot
slash
DEM
slash
liggghts.restart_
timeStamp
);
runFirst off;
runLast off;
runEveryCouplingStep off;
runEveryWriteStep on;
\} :pre
[Description:]
The execute liggghtsCommand Model can be used to execute a LIGGGHTS command during a CFD run. In above example execute_0 for instance executes "run $couplingInterval" every coupling step. $couplingInterval is automatically replaced by the correct number of DEM steps. Additionally execute_1 executes "write_restart ../DEM/liggghts.restart_$timeStamp" every writing step, where $timeStamp is automatically set.
These rather complex execute commands can be replaced by the "readLiggghts" and "writeLiggghts" commands! :h4
[Restrictions:] None.
[Related commands:]
"liggghtsCommandModel"_liggghtsCommandModel.html

49
doc/liggghtsCommandModel_readLiggghtsData.html Normal file
View File

@ -0,0 +1,49 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>liggghtsCommandModel_readLiggghtsData command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in liggghtsCommmands dictionary.
</P>
<PRE>liggghtsCommandModels
(
readLiggghtsData
);
readLiggghtsDataProps0
{
???
}
</PRE>
<P><B>Examples:</B>
</P>
<PRE>liggghtsCommandModels
(
readLiggghtsData
readLiggghtsData
);
readLiggghtsDataProps0
{
???
}
</PRE>
<P><B>Description:</B>
</P>
<P>The readLiggghtsData liggghtsCommand Model can be used to ???
</P>
<P><B>Restrictions:</B>
</P>
<P>Note: Model is not up to date.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "liggghtsCommandModel.html">liggghtsCommandModel</A>
</P>
</HTML>

48
doc/liggghtsCommandModel_readLiggghtsData.txt Normal file
View File

@ -0,0 +1,48 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
liggghtsCommandModel_readLiggghtsData command :h3
[Syntax:]
Defined in liggghtsCommmands dictionary.
liggghtsCommandModels
(
readLiggghtsData
);
readLiggghtsDataProps0
\{
???
\} :pre
[Examples:]
liggghtsCommandModels
(
readLiggghtsData
readLiggghtsData
);
readLiggghtsDataProps0
\{
???
\} :pre
[Description:]
The readLiggghtsData liggghtsCommand Model can be used to ???
[Restrictions:]
Note: Model is not up to date.
[Related commands:]
"liggghtsCommandModel"_liggghtsCommandModel.html

38
doc/liggghtsCommandModel_runLiggghts.html Normal file
View File

@ -0,0 +1,38 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>liggghtsCommandModel_runLiggghts command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in liggghtsCommmands dictionary.
</P>
<PRE>liggghtsCommandModels
(
runLiggghts
);
</PRE>
<P><B>Examples:</B>
</P>
<PRE>liggghtsCommandModels
(
runLiggghts
);
</PRE>
<P><B>Description:</B>
</P>
<P>The liggghtsCommand models can be used to execute a LIGGGHTS command during a CFD run. The "runLiggghts" command executes the command "run $nrDEMsteps", where $nrDEMsteps is automaically set according to the coupling intervals, every coupling step.
</P>
<P><B>Restrictions:</B> None.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "liggghtsCommandModel.html">liggghtsCommandModel</A>
</P>
</HTML>

35
doc/liggghtsCommandModel_runLiggghts.txt Normal file
View File

@ -0,0 +1,35 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
liggghtsCommandModel_runLiggghts command :h3
[Syntax:]
Defined in liggghtsCommmands dictionary.
liggghtsCommandModels
(
runLiggghts
); :pre
[Examples:]
liggghtsCommandModels
(
runLiggghts
); :pre
[Description:]
The liggghtsCommand models can be used to execute a LIGGGHTS command during a CFD run. The "runLiggghts" command executes the command "run $nrDEMsteps", where $nrDEMsteps is automaically set according to the coupling intervals, every coupling step.
[Restrictions:] None.
[Related commands:]
"liggghtsCommandModel"_liggghtsCommandModel.html

55
doc/liggghtsCommandModel_writeLiggghts.html Normal file
View File

@ -0,0 +1,55 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>liggghtsCommandModel_writeLiggghts command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in liggghtsCommmands dictionary.
</P>
<PRE>liggghtsCommandModels
(
writeLiggghts
);
writeLiggghtsProps
{
writeName "name";
overwrite switch;
}
</PRE>
<UL><LI><I>name</I> = name of the restart file to be written in /$caseDir/DEM/
<LI><I>switch</I> = switch (choose on/off) to select if only one restart file $name or many files $name_$timeStamp are written
</UL>
<P><B>Examples:</B>
</P>
<PRE>liggghtsCommandModels
(
runLiggghts
writeLiggghts
);
writeLiggghtsProps
{
writeName "liggghts_restart";
overwrite off;
}
</PRE>
<P><B>Description:</B>
</P>
<P>The liggghtsCommand models can be used to execute a LIGGGHTS command during a CFD write. The "writeLiggghts" command executes the command "write_restart $name", where $name is the name of the restart file, every write step.
</P>
<P><B>Restrictions:</B> None.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "liggghtsCommandModel.html">liggghtsCommandModel</A>
</P>
</HTML>

50
doc/liggghtsCommandModel_writeLiggghts.txt Normal file
View File

@ -0,0 +1,50 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
liggghtsCommandModel_writeLiggghts command :h3
[Syntax:]
Defined in liggghtsCommmands dictionary.
liggghtsCommandModels
(
writeLiggghts
);
writeLiggghtsProps
\{
writeName "name";
overwrite switch;
\} :pre
{name} = name of the restart file to be written in /$caseDir/DEM/ :ulb,l
{switch} = switch (choose on/off) to select if only one restart file $name or many files $name_$timeStamp are written :l
:ule
[Examples:]
liggghtsCommandModels
(
runLiggghts
writeLiggghts
);
writeLiggghtsProps
\{
writeName "liggghts_restart";
overwrite off;
\} :pre
[Description:]
The liggghtsCommand models can be used to execute a LIGGGHTS command during a CFD write. The "writeLiggghts" command executes the command "write_restart $name", where $name is the name of the restart file, every write step.
[Restrictions:] None.
[Related commands:]
"liggghtsCommandModel"_liggghtsCommandModel.html

34
doc/locateModel.html Normal file
View File

@ -0,0 +1,34 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>locateModel command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>locateModel model;
</PRE>
<UL><LI>model = name of the locateModel to be applied
</UL>
<P><B>Examples:</B>
</P>
<PRE>locateModel engine;
</PRE>
<P>Note: This examples list might not be complete - please look for other models (locateModel_XY) in this documentation.
</P>
<P><B>Description:</B>
</P>
<P>The locateModel is the base class for models which search for the CFD cell and cellID corresponding to a position. In general it is used to find the cell a particle is located in.
</P>
<P><B>Restrictions:</B> none.
</P>
<P><B>Default:</B> none.
</P>
</HTML>

30
doc/locateModel.txt Normal file
View File

@ -0,0 +1,30 @@
"CFDEMproject WWW Site"_lws - "CFDEM Commands"_lc :c
:link(lws,http://www.cfdem.com)
:link(lc,CFDEMcoupling_Manual.html#comm)
:line
locateModel command :h3
[Syntax:]
Defined in couplingProperties dictionary.
locateModel model; :pre
model = name of the locateModel to be applied :ul
[Examples:]
locateModel engine; :pre
Note: This examples list might not be complete - please look for other models (locateModel_XY) in this documentation.
[Description:]
The locateModel is the base class for models which search for the CFD cell and cellID corresponding to a position. In general it is used to find the cell a particle is located in.
[Restrictions:] none.
[Default:] none.

55
doc/locateModel_engineSearch.html Normal file
View File

@ -0,0 +1,55 @@
<HTML>
<CENTER><A HREF = "http://www.cfdem.com">CFDEMproject WWW Site</A> - <A HREF = "CFDEMcoupling_Manual.html#comm">CFDEM Commands</A>
</CENTER>
<HR>
<H3>locateModel_engineSearch command
</H3>
<P><B>Syntax:</B>
</P>
<P>Defined in couplingProperties dictionary.
</P>
<PRE>locateModel engine;
engineProps
{
faceDecomp switch1;
treeSearch switch2;
}
</PRE>
<UL><LI><I>switch1</I> = time to start the averaging (default 0)
<LI><I>switch2</I> = names of the finite volume scalar fields to be temporally averaged
</UL>
<P><B>Examples:</B>
</P>
<PRE>locateModel engine;
engineProps
{
faceDecomp false;
treeSearch false;
}
</PRE>
<P><B>Description:</B>
</P>
<P>The locateModel "engine" locates the CFD cell and cellID corresponding to a given position.
The engineSearch locate Model can be used with different settings to use different algorithms:
</P>
<UL><LI>faceDecomp false; treeSearch false; will execute some geometric (linear) search using the last known cellID (recommended)
<LI>faceDecomp false; treeSearch true; will use a recursive tree structure to find the cell.
</UL>
<P><B>Restrictions:</B> none.
</P>
<P><B>Related commands:</B>
</P>
<P><A HREF = "locateModel.html">locateModel</A>
</P>
</HTML>

Some files were not shown because too many files have changed in this diff Show More