noDrag

Syntax

Defined in couplingProperties dictionary.

forceModels
(
    noDrag
);

noDragProps
{
    noDEMForce switch;
    noCFDForce switch;
}

  • noDEMForce = do not apply the previously calculated forces (implicitly and explicitly treated) in DEM integration (default: false)

  • noCFDForce = do not apply the previously calculated forces (implicitly and explicitly treated) and use them in CFD source terms (default: true)

Examples

Following settings discard the contribution of DiFeliceDrag on the CFD side only. Archimedes force will impact both particles and the fluid as it is executed after the noDrag model.

forceModels
(
    DiFeliceDrag
    noDrag
    Archimedes
);

noDragProps
{
    noDEMForce false;
    noCFDForce true;
};

Description

The noDrag model discards all previously computed forces (in terms of the forceModels list) and sets them to zero. If several force models are selected and noDrag is the last model being executed, the entire-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.

This model can be used to create a one-way coupling between particles and fluid if noCFDForce true. In this scenario the user should also take care of the voidfraction model settings and limit the voidfraction alphaMin 1; to minimize tha particle impact on the fluid flow.

Note

This model is not supposed to be used as a stand-alone model or as a replacement for a another forceModel. Doing so will almost certainly result in errors during communication setup using the twoWaySocket data exhcange model. Instead, this model should be appended to the list of force models where appropriate.

Restrictions

None.