-
-The CFDEMcoupling documentation is organized into the following sections. If you find any errors or omissions in this manual or have suggestions for useful information to add, please send an email to the developers so the CFDEMcoupling documentation can be improved. -
-1.1 About CFDEMcouplingCFDEM coupling provides an open source parallel coupled CFD-DEM framework combining the strengths of LIGGGHTS DEM code and the Open Source CFD package OpenFOAM(R)(*). The CFDEMcoupling toolbox allows to expand standard CFD solvers of OpenFOAM(R)(*) to include a coupling to the DEM code LIGGGHTS. 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: -
-The file structure: -
-Details on installation are given on the CFDEMproject WWW Site . -The functionality of this CFD-DEM framework is described via tutorial cases 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 -
-This documentation was written by Christoph Goniva, DCS Computing GmbH, 2012 -
-(*) This offering is not approved or endorsed by OpenCFD Limited, the producer of the OpenFOAM software and owner of the OPENFOAM® and OpenCFD® trade marks. OPENFOAM® is a registered trade mark of OpenCFD Limited, a wholly owned subsidiary of the ESI Group. -
-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). -
-General: -
-Each solver of the CFDEMcoupling comes with at least one tutorial example, showing its functionality and correct usage. 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 input file located in $caseDir/DEM (e.g. in.liggghts_init). For details on the LIGGGHTS setup, please have a look at the LIGGGHTS 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)(*) documentations (www.openFoam.com)(*). -
-Settings of the coupling routines are defined in $caseDir/CFD/constant/couplingProperies (e.g. force models, data exchange model, etc.) and $caseDir/CFD/constant/liggghtsCommands (allows to execute a LIGGGHTS command during a coupled simulation). -
-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: -
-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. -
-modelType --
"modelType" refers to the formulation of the equations to be solved. Choose "A", "B" or "Bfull", according to Zhou et al. (2010): "Discrete particle simulation of particle-fluid flow: model formulations and their applicability", JFM. "A" requires the use of the force models gradPForce and viscForce, whereas "B" requires the force model "Archimedes". "Bfull" refers to model type I. -
-couplingInterval --
The coupling interval determines the time passing between two CFD-DEM data exchanges. -
-A useful procedure would be: -1) Set the DEM timestep in the in.xxx file according to the needs of the pure DEM problem. -2) Set the "couplingInterval", which refers to the DEM timesteps. Depending on the problem you will need to have a close (small couplingInterval) or loose coupling. -3) Choose the CFD timestep in the controlDict. It must be equal to or smaller than the coupling time, otherwise you will get the error: "Error - TS bigger than coupling interval!". -
-Example: DEMts=0.00001s, couplingInterval=10 exchange data (=couple) will happen every 0.0001s. -
-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. -
-This section lists all CFDEMcoupling sub-models and solvers alphabetically, with a separate -listing below of styles within certain commands. -
-Syntax: -
-Defined in couplingProperties dictionary. -
-IOModel "model"; --
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. -
- diff --git a/doc/IOModel_basicIO.html b/doc/IOModel_basicIO.html deleted file mode 100644 index 8152c9e9..00000000 --- a/doc/IOModel_basicIO.html +++ /dev/null @@ -1,32 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-IOModel "basicIO"; --
Examples: -
-IOModel "basicIO"; --
Description: -
-The basic IO-model writes particle positions velocities and radii to files. The default output directory ($casePath/CFD/proc*/time/lagrangian). Using the keyword "serialOutput;" in couplingProperties the IO is serial to the directory ($casePath/CFD/lagrangian). In the latter case only the data on processor 0 is written! Data is written every write time of the CFD simulation. -
-Restrictions: None. -
-Related commands: -
-IOModel -
- diff --git a/doc/IOModel_noIO.html b/doc/IOModel_noIO.html deleted file mode 100644 index 0fb2343c..00000000 --- a/doc/IOModel_noIO.html +++ /dev/null @@ -1,32 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-IOModel "off"; --
Examples: -
-IOModel "off"; --
Description: -
-The noIO-model is a dummy IO model. -
-Restrictions: None. -
-Related commands: -
-IOModel -
- diff --git a/doc/IOModel_sophIO.html b/doc/IOModel_sophIO.html deleted file mode 100644 index 2bbf56ce..00000000 --- a/doc/IOModel_sophIO.html +++ /dev/null @@ -1,32 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-IOModel "sophIO"; --
Examples: -
-IOModel "sophIO"; --
Description: -
-The sophIO-model is based on basicIO model and additionally writes voidfraction, implicit forces, explicit forces. Data is written every write time of the CFD simulation. -
-Restrictions: None. -
-Related commands: -
-IOModel -
- diff --git a/doc/IOModel_trackIO.html b/doc/IOModel_trackIO.html deleted file mode 100644 index 28d1e861..00000000 --- a/doc/IOModel_trackIO.html +++ /dev/null @@ -1,32 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-IOModel "trackIO"; --
Examples: -
-IOModel "trackIO"; --
Description: -
-The trackIO-model is based on sophIO model and additionally writes fields necessary to use the particleTracks utility (which needs a particleTrackProperties file in the constant dir). The particleTracks utility generates tracks of the particles and writes them to a vtk file. -
-Restrictions: None. -
-Related commands: -
-IOModel -
- diff --git a/doc/SCcontent/individual_commands.txt b/doc/SCcontent/individual_commands.txt deleted file mode 100644 index f9512e78..00000000 --- a/doc/SCcontent/individual_commands.txt +++ /dev/null @@ -1,4 +0,0 @@ -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. diff --git a/doc/averagingModel.html b/doc/averagingModel.html deleted file mode 100644 index 5237b6d4..00000000 --- a/doc/averagingModel.html +++ /dev/null @@ -1,41 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-averagingModel model; --
Examples: -
-averagingModel dense; -averagingModel dilute; --
Note: This examples list might not be complete - please look for other averaging 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: -
- -Default: none -
- diff --git a/doc/averagingModel_dense.html b/doc/averagingModel_dense.html deleted file mode 100644 index 239c82d9..00000000 --- a/doc/averagingModel_dense.html +++ /dev/null @@ -1,34 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-averagingModel dense; --
Examples: -
-averagingModel dense; --
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 "dense" model is supposed to be applied to cases where the granular regime is rather dense. -
-Restrictions: -
-No known restrictions. -
-Related commands: -
- - diff --git a/doc/averagingModel_dilute.html b/doc/averagingModel_dilute.html deleted file mode 100644 index 6f75339c..00000000 --- a/doc/averagingModel_dilute.html +++ /dev/null @@ -1,35 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-averagingModel dilute; --
Examples: -
-averagingModel dilute; --
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: -
- - diff --git a/doc/cfdemSolverIB.html b/doc/cfdemSolverIB.html deleted file mode 100644 index 556d2441..00000000 --- a/doc/cfdemSolverIB.html +++ /dev/null @@ -1,53 +0,0 @@ - -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. Using 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. -
-Code of this solver contributions by Alice Hager, JKU. -
-Algorithm: -
-For each time step ... -
-Use: -
-The solver is realized within the Open Source framework CFDEMcoupling. Just as for the unresolved CFD-DEM solver cfdemSolverPiso the file CFD/constant/couplingProperties contains information about the settings for the different models. While IOmodel, DataExchangeModel etc. are applicable for all CFDEMcoupling-solvers, special locate-, force- and void fraction models were designed for the present case: -
-engineSearchIB, ArchimedesIB, ShirgaonkarIB, IBVoidfraction -
-References: -
-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 -
-(*) OpenFOAM(R) 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. -
-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 the 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. -
-(*) This offering is not approved or endorsed by OpenCFD Limited, the producer of the OpenFOAM software and owner of the OPENFOAM® and OpenCFD® trade marks. OPENFOAM® is a registered trade mark of OpenCFD Limited, a wholly owned subsidiary of the ESI Group. -
-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. -
-The heat transfer equation is implemented according to Nield & Bejan (2013), Convection in Porous Media, DOI 10.1007/978-1-4614-5541-7_2, Springer -
-(*) This offering is not approved or endorsed by OpenCFD Limited, the producer of the OpenFOAM software and owner of the OPENFOAM® and OpenCFD® trade marks. OPENFOAM® is a registered trade mark of OpenCFD Limited, a wholly owned subsidiary of the ESI Group. -
-Syntax: -
-Defined in couplingProperties dictionary. -
-chemistryModels -( - model_x - model_y -); --
Examples: -
-chemistryModels -( - species - diffusionCoefficients - massTransferCoeff -); --
Note: This examples list might not be complete - please look for other models (forceModel_XY) in this documentation. -
-Description: -
-The chemistry model initialized the fields performs calculation of molar fractions and diffusion coefficients of the gaseous reactants at the location of each DEM particle. All models are executed sequentially. These values are used in the DEM calculation of particle reduction models. -
-Restrictions: -
-None. -
-Related commands: -
-species, diffusionCoefficient, massTransferCoeff -
-Note: This examples list may be incomplete - please look for other models (forceModel_XY) in this documentation. -
-Default: none. -
- diff --git a/doc/chemistryModel_diffusionCoefficients.html b/doc/chemistryModel_diffusionCoefficients.html deleted file mode 100644 index 94c463dd..00000000 --- a/doc/chemistryModel_diffusionCoefficients.html +++ /dev/null @@ -1,62 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-chemistryModels
-(
- diffusionCoefficients
-);
-diffusionCoefficientsProps
-{
- verbose switch1;
- ChemistryFile "$casePath/CFD/constant/foam.inp";
- diffusantGasNames ( speciesNames );
-};
-
-Examples: -
-chemistryModels
-(
- diffusionCoefficients
-);
-speciesProps
-{
- verbose false;
- ChemistryFile "$casePath/CFD/constant/foam.inp";
- diffusantGasNames ( CO
- H2
- );
-}
-
-Description: -
-The chemistry model performs the calculation of chemical reactional effects acting on each DEM particle. The diffusionCoefficients model activates the binary molecular diffusion calculation of the reacting species using the Fuller-Schettler-Giddings correlation. -
-Restrictions: -
-Species model needs to be active. -
-Related commands: -
- - diff --git a/doc/chemistryModel_massTransferCoeff.html b/doc/chemistryModel_massTransferCoeff.html deleted file mode 100644 index a80c8d4a..00000000 --- a/doc/chemistryModel_massTransferCoeff.html +++ /dev/null @@ -1,52 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-chemistryModels
-(
- massTransferCoeff
-);
-diffusionCoefficientsProps
-{
- verbose switch1;
-};
-
-Examples: -
-chemistryModels
-(
- massTransferCoeff
-);
-massTransferCoeffProps
-{
- verbose false;
-}
-
-Description: -
-The chemistry model performs the calculation of chemical reactional effects acting on each DEM particle. The coeffs needed to calculate the mass transfer coefficients are transferred to the DEM side, where it is used in the fix_chem_shrink_core module. -
-Restrictions: -
-Species model needs to be active. -
-Related commands: -
- - diff --git a/doc/chemistryModel_species.html b/doc/chemistryModel_species.html deleted file mode 100644 index 7a4da001..00000000 --- a/doc/chemistryModel_species.html +++ /dev/null @@ -1,74 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-chemistryModels
-(
- species
-);
-speciesProps
-{
- ChemistryFile "$casePath/CFD/constant/foam.inp";
- verbose switch1;
- tempFieldName "T";
- densityFieldName "rho"
- voidfractionFieldName "voidfraction"
- totalMoleFieldName "molarConc"
- partTempName "partTemp"
- partRhoName "partRho"
-};
-
-Examples: -
-chemistryModels
-(
- species
-);
-speciesProps
-{
- ChemistryFile "$casePath/CFD/constant/foam.inp";
- verbose false;
-}
-
-Description: -
-The chemistry model performs the calculation of chemical reactional effects acting on each DEM particle. The species model is the model, where the specified species fields (from the foam.inp folder) are intialized, and information such as temperature, density, molar concentration and more importantly the molar fractions are transferred to DEM side. -
-Restrictions: -
-none. -
-Related commands: -
- - diff --git a/doc/clockModel.html b/doc/clockModel.html deleted file mode 100644 index 7b590f81..00000000 --- a/doc/clockModel.html +++ /dev/null @@ -1,36 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-clockModel model; --
Examples: -
-clockModel standardClock; --
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. -
-Main parts of the clockModel classes are written by Josef Kerbl, JKU. -
-Restrictions: none. -
-Default: none. -
- diff --git a/doc/clockModel_noClock.html b/doc/clockModel_noClock.html deleted file mode 100644 index 23448e45..00000000 --- a/doc/clockModel_noClock.html +++ /dev/null @@ -1,32 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-clockModel off; --
Examples: -
-clockModel off; --
Description: -
-The "noClock" model is a dummy clockModel model which does not measure/evaluate the run time. -
-Restrictions: none. -
-Related commands: -
- - diff --git a/doc/clockModel_standardClock.html b/doc/clockModel_standardClock.html deleted file mode 100644 index b757df1f..00000000 --- a/doc/clockModel_standardClock.html +++ /dev/null @@ -1,34 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-clockModel standardClock; --
Examples: -
-clockModel standardClock; --
Description: -
-The "standardClock" model is a basic clockModel model which measures the run time between every ".start(int arrayPos,string name)" and ".stop(string name)" 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 . -Since the measurements are stored in an array, it is necessary to put a variable arrayPos (type integer) at the start command. Those do not need to be in ascending order and positions may be omitted. The standard size of this array is 30 and can be changed at the initialization of the standardClock class. If arrayPos is out of bounds, the array size will be doubled. The stop command does not need arrayPos, since the class remembers the positions. The string name is intended for easier evaluation afterwards an may be omitted like ".start(int arrayPos)" and ".stop()". The command ".stop(string name)" is a safety feature, because if the name is not equal to the started name, output will be produced for information. -After the case ran you may use the matPlot.py script located in $CFDEM_UT_DIR/vizClock/ to produce a graphical output of your measurements. The usage is like 'python < matPlot.py' and you have to be in the directory of the desired time step, where there is a file called "timeEvalFull.txt", which contains averaged and maximum data with respect to the number of processes. There is an alias called "vizClock" to run this python routine for visualizing the data. -
-Restrictions: none. -
-Related commands: -
- - diff --git a/doc/dataExchangeModel.html b/doc/dataExchangeModel.html deleted file mode 100644 index 51d81bbd..00000000 --- a/doc/dataExchangeModel.html +++ /dev/null @@ -1,41 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-dataExchangeModel model; --
Examples: -
-dataExchangeModel twoWayFiles; -dataExchangeModel twoWayMPI; --
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, oneWayVTK, twoWayFiles, twoWayMPI -
-Default: none -
- diff --git a/doc/dataExchangeModel_noDataExchange.html b/doc/dataExchangeModel_noDataExchange.html deleted file mode 100644 index f84f4a55..00000000 --- a/doc/dataExchangeModel_noDataExchange.html +++ /dev/null @@ -1,34 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-dataExchangeModel noDataExchange; --
Examples: -
-dataExchangeModel noDataExchange; --
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: -
- - diff --git a/doc/dataExchangeModel_oneWayVTK.html b/doc/dataExchangeModel_oneWayVTK.html deleted file mode 100644 index def26192..00000000 --- a/doc/dataExchangeModel_oneWayVTK.html +++ /dev/null @@ -1,58 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-dataExchangeModel oneWayVTK;
-oneWayVTKProps
-{
- DEMts timeStep;
- relativePath "path";
- couplingFilename "filename";
- maxNumberOfParticles number;
-};
-
-Examples: -
-dataExchangeModel oneWayVTK;
-oneWayVTKProps
-{
- DEMts 0.0001;
- relativePath "../DEM/post";
- couplingFilename "vtk_out%4.4d.vtk";
- maxNumberOfParticles 30000;
-}
-
-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: -
- - diff --git a/doc/dataExchangeModel_twoWayFiles.html b/doc/dataExchangeModel_twoWayFiles.html deleted file mode 100644 index 46d2d891..00000000 --- a/doc/dataExchangeModel_twoWayFiles.html +++ /dev/null @@ -1,50 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-dataExchangeModel twoWayFiles;
-twoWayFilesProps
-{
- couplingFilename "filename";
- maxNumberOfParticles number;
-};
-
-Examples: -
-dataExchangeModel twoWayFiles;
-twoWayFilesProps
-{
- couplingFilename "vtk_out%4.4d.vtk";
- maxNumberOfParticles 30000;
-}
-
-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 one for CFD run. -
-Related commands: -
- - diff --git a/doc/dataExchangeModel_twoWayMPI.html b/doc/dataExchangeModel_twoWayMPI.html deleted file mode 100644 index cde5fabe..00000000 --- a/doc/dataExchangeModel_twoWayMPI.html +++ /dev/null @@ -1,46 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-dataExchangeModel twoWayMPI;
-twoWayMPIProps
-{
- liggghtsPath "path";
-};
-
-Examples: -
-dataExchangeModel twoWayMPI;
-twoWayMPIProps
-{
- liggghtsPath "../DEM/in.liggghts_init";
-}
-
-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: -
- - diff --git a/doc/dataExchangeModel_twoWayMany2Many.html b/doc/dataExchangeModel_twoWayMany2Many.html deleted file mode 100644 index db5b6592..00000000 --- a/doc/dataExchangeModel_twoWayMany2Many.html +++ /dev/null @@ -1,46 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-dataExchangeModel twoWayMany2Many;
-twoWayMany2ManyProps
-{
- liggghtsPath "path";
-};
-
-Examples: -
-dataExchangeModel twoWayMany2Many;
-twoWayMany2ManyProps
-{
- liggghtsPath "../DEM/in.liggghts_init";
-}
-
-Description: -
-The data exchange model performs the data exchange between the DEM code and the CFD code. The twoWayMany2Many model is a model that can exchange particle properties from DEM to CFD and from CFD to DEM. Data is exchanged via MPI technique using the many to many mapping scheme. The DEM run is executed by the coupling model, via a liggghtsCommandModel object. -
-Restrictions: -
-Must be used in combination with the engineSearchMany2Many locate model! -
-Related commands: -
- - diff --git a/doc/forceModel.html b/doc/forceModel.html deleted file mode 100644 index fa2d2f78..00000000 --- a/doc/forceModel.html +++ /dev/null @@ -1,50 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-forceModels -( - model_x - model_y -); --
Examples: -
-forceModels -( - Archimedes - DiFeliceDrag -); --
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. If the fluid density field is needed, by default a field named "rho" will be used. Via the forceSubModel an alternative field can be chosen. -
-Restrictions: -
-None. -
-Related commands: -
-Archimedes, DiFeliceDrag, gradPForce, viscForce">dSauter -
-Note: This examples list may be incomplete - please look for other models (forceModel_XY) in this documentation. -
-Default: none. -
- diff --git a/doc/forceModel_Archimedes.html b/doc/forceModel_Archimedes.html deleted file mode 100644 index 8301478d..00000000 --- a/doc/forceModel_Archimedes.html +++ /dev/null @@ -1,52 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-forceModels
-(
- Archimedes
-);
-ArchimedesProps
-{
- gravityFieldName "gravity";
-};
-
-Examples: -
-forceModels
-(
- Archimedes
-);
-ArchimedesProps
-{
- gravityFieldName "g";
-}
-
-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: -
- - diff --git a/doc/forceModel_ArchimedesIB.html b/doc/forceModel_ArchimedesIB.html deleted file mode 100644 index 9f43172f..00000000 --- a/doc/forceModel_ArchimedesIB.html +++ /dev/null @@ -1,56 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-forceModels
-(
- ArchimedesIB
-);
-ArchimedesIBProps
-{
- gravityFieldName "gravity";
- voidfractionFieldName "voidfraction";
-};
-
-Examples: -
-forceModels
-(
- ArchimedesIB
-);
-ArchimedesIBProps
-{
- gravityFieldName "g";
- voidfractionFieldName "voidfractionNext";
-}
-
-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 boundary method. -
-Restrictions: -
-Only for immersed boundary solvers. -
-Related commands: -
- - diff --git a/doc/forceModel_DiFeliceDrag.html b/doc/forceModel_DiFeliceDrag.html deleted file mode 100644 index 53a2aebf..00000000 --- a/doc/forceModel_DiFeliceDrag.html +++ /dev/null @@ -1,56 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-forceModels
-(
- DiFeliceDrag
-);
-DiFeliceDragProps
-{
- velFieldName "U";
- interpolation switch1;
-};
-
-Examples: -
-forceModels
-(
- DiFeliceDrag
-);
-DiFeliceDragProps
-{
- velFieldName "U";
- interpolation true;
-}
-
-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: -
- - diff --git a/doc/forceModel_GidaspowDrag.html b/doc/forceModel_GidaspowDrag.html deleted file mode 100644 index 9aa7318d..00000000 --- a/doc/forceModel_GidaspowDrag.html +++ /dev/null @@ -1,68 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-forceModels
-(
- GidaspowDrag
-);
-GidaspowDragProps
-{
- velFieldName "U";
- voidfractionFieldName "voidfraction";
- granVelFieldName "Us";
- phi "scalar";
- interpolation switch1;
- implForceDEM switch2;
-};
-
-Examples: -
-forceModels
-(
- GidaspowDrag
-);
-GidaspowDragProps
-{
- velFieldName "U";
- voidfractionFieldName "voidfraction";
- granVelFieldName "Us";
-}
-
-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 Ergun (1952) and Wen & Yu (1966) (see Zhu et al. (2007): "Discrete particle simulation of particulate systems: Theoretical developments", ChemEngScience). -
-Restrictions: -
-none. -
-Related commands: -
- - diff --git a/doc/forceModel_KochHillDrag.html b/doc/forceModel_KochHillDrag.html deleted file mode 100644 index 1cf16d96..00000000 --- a/doc/forceModel_KochHillDrag.html +++ /dev/null @@ -1,61 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-forceModels
-(
- KochHillDrag
-);
-KochHillDragProps
-{
- velFieldName "U";
- voidfractionFieldName "voidfraction";
- interpolation "bool1";
- implForceDEM "bool2";
-};
-
-Examples: -
-forceModels
-(
- KochHillDrag
-);
-KochHillDragProps
-{
- velFieldName "U";
- voidfractionFieldName "voidfraction";
-}
-
-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: -
- - diff --git a/doc/forceModel_LaEuScalarTemp.html b/doc/forceModel_LaEuScalarTemp.html deleted file mode 100644 index 778d3e32..00000000 --- a/doc/forceModel_LaEuScalarTemp.html +++ /dev/null @@ -1,82 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-forceModels
-(
- LaEuScalarTemp
-);
-LaEuScalarTempProps
-{
- velFieldName "U";
- tempFieldName "T";
- voidfractionFieldName "voidfraction";
- partTempName "Temp";
- partHeatFluxName "convectiveHeatFlux";
- lambda value;
- Cp value1;
- interpolation "switch1";
- verbose "switch2";
-};
-
-Examples: -
-forceModels
-(
- LaEuScalarTemp
-);
-LaEuScalarTempProps
-{
- velFieldName "U";
- tempFieldName "T";
- voidfractionFieldName "voidfraction";
- partTempName "Temp";
- partHeatFluxName "convectiveHeatFlux";
- lambda 0.0256;
- Cp 1007;
-}
-
-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. The force model has to be the second (!!!) model in the forces list. -
-Related commands: -
- - diff --git a/doc/forceModel_MeiLift.html b/doc/forceModel_MeiLift.html deleted file mode 100644 index e21aa8b2..00000000 --- a/doc/forceModel_MeiLift.html +++ /dev/null @@ -1,64 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-forceModels
-(
- MeiLift
-);
-MeiLiftProps
-{
- velFieldName "U";
- useSecondOrderTerms;
- interpolation "switch1";
- verbose "switch2";
-};
-
-Examples: -
-forceModels
-(
- MeiLift
-);
-MeiLiftProps
-{
- velFieldName "U";
- useSecondOrderTerms;
- interpolation true;
- verbose true;
-}
-
-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). In case the keyword "useSecondOrderTerms" is not specified, this lift force model uses the expression of McLaughlin (1991, Journal of Fluid Mechanics 224:261-274). -
-Restrictions: -
-None. -
-Related commands: -
- - diff --git a/doc/forceModel_SchillerNaumannDrag.html b/doc/forceModel_SchillerNaumannDrag.html deleted file mode 100644 index 7ff1ecae..00000000 --- a/doc/forceModel_SchillerNaumannDrag.html +++ /dev/null @@ -1,52 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-forceModels
-(
- SchillerNaumannDrag
-);
-SchillerNaumannDragProps
-{
- velFieldName "U";
-};
-
-Examples: -
-forceModels
-(
- SchillerNaumannDrag
-);
-SchillerNaumannDragProps
-{
- velFieldName "U";
-}
-
-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: -
- - diff --git a/doc/forceModel_ShirgaonkarIB.html b/doc/forceModel_ShirgaonkarIB.html deleted file mode 100644 index 27e0ddc4..00000000 --- a/doc/forceModel_ShirgaonkarIB.html +++ /dev/null @@ -1,60 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-forceModels
-(
- ShirgaonkarIB
-);
-ShirgaonkarIBProps
-{
- velFieldName "U";
- pressureFieldName "pressure";
-};
-
-Examples: -
-forceModels
-(
- ShirgaonkarIB
-);
-ShirgaonkarIBProps
-{
- velFieldName "U";
- pressureFieldName "p";
-}
-
-Description: -
-The force model performs the calculation of forces (e.g. fluid-particle interaction forces) acting on each DEM particle. The ShirgaonkarIB 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 boundary method. -
-References: -
-SHIRGAONKAR, A.A., MACIVER, M.A. and PATANKAR, N.A., (2009), “A new mathematical formulation and fast algorithm for fully resolved simulation of self-propulsion”, J. Comput. Phys., 228, 2366-2390. -
-Restrictions: -
-Only for immersed boundary solvers. -
-Related commands: -
- - diff --git a/doc/forceModel_dSauter.html b/doc/forceModel_dSauter.html deleted file mode 100644 index 4f8050e3..00000000 --- a/doc/forceModel_dSauter.html +++ /dev/null @@ -1,47 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-forceModels
-(
- dSauter
-);
-dSauterProps
-{
- coarseGrainingFactors
- (
- X Y Z
- );
-};
-
-Description: -
-This "forceModel" does not influence the particles or the flow - it calculates the Sauter diameter -
-
-. -
-Restrictions: -
-none. -
-Related commands: -
- - diff --git a/doc/forceModel_fieldStore.html b/doc/forceModel_fieldStore.html deleted file mode 100644 index d21cbcb9..00000000 --- a/doc/forceModel_fieldStore.html +++ /dev/null @@ -1,68 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-forceModels
-(
- fieldStore
-);
-fieldStoreProps
-{
- scalarFieldNames
- (
- "scalarField"
- );
- vectorFieldNames
- (
- "vectorField"
- );
-};
-
-Examples: -
-forceModels
-(
- fieldStore
-);
-fieldStoreProps
-{
- scalarFieldNames
- (
- "voidfraction"
- );
- vectorFieldNames
- (
- "U"
- );
-}
-
-Description: -
-This "forceModel" does not influence the particles or the flow - it is a tool to store a scalar/vector field! This is especially useful if you use a boundary condition which cannot interpreted correctly in your postporcessor (e.g. paraview). -
-Restrictions: -
-none. -
-Related commands: -
- - diff --git a/doc/forceModel_gradPForce.html b/doc/forceModel_gradPForce.html deleted file mode 100644 index 661b4a0e..00000000 --- a/doc/forceModel_gradPForce.html +++ /dev/null @@ -1,60 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-forceModels
-(
- gradPForce;
-);
-gradPForceProps
-{
- pFieldName "pressure";
- velocityFieldName "U";
- interpolation switch1;
-};
-
-Examples: -
-forceModels
-(
- gradPForce;
-);
-gradPForceProps
-{
- pFieldName "p";
- velocityFieldName "U";
- interpolation true;
-}
-
-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: -
- - diff --git a/doc/forceModel_noDrag.html b/doc/forceModel_noDrag.html deleted file mode 100644 index 9baaa53f..00000000 --- a/doc/forceModel_noDrag.html +++ /dev/null @@ -1,45 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-forceModels -( - noDrag -); --
Examples: -
-forceModels -( - noDrag -); --
noDragProps (optional)
-{
- noDEMForce; (optional)
-};
-
-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. If the variable noDEMForce is set, then the forces communicated to the DEM solver are also set to zero. -
-Restrictions: -
-None. -
-Related commands: -
- - diff --git a/doc/forceModel_particleCellVolume.html b/doc/forceModel_particleCellVolume.html deleted file mode 100644 index c34aa71e..00000000 --- a/doc/forceModel_particleCellVolume.html +++ /dev/null @@ -1,59 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-forceModels
-(
- particleCellVolume
-);
-particleCellVolumeProps
-{
- upperThreshold value;
- lowerThreshold value2;
- verbose;
-};
-
-Examples: -
-forceModels
-(
- particleCellVolume
-);
-particleCellVolumeProps
-{
- upperThreshold 0.999;
- lowerThreshold 0;
- verbose;
-}
-
-Description: -
-This "forceModel" does not influence the particles or the simulation - it is a postprocessing tool! The total volume of the particles as they are represented on the CFD mesh is calculated. Further the total volume of the cells particles are in is calculated. -At "writeTime" a field named particleCellVolume , where scalarField is the name of the original field, is written. This can then be probed using standard function object probes. Analogously a field named cellVolume is written. Using the verbose option a screen output is given. -
-Restrictions: -
-None. -
-Related commands: -
- - diff --git a/doc/forceModel_pdCorrelation.html b/doc/forceModel_pdCorrelation.html deleted file mode 100644 index c838e5e2..00000000 --- a/doc/forceModel_pdCorrelation.html +++ /dev/null @@ -1,58 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-forceModels
-(
- pdCorrelation
-);
-pdCorrelationProps
-{
- coarseGrainingFactors
- (
- X Y Z
- );
- particleDensities
- (
- A B C
- );
- runOnWriteOnly true;
-};
-
-Description: -
-This "forceModel" does not influence the particles or the flow - it calculates the particle momentum-diameter correlation -
-
-where delta is the type-specific coarsegraining factor. -
-This model is sensitive to additionally pulled particle type info, and can either use the type-specific densities from the dict or those pulled from LIGGGHTS. -
-Restrictions: -
-none. -
-Related commands: -
- - diff --git a/doc/forceModel_virtualMassForce.html b/doc/forceModel_virtualMassForce.html deleted file mode 100644 index 8c7499fc..00000000 --- a/doc/forceModel_virtualMassForce.html +++ /dev/null @@ -1,52 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-forceModels
-(
- virtualMassForce
-);
-virtualMassForceProps
-{
- velFieldName "U";
-};
-
-Examples: -
-forceModels
-(
- virtualMassForce
-);
-virtualMassForceProps
-{
- velFieldName "U";
-}
-
-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: -
- - diff --git a/doc/forceModel_viscForce.html b/doc/forceModel_viscForce.html deleted file mode 100644 index cb233bf1..00000000 --- a/doc/forceModel_viscForce.html +++ /dev/null @@ -1,55 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-forceModels
-(
- viscForce;
-);
-viscForceProps
-{
- velocityFieldName "U";
- interpolation "switch";
-};
-
-Examples: -
-forceModels
-(
- viscForce;
-);
-viscForceProps
-{
- velocityFieldName "U";
-}
-
-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: -
- - diff --git a/doc/forceSubModel.html b/doc/forceSubModel.html deleted file mode 100644 index 090c1c98..00000000 --- a/doc/forceSubModel.html +++ /dev/null @@ -1,49 +0,0 @@ - -Syntax: -
-Defined in couplingProperties sub-dictionary of the force model in use. If no force sub-model is applied ImEx is used as default. If the keyword "forceSubModels" is provided, a choice of sub model is demanded. -
-forceSubModels -( - model_x - model_y -); --
Examples: -
-forceSubModels -( - ImEx -); --
Note: This examples list might not be complete - please look for other models (forceSubModel_XY) in this documentation. -
-Description: -
-The force sub model is designed to hold the settings a force model can have. For now it handles the treatExplicit, treatDEM and implDEM option. -
-Restrictions: -
-None. -
-Related commands: -
-ImEx -
-Note: This examples list may be incomplete - please look for other models (forceSubModel_XY) in this documentation. -
-Default: none. -
- diff --git a/doc/forceSubModel_ImEx.html b/doc/forceSubModel_ImEx.html deleted file mode 100644 index 43b92d46..00000000 --- a/doc/forceSubModel_ImEx.html +++ /dev/null @@ -1,45 +0,0 @@ - -Syntax: -
-Defined in couplingProperties sub-dictionary of the force model in use. -
-forceSubModels -( - ImEx; -); -
-treatExplicit true; // optional for some force models. -treatDEM true; // optional for some force models. -implDEM true; // optional for some force models. -
-Examples: -
-forceSubModels -( - ImEx; -); -treatExplicit true; // optional for some force models. -
-Description: -
-If no force sub-model is applied ImEx is used as default. If the keyword "forceSubModels" is provided, a choice of sub model is demanded. Depending on the force model different keywords are read and can therefrore be set (see the log file). If the keyword is provided, its value is used. -
-Restrictions: -
-none. -
-Related commands: -
- - diff --git a/doc/forceSubModel_ImExCorr.html b/doc/forceSubModel_ImExCorr.html deleted file mode 100644 index 215cb415..00000000 --- a/doc/forceSubModel_ImExCorr.html +++ /dev/null @@ -1,46 +0,0 @@ - -Syntax: -
-Defined in couplingProperties sub-dictionary of the force model in use. -
-forceSubModels -( - ImExCorr; -); -
-treatExplicit true; // optional for some force models. -treatDEM true; // optional for some force models. -implDEM true; // optional for some force models. -explicitInterpCorr true; // optional for some force models. -
-Examples: -
-forceSubModels -( - ImExCorr; -); -treatExplicit true; // optional for some force models. -
-Description: -
-Same as ImEx, but it additionally reads "explicitInterpCorr" to correct the error steming from interpolation of Ufluid and averaging of Uparticles. -
-Restrictions: -
-none. -
-Related commands: -
- - diff --git a/doc/githubAccess_public.html b/doc/githubAccess_public.html deleted file mode 100644 index b27e7093..00000000 --- a/doc/githubAccess_public.html +++ /dev/null @@ -1,186 +0,0 @@ - -Description: -
-This routine describes how to set up a github account and pull repositories of the CFDEM(R)project. -After setting some environment variables LIGGGHTS(R) and CFDEM(R)coupling can be compiled -
-Procedure: -
-Basically the following steps have to be performed: -
-git clone the desired repository: -
-If not already done, open a terminal and create a directory for LIGGGHTS(R) in $HOME: -
-cd --
mkdir LIGGGHTS --
cd LIGGGHTS --
To clone the public LIGGGHTS repository, open a terminal and execute: -
--git clone git://github.com/CFDEMproject/LIGGGHTS-PUBLIC.git LIGGGHTS-PUBLIC -
If not already done, open a terminal and create a directory for CFDEM(R)coupling in $HOME: -
-cd --
mkdir CFDEM --
cd CFDEM --
Make sure that OpenFOAM(R) is already set up correctly! -
-To clone the public CFDEM(R)coupling repository, open a terminal and execute: -
--git clone git://github.com/CFDEMproject/CFDEMcoupling-PUBLIC.git CFDEMcoupling-PUBLIC-$WM_PROJECT_VERSION -
Troubles? See Troubleshooting section below. -
-Update your repositories by git pull: -
-To get the latest version, open a terminal, go to the location of your local installation and type: -Warning: git stash will remove your changes in $HOME/CFDEM/CFDEMcoupling-PUBLIC-$WM_PROJECT_VERSION ! -
-cd $HOME/CFDEM/CFDEMcoupling-PUBLIC-$WM_PROJECT_VERSION -git stash -git pull --
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 & --
add the lines (you find them also in .../cfdemParticle/etc/bashrc and cshrc respectively): -
-#================================================# -#- 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 -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/lagrangian/cfdemParticle/etc/bashrc -export CFDEM_LIGGGHTS_SRC_DIR=$HOME/LIGGGHTS/LIGGGHTS-PUBLIC/src -export CFDEM_LIGGGHTS_MAKEFILE_NAME=fedora_fpic -export CFDEM_LPP_DIR=$HOME/LIGGGHTS/mylpp/src -export CFDEM_PIZZA_DIR=$HOME/LIGGGHTS/PIZZA/gran_pizza_17Aug10/src -. $CFDEM_bashrc -#================================================# --
Save the ~/.bashrc, open a new terminal and test the settings. The commands: -
-$CFDEM_PROJECT_DIR -$CFDEM_SRC_DIR -$CFDEM_LIGGGHTS_SRC_DIR --
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/lagrangian/cfdemParticle/etc/bashrc. -
-If $CFDEM_SRC_DIR is set correctly, you can type -
-cfdemSysTest --
to get some information if the paths are set correctly. -
-Compile LIGGGHTS(R) and CFDEM(R)coupling: -
-If above settings were done correctly, you can compile LIGGGHTS(R) by typing: -
-cfdemCompLIG --
and you can then compile CFDEM(R)coupling by typing: -
-cfdemCompCFDEM --
You can run the tutorial cases by executing .../etc/testTutorial.sh through the alias cfdemTestTUT. -Alternatively you can run each tutorial using the Allrun.sh scripts in the tutorial directories. -
-In case questions concerning the installation arise, please feel free to contact our forum at www.cfdem.com. -
-Run Your Own Cases: -
-If you want to run your own cases, please do so in $CFDEM_PROJECT_USER_DIR/run which is automatically being generated. E.g. copy one of the tutorial cases there, adapt it to your needs. -Changes in $CFDEM_TUT_DIR will be lost after every git stash! -
-Additional Installations: -
-Optionally you can install lpp which will help you convert the DEM (dump) data to VTK format. For standard CFD-DEM runs this will not be necessary. To get the DEM postprocessing tool "lpp" you need python-numpy package installed: -
-sudo apt-get install python-numpy --
You can pull the latest version of lpp with: -
-cd $HOME/LIGGGHTS --
git clone git://cfdem.git.sourceforge.net/gitroot/cfdem/lpp mylpp --
Backwards Compatibility: -
-Basically CFDEM(R)coupling supports one OpenFOAM(R) version therefore all settings are prepared for that. Nevertheless we try to maintain backwards compatibility as long as it works with reasonable effort. -
-The supported OpenFOAM(R) and LIGGGHTS(R) versions are stated in: -src/lagrangian/cfdemParticle/cfdTools/versionInfo.H -
-For using other versions you can manipulate: -src/lagrangian/cfdemParticle/etc/OFversion/OFversion.H -(still not all functionality might work then!) -
-Troubleshooting: -
-a) The git protocol will not work if your computer is behind a firewall which blocks the relevant TCP port, you can use alternatively (write command in one line): -
-git clone https://user@github.com/CFDEMproject/CFDEMcoupling-PUBLIC.git -CFDEMcoupling-PUBLIC-$WM_PROJECT_VERSION -
-b) If you face the error: "error: SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed while accessing https://github.com/...", -
-please use: env GIT_SSL_NO_VERIFY=true git clone https://github... -
-(see http://stackoverflow.com/questions/3777075/https-github-access) -
-c) If you face the error: "Agent admitted failure to sign using the key. Permission denied (publickey).", after ssh -T git@github.com -
-please type: "ssh-add" -
-(see: https://help.github.com/articles/error-agent-admitted-failure-to-sign) -
- diff --git a/doc/githubAccess_public.pdf b/doc/githubAccess_public.pdf deleted file mode 100644 index 13f6bb53..00000000 Binary files a/doc/githubAccess_public.pdf and /dev/null differ diff --git a/doc/liggghtsCommandModel.html b/doc/liggghtsCommandModel.html deleted file mode 100644 index 2c0ca7e6..00000000 --- a/doc/liggghtsCommandModel.html +++ /dev/null @@ -1,44 +0,0 @@ - -Syntax: -
-Defined in liggghtsCommmands dictionary. -
-liggghtsCommandModels -( - model_x - model_y -); --
Examples: -
-liggghtsCommandModels -( - runLiggghts - writeLiggghts -); --
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. -
- diff --git a/doc/liggghtsCommandModel_execute.html b/doc/liggghtsCommandModel_execute.html deleted file mode 100644 index 58909fe3..00000000 --- a/doc/liggghtsCommandModel_execute.html +++ /dev/null @@ -1,97 +0,0 @@ - -Syntax: -
-Defined in liggghtsCommmands dictionary. -
-liggghtsCommandModels
-(
- execute
-);
-executeProps0
-{
- command
- (
- run
- $couplingInterval
- );
- runFirst switch1;
- runLast switch2;
- runEveryCouplingStep switch3;
- runEveryWriteStep switch4;
- verbose;
-}
-
-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;
-}
-
-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. -
-Restrictions: None. -
-Related commands: -
- - diff --git a/doc/liggghtsCommandModel_readLiggghtsData.html b/doc/liggghtsCommandModel_readLiggghtsData.html deleted file mode 100644 index 1981d499..00000000 --- a/doc/liggghtsCommandModel_readLiggghtsData.html +++ /dev/null @@ -1,49 +0,0 @@ - -Syntax: -
-Defined in liggghtsCommmands dictionary. -
-liggghtsCommandModels
-(
- readLiggghtsData
-);
-readLiggghtsDataProps0
-{
- ???
-}
-
-Examples: -
-liggghtsCommandModels
-(
- readLiggghtsData
- readLiggghtsData
-);
-readLiggghtsDataProps0
-{
- ???
-}
-
-Description: -
-The readLiggghtsData liggghtsCommand Model can be used to ??? -
-Restrictions: -
-Note: Model is not up to date. -
-Related commands: -
- - diff --git a/doc/liggghtsCommandModel_runLiggghts.html b/doc/liggghtsCommandModel_runLiggghts.html deleted file mode 100644 index b9ad8864..00000000 --- a/doc/liggghtsCommandModel_runLiggghts.html +++ /dev/null @@ -1,44 +0,0 @@ - -Syntax: -
-Defined in liggghtsCommmands dictionary. -
-liggghtsCommandModels
-(
- runLiggghts
-);
-//- optional
-runLiggghtsProps
-{
- preNo true;
- verbose; (optional)
-}
-
-Examples: -
-liggghtsCommandModels -( - runLiggghts -); --
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 automatically set according to the coupling intervals, every coupling step. Optionally a dictionary called runLiggghtsProps can be specified where the "preNo" switch can be set, which uses the command "run $nrDEMsteps pre no" for every time step except the first. -
-Restrictions: Warning: the "pre no" option can cause troubles (dump data of particles changing the domain might be erroneous)! -
-Related commands: -
- - diff --git a/doc/liggghtsCommandModel_writeLiggghts.html b/doc/liggghtsCommandModel_writeLiggghts.html deleted file mode 100644 index 1fa64a67..00000000 --- a/doc/liggghtsCommandModel_writeLiggghts.html +++ /dev/null @@ -1,56 +0,0 @@ - -Syntax: -
-Defined in liggghtsCommmands dictionary. -
-liggghtsCommandModels
-(
- writeLiggghts
-);
-//- optional
-writeLiggghtsProps
-{
- writeLast switch1;
- writeName "name";
- overwrite switch2;
- verbose;
-}
-
-Examples: -
-liggghtsCommandModels -( - runLiggghts - writeLiggghts -); --
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: -
- - diff --git a/doc/locateModel.html b/doc/locateModel.html deleted file mode 100644 index 58c59a0f..00000000 --- a/doc/locateModel.html +++ /dev/null @@ -1,34 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-locateModel model; --
Examples: -
-locateModel engine; --
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. -
- diff --git a/doc/locateModel_engineSearch.html b/doc/locateModel_engineSearch.html deleted file mode 100644 index c68e36f2..00000000 --- a/doc/locateModel_engineSearch.html +++ /dev/null @@ -1,51 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-locateModel engine;
-engineProps
-{
- treeSearch switch1;
-}
-
-Examples: -
-locateModel engine;
-engineProps
-{
- treeSearch true;
-}
-
-Description: -
-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: -
-Restrictions: none. -
-Related commands: -
- - diff --git a/doc/locateModel_engineSearchIB.html b/doc/locateModel_engineSearchIB.html deleted file mode 100644 index 16ec8ce5..00000000 --- a/doc/locateModel_engineSearchIB.html +++ /dev/null @@ -1,70 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-locateModel engineIB;
-engineIBProps
-{
- engineProps
- {
- treeSearch switch1;
- }
- zSplit value1;
- xySplit value2;
-}
-
-Examples: -
-locateModel engineIB;
-engineIBProps
-{
- engineProps
- {
- treeSearch false;
- }
- zSplit 8;
- xySplit 16;
-}
-
-Description: -
-The locateModel "engine" locates the CFD cell and cellID corresponding to a given position. This locate model is especially designed for parallel immersed boundary method. Each particle is represented by "satellite points" if it is distributed over several processors. -
-The engineSearchIB locate Model can be used with different settings to use different algorithms: -
-This model is a modification of the engine search model. Instead of using the centre-cell as starting point for the engine search, further satellite points located on the surface of the sphere are checked. This ensures that (parts of) spheres can be located even when their centre is on another processor. This is especially important for parallel computations, when a sphere is about to move from one processor to another. -
-Restrictions: -
-Only for immersed boundary solvers! -
-Related commands: -
- - diff --git a/doc/locateModel_engineSearchMany2Many.html b/doc/locateModel_engineSearchMany2Many.html deleted file mode 100644 index fba74cd4..00000000 --- a/doc/locateModel_engineSearchMany2Many.html +++ /dev/null @@ -1,59 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-locateModel engineSearchMany2Many;
-engineSearchMany2ManyProps
-{
- engineProps
- {
- treeSearch switch1;
- }
-}
-
-switch1 = switch to use tree search algorithm
-
-
-Examples: -
-locateModel engineSearchMany2Many;
-engineSearchMany2ManyProps
-{
- engineProps
- {
- treeSearch true;
- }
-}
-
-Description: -
-The locateModel "engine" locates the CFD cell and cellID corresponding to a given position. This model is a dummy for the "twoWayMany2Many" dataExchangeModel which locates using the specified "engine" during coupling. Using this model with any other dataExchangeModel will cause problems. -
-The engineSearchMany2Many locateModel can be used with different settings to use different algorithms: -
-Restrictions: -
-Use only with the twoWayMany2Many dataExchangeModel! -
-Related commands: -
- - diff --git a/doc/locateModel_standardSearch.html b/doc/locateModel_standardSearch.html deleted file mode 100644 index d5e37a0a..00000000 --- a/doc/locateModel_standardSearch.html +++ /dev/null @@ -1,32 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-locateModel standard; --
Examples: -
-locateModel standard; --
Description: -
-The locateModel "standard" locates the CFD cell and cellID corresponding to a given position. A very straight-forward (robust!) locate algorithm is used. -
-Restrictions: none. -
-Related commands: -
- - diff --git a/doc/locateModel_turboEngineSearch.html b/doc/locateModel_turboEngineSearch.html deleted file mode 100644 index 7adacd7b..00000000 --- a/doc/locateModel_turboEngineSearch.html +++ /dev/null @@ -1,51 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-locateModel turboEngine;
-turboEngineProps
-{
- treeSearch switch1;
-}
-
-Examples: -
-locateModel turboEngine;
-turboEngineProps
-{
- treeSearch true;
-}
-
-Description: -
-The locateModel "turboEngine" locates the CFD cell and cellID corresponding to a given position. The algorithm is improved compared to engine search to show better parallel performance. -
-The turboEngineSearch locate Model can be used with different settings to use different algorithms: -
-Restrictions: none. -
-Related commands: -
- - diff --git a/doc/meshMotionModel.html b/doc/meshMotionModel.html deleted file mode 100644 index c056b6b4..00000000 --- a/doc/meshMotionModel.html +++ /dev/null @@ -1,34 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-meshMotionModel model; --
Examples: -
-meshMotionModel noMeshMotion; --
Note: This examples list might not be complete - please look for other models (meshMotionModel_XY) in this documentation. -
-Description: -
-The meshMotionModel is the base class for models which manipulate the CFD mesh according to the DEM mesh motion. -
-Restrictions: none. -
-Default: none. -
- diff --git a/doc/meshMotionModel_noMeshMotion.html b/doc/meshMotionModel_noMeshMotion.html deleted file mode 100644 index 5f166bd4..00000000 --- a/doc/meshMotionModel_noMeshMotion.html +++ /dev/null @@ -1,32 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-meshMotionModel noMeshMotion; --
Examples: -
-meshMotionModel noMeshMotion; --
Description: -
-The noMeshMotion-model is a dummy meshMotion model. -
-Restrictions: None. -
-Related commands: -
- - diff --git a/doc/momCoupleModel.html b/doc/momCoupleModel.html deleted file mode 100644 index 3a37c23a..00000000 --- a/doc/momCoupleModel.html +++ /dev/null @@ -1,45 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-momCoupleModels -( - model -); --
Examples: -
-momCoupleModels -( - implicitCouple -); --
Note: This examples list might not be complete - please look for other models (momCoupleModel_XY) in this documentation. -
-Forces can be coupled in an implicit way to the fluid solver (i.e., when solving the Navier-Stokes equations, the fluid velocity at the new time will be considered for the coupling force). This implicit coupling is typically done for the drag forces (look for "impForces()" in the implementation of the drag model). Implicit coupling is more stable (especially important for dense flows), but conflicts Newton's third law. Explicit forces are imposed on the flow solver in an explicit fashion (look for "expForces()" in the implementation of the drag model), which is less stable, but does not conflict Newton's third law. -
-Note that the variable "imExSplitFactor" can be set in the couplingProperties in order to treat implicitly defined forces (in the implementation of the force model) as explicit ones. "imExSplitFactor 1.0;" is set by default, meaning that all implicit forces will be considered implicitly, whereas "imExSplitFactor 0.0;" would mean that implicitly defined forces will be treated in an explicit fashion. -
-Note that the switch "treatVoidCellsAsExplicitForce true;" can be set in the couplingProperties in order to change the treatment of cells which are void of particles. This is only relevant if (i) smoothing is used, and (ii) implicit force coupling is performed. By default, the particle veloctiy field (Us) will be smoothed to obtain a meaningful reference quantity for the implicit force coupling. In case "treatVoidCellsAsExplicitForce true;" is set, however, Us will not be smoothed and implicit forces (after the smoothing has been performed) in cells void of particles be treated as explicit ones. This avoids the problem of defining Us in cells that are void of particles, but for which an implicit coupling force is obtained in the smoothing process. -Description: -
-The momCoupleModel is the base class for momentum exchange between DEM and CFD simulation. -
-Restrictions: none. -
-Default: none. -
- diff --git a/doc/momCoupleModel_explicitCouple.html b/doc/momCoupleModel_explicitCouple.html deleted file mode 100644 index ac6b5ba5..00000000 --- a/doc/momCoupleModel_explicitCouple.html +++ /dev/null @@ -1,52 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-momCoupleModels
-(
- explicitCouple
-);
-explicitCoupleProps
-{
- fLimit vector;
-}
-
-Examples: -
-momCoupleModels
-(
- explicitCouple
-);
-explicitCoupleProps
-{
- fLimit (1e3 1e2 1e4);
-}
-
-Description: -
-The explicitCouple-model is a momCoupleModel model providing an explicit momentum source term for the CFD solver. -
-Restrictions: -
-Only for solvers that include explicit momentum exchange. -
-Related commands: -
- - diff --git a/doc/momCoupleModel_implicitCouple.html b/doc/momCoupleModel_implicitCouple.html deleted file mode 100644 index f2b1a00a..00000000 --- a/doc/momCoupleModel_implicitCouple.html +++ /dev/null @@ -1,62 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-momCoupleModels
-(
- implicitCouple
-);
-implicitCoupleProps
-{
- velFieldName "U";
- granVelFieldName "Us";
- voidfractionFieldName "voidfraction";
- minAlphaP number;
-}
-
-Examples: -
-momCoupleModels
-(
- implicitCouple
-);
-implicitCoupleProps
-{
- velFieldName "U";
- granVelFieldName "Us";
- voidfractionFieldName "voidfraction";
-}
-
-Description: -
-The implicitCouple-model is a momCoupleModel model providing an implicit momentum source term for the CFD solver. -
-Restrictions: -
-Only for solvers that include implicit momentum exchange. -
-Related commands: -
- - diff --git a/doc/momCoupleModel_noCouple.html b/doc/momCoupleModel_noCouple.html deleted file mode 100644 index 0ec1e601..00000000 --- a/doc/momCoupleModel_noCouple.html +++ /dev/null @@ -1,40 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-momCoupleModels -( - off -); --
Examples: -
-momCoupleModels -( - off -); --
Description: -
-The noCouple-model is a dummy momCoupleModel model providing a no momentum source term for the CFD solver. -
-Restrictions: -
-Only for solvers that include no momentum exchange, e.g. immersed boundary. -
-Related commands: -
- - diff --git a/doc/probeModel.html b/doc/probeModel.html deleted file mode 100644 index 72309a36..00000000 --- a/doc/probeModel.html +++ /dev/null @@ -1,42 +0,0 @@ - -Syntax: -
-To be activated via couplingProperties dictionary. -
-probeModel myProbeModel; --
Use probe model "off" to disable this feature. -
-myProbeModelProps --
{
-
-}; --
Examples: -
-See particleProbe -
-Note: This examples list might not be complete - please check below for the list of force models that can perform particle probing. -
-Description: -
-The probeModel feature allows to implement various probing features in CFDEM. Currently, only the particleProbe model is implemented, that performs probing of particle forces. -
-Restrictions: -
-None. -
-Default: none. -
- diff --git a/doc/probeModel_noProbe.html b/doc/probeModel_noProbe.html deleted file mode 100644 index 63021115..00000000 --- a/doc/probeModel_noProbe.html +++ /dev/null @@ -1,43 +0,0 @@ - -Syntax: -
-To be activated via couplingProperties dictionary. -
-forceModels
-{
- myForceModel1
- myForceModel2
- myForceModel3
-};
-
-Examples: -
-probeModel off; --
Note: This examples list might not be complete - please check below for the list of force models that can perform particle probing. -
-Description: -
-Does not perform any probing. -
-Restrictions: -
-None. -
-Related commands which are currently enabled for particle probing: -
- -Default: none. -
- diff --git a/doc/regionModel.html b/doc/regionModel.html deleted file mode 100644 index 7d2304f6..00000000 --- a/doc/regionModel.html +++ /dev/null @@ -1,34 +0,0 @@ - -Syntax: -
-Note: In the current CFDEMcoupling version, this model is no longer used. Defined in couplingProperties dictionary. -
-regionModel model; --
Examples: -
-regionModel allRegion; --
Note: This examples list might not be complete - please look for other models (regionModel_XY) in this documentation. -
-Description: -
-The regionModel is the base class for region models to select a certain region for coupled simulation. -
-Restrictions: none. -
-Default: none. -
- diff --git a/doc/regionModel_allRegion.html b/doc/regionModel_allRegion.html deleted file mode 100644 index 048c863e..00000000 --- a/doc/regionModel_allRegion.html +++ /dev/null @@ -1,32 +0,0 @@ - -Syntax: -
-Note: In the current CFDEMcoupling version, this model is no longer used. Defined in couplingProperties dictionary. -
-regionModel allRegion; --
Examples: -
-regionModel allRegion; --
Description: -
-The allRegion-model is a region model including the whole CFD region for the coupling. -
-Restrictions: None. -
-Related commands: -
- - diff --git a/doc/smoothingModel.html b/doc/smoothingModel.html deleted file mode 100644 index 78e8f23e..00000000 --- a/doc/smoothingModel.html +++ /dev/null @@ -1,38 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-smoothingModel model; --
Examples: -
-smoothingModel off; --
smoothingModel constDiffSmoothing; --
Note: This examples list might not be complete - please look for other models (smoothingModel_XY) in this documentation. -
-ATTENTION: In case a smoothing model is used in conjunction with "PimpleImEx" solvers, the fields "f" and "fSmooth" must be placed in the initial time directory! This is because zeroGradient boundary conditions for the fields "f" and "fSmooth" must be specified, otherwise the smoothing operation will give an Error. -
-Description: -
-The smoothingModel is the base class for models that smoothen the exchange fields (i.e., voidfraction and the Ksl field in case of implicit force coupling). This is relevant in case one uses a small grid resolution compared to the local particle diameter (or parcel diameter in case one uses a parcel approach). -
-Restrictions: These models are in beta testing. -
-Default: none. -
- diff --git a/doc/smoothingModel_constDiffSmoothing.html b/doc/smoothingModel_constDiffSmoothing.html deleted file mode 100644 index cf5904ab..00000000 --- a/doc/smoothingModel_constDiffSmoothing.html +++ /dev/null @@ -1,58 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-smoothingModel constDiffSmoothing;
-constDiffSmoothingProps
-{
- lowerLimit number1;
- upperLimit number2;
- smoothingLength lengthScale;
- smoothingLengthReferenceField lengthScaleRefField;
-}
-
-Examples: -
-constDiffSmoothingProps
-{
- lowerLimit 0.1;
- upperLimit 1e10;
- smoothingLength 1500e-6;
- smoothingLengthReferenceField 9000e-6;
-}
-
-Description: -
-The "constDiffSmoothing" model is a basic smoothingModel model which reads a smoothing length scale being used for smoothing the exchange fields (voidfraction, Ksl, f if present). This model can be used for smoothing explicit force coupling fields, as well as implicit force coupling algorithms. -Smoothing for reference fields is performed to "fill in" values in cells in which these reference fields are not specified. Values calculated in the cells (via Lagrangian-To-Euler mapping) are NOT changed! These reference fields are, e.g., the average particle velocity, which are not specified in all cells in case the flow is rather dilute. -
-Restrictions: This model is tested in a limited number of flow situations. -
-ATTENTION: In case a smoothing model is used in conjunction with "PimpleImEx" solvers, the fields "f" and "fSmooth" must be placed in the initial time directory! This is because zeroGradient boundary conditions for the fields "f" and "fSmooth" must be specified, otherwise the smoothing operation will give an Error. -
-Related commands: -
- - diff --git a/doc/smoothingModel_noSmoothing.html b/doc/smoothingModel_noSmoothing.html deleted file mode 100644 index 40081ed7..00000000 --- a/doc/smoothingModel_noSmoothing.html +++ /dev/null @@ -1,32 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-smoothingModel off; --
Examples: -
-smoothingModel off; --
Description: -
-The "noSmoothing" model is a dummy smoothingModel model which does no smoothing. -
-Restrictions: none. -
-Related commands: -
- - diff --git a/doc/voidFractionModel.html b/doc/voidFractionModel.html deleted file mode 100644 index 0dd37937..00000000 --- a/doc/voidFractionModel.html +++ /dev/null @@ -1,34 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-voidfractionModel model; --
Examples: -
-voidfractionModel centre; --
Note: This examples list might not be complete - please look for other models (voidfractionModel_XY) in this documentation. -
-Description: -
-The voidfractionModel is the base class for models to represent the DEM particle's volume in the CFD domain via a voidfraction field. -
-Restrictions: none. -
-Default: none. -
- diff --git a/doc/voidFractionModel_GaussVoidFraction.html b/doc/voidFractionModel_GaussVoidFraction.html deleted file mode 100644 index 2ad4fd92..00000000 --- a/doc/voidFractionModel_GaussVoidFraction.html +++ /dev/null @@ -1,60 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-voidfractionModel Gauss;
-GaussProps
-{
- maxCellsPerParticle number1;
- alphaMin number2;
- weight number3;
- porosity number4;
-}
-
-Examples: -
-voidfractionModel Gauss;
-GaussProps
-{
- maxCellsPerParticle 1000;
- alphaMin 0.10;
- weight 1.;
- porosity 1.;
-}
-
-Description: -
-The Gauss voidFraction model is supposed to be used when a particle (or its representation) is bigger than a CFD cell. The voidfraction field is set in those cell whose centres are inside the particle. The volume is here distributed according to a Gaussian distribution. -
-The region of influence of a particle can be increased artificially by "porosity", which blows up the particles, but keeps their volume (for voidfraction calculation) constant. -
-The particle volume occupied in the CFD domain can be adjusted by the parameter "weight", using Vparticle=dsphere^3*pi/6*weight. -
-Restrictions: none. -
-Related commands: -
-voidfractionModel , bigParticle -
- diff --git a/doc/voidFractionModel_IBVoidFraction.html b/doc/voidFractionModel_IBVoidFraction.html deleted file mode 100644 index bdb61e78..00000000 --- a/doc/voidFractionModel_IBVoidFraction.html +++ /dev/null @@ -1,56 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-voidfractionModel IB;
-IBProps
-{
- maxCellsPerParticle number1;
- alphaMin number2;
- scaleUpVol number3;
-}
-
-Examples: -
-voidfractionModel IB;
-IBProps
-{
- maxCellsPerParticle 1000;
- alphaMin 0.10;
- scaleUpVol 5.0;
-}
-
-Description: -
-The IB voidFraction model is supposed to be used when a particle (or its representation) is bigger than a CFD cell. The voidfraction field is set in those cell whose centres are inside the particle. The model is specially designed for cfdemSolverIB and creates a smooth transition of the voidfraction at the particle surface. Cells which are only partially covered by solid are marked by voidfraction values between 0 and 1 respectively. -
-The region of influence of a particle can be increased artificially by "scaleUpVol", which blows up the particles, but keeps their volume (for voidfraction calculation) constant. -
-Code of this sub-model contributed by Alice Hager, JKU. -
-Restrictions: none. -
-Related commands: -
- - diff --git a/doc/voidFractionModel_bigParticleVoidFraction.html b/doc/voidFractionModel_bigParticleVoidFraction.html deleted file mode 100644 index ad0b0c05..00000000 --- a/doc/voidFractionModel_bigParticleVoidFraction.html +++ /dev/null @@ -1,62 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-voidfractionModel bigParticle;
-bigParticleProps
-{
- maxCellsPerParticle number1;
- alphaMin number2;
- weight number3;
- porosity number4;
-}
-
-Examples: -
-voidfractionModel bigParticle;
-bigParticleProps
-{
- maxCellsPerParticle 1000;
- alphaMin 0.10;
- weight 1.;
- porosity 5.0;
-}
-
-Description: -
-The bigParticle voidFraction model is supposed to be used when a particle (or its representation) is bigger than a CFD cell. The voidfraction field is set in those cell whose centres are inside the particle which results in a stairstep representation of the bodies within the mesh (i.e. voidfraction is either 1 (fluid) of zero (solid)). For archiving accurate results, approx. 8 cells per particle diameter are necessary. -
-The region of influence of a particle can be increased artificially by "porosity", which blows up the particles, but keeps their volume (for voidfraction calculation) constant. -
-The particle volume occupied in the CFD domain can be adjusted by the parameter "weight", using Vparticle=dsphere^3*pi/6*weight. -
-Parts of this sub-model contributed by Alice Hager, JKU. -
-Restrictions: none. -
-Related commands: -
- - diff --git a/doc/voidFractionModel_centreVoidFraction.html b/doc/voidFractionModel_centreVoidFraction.html deleted file mode 100644 index 94ccd154..00000000 --- a/doc/voidFractionModel_centreVoidFraction.html +++ /dev/null @@ -1,50 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-voidfractionModel centre;
-centreProps
-{
- alphaMin number1;
- weight number2;
-}
-
-Examples: -
-voidfractionModel centre;
-centreProps
-{
- alphaMin 0.1;
- weight 1.;
-}
-
-Description: -
-The centre voidFraction model calculates the voidfraction in a CFD cell accounting for the volume of the particles whose centres are inside the cell. -
-The particle volume occupied in the CFD domain can be adjusted by the parameter "weight", using Vparticle=dsphere^3*pi/6*weight. -
-Restrictions: none. -
-Related commands: -
- - diff --git a/doc/voidFractionModel_dividedVoidFraction.html b/doc/voidFractionModel_dividedVoidFraction.html deleted file mode 100644 index b6cbc2f6..00000000 --- a/doc/voidFractionModel_dividedVoidFraction.html +++ /dev/null @@ -1,60 +0,0 @@ - -Syntax: -
-Defined in couplingProperties dictionary. -
-voidfractionModel divided;
-dividedProps
-{
- alphaMin number1;
- interpolation;
- weight number2;
- porosity number3;
-}
-
-Examples: -
-voidfractionModel divided;
-dividedProps
-{
- alphaMin 0.2;
-}
-
-Description: -
-The divided voidFraction model is supposed to be used when a particle (or its representation) is in the size range of a CFD cell. Satellite points are used to divide the particle's volume to the touched cells. -
-The region of influence of a particle can be increased artificially by "porosity", which blows up the particles, but keeps their volume (for voidfraction calculation) constant. -
-The particle volume occupied in the CFD domain can be adjusted by the parameter "weight", using Vparticle=dsphere^3*pi/6*weight. -
-In the basic implementation of solvers, the void fraction is calculated based on all particles. Depending on the solver used, the void fraction calculation is also performed for a certain type of particles. -The void fraction calculation is based on a three-step approach (reset, set and interpolate), i.e., the void fraction is time interpolated from a previous and a next void fraction field. Appropriate names for these fields have to be specified in the sub-dictionaries voidFracFieldNamesPrev and voidFracFieldNamesNext in the couplingProperties dictionary. -
-Restrictions: none. -
-Related commands: -
- -