forceSubModel command

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
);

model = name of force sub-model to be applied

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.

Switches:

Depending on the availability within the respective force model, a number of switches can be activated:

treatForceExplicit: switch for the purely explicit consideration of the force term in the equation of motion on the CFD side (off -> the force is considered semi-implicitly; default off) treatForceDEM: switch for the consideration of the forces on the DEM side only (off -> calculate forces for DEM and CFD; default off) implForceDEM: If true, the fluid velocity and drag coefficient are communicated to the DEM calculation at each coupling time step and the drag force is calculated at each DEM time step, using the current particle velocity. If false, a force term is communiated to the DEM calculation at each coupling time step, the term is constant for one coupling interval. (on -> DEM forces are updated every DEM step; default off) implForceDEM: If true, all fields for implicit torque handling on DEM side are communicated to DEM. (default off) verbose: switch for debug output to screen (on -> enable debug output; default off) interpolation: switch for the usage of interpolation models when getting data for the Lagrangian calculation from Eulerian fields; If false, the cell centre values are used. (default off) useFilteredDragModel: switch for using a coarse-grid version of the Beetstra drag model (takes grid-size effects into account; default = off) useParcelSizeDependentFilteredDrag: switch for using a coarse-grid version of the Beetstra drag model (takes parcel-size effects into account, will force the switch useFilteredDragModel to “on”; default = off) implForceDEMaccumulated: Can only be used in combination with implForceDEM switch, drag force values of each DEM time step are accumulated and passed on to the CFD-calculation. (default off) scalarViscosity: switch for the usage of a user-defined viscosity nu for the calculation of the drag force; The CFD calculation always uses the value of the transport model. (off -> use tranportProperties nu; default off) voidageFunctionDiFelice: switch for the usage of the DiFelice voidage correction function during the drag force calculation. The correction is given by the relation Xi = 3.7 - 0.65 * exp(-sqr(1.5-log10(Rep))/2), where Rep is the particle Reynolds number. If switch is set to true, the voidageFunctionRong switch (or others) must be set to false if false is not the default value for the selected model. voidageFunctionRong: switch for the usage of the Rong voidage correction function during the drag force calculation. The correction is given by the relation Xi = 2.65 * (voidfraction + 1) - (5.3-3.5*voidfraction)*sqr(voidfraction)*exp(-sqr(1.5-log10(Rep))/2), where Rep is the particle Reynolds number. voidageFunctionTang: switch for the usage of the Tang voidage correction function during the drag force calculation. The correction is given by the relation Xi = 2 - log10(((1.5*sqrt(1-voidfraction)+1)*voidfraction^2 - (10*(voidfraction-1))/(voidfraction^2) + (0.0644*voidfraction^-4+0.169*voidfraction)*Rep^0.657 - (0.00456*Rep)*voidfraction^-4 + 0.11*(voidfraction-2)*(voidfraction-1)*Rep) / (0.2334*Rep^0.657 - 0.00456*Rep + 1)) / log10(voidfraction); (see: 2018,ChemEngSci, Mahajan et al., Non-spherical particles in a pseudo-2d fluidized bed: Modelling Study) , where Rep is the particle Reynolds number.:ul

Restrictions

None.