colorIO

Syntax

Defined in couplingProperties dictionary.

IOModel colorIO;

colorIOProps
{
     partScalarName      wordList;
     partScalarFluxName  wordList;
     partVectorName      wordList;
     partVectorFluxName  wordList;
}

partScalarName = list of the names of the generic scalar DEM quantities to be transferred to the CFD side and written to file. Use this list for properties that are communicated from the DEM to the CFD side (e.g. “Temp”). (default: empty list)
partScalarFluxName = list of the names of the generic scalar DEM quantities to be transferred to the CFD side and written to file. Use this list for properties that are communicated from the CFD to the DEM side (e.g. “convectiveHeatFlux”). (default: empty list)
partVectorName = list of the names of the generic vector-valued DEM quantities to be transferred to the CFD side and written to file. Use this list for properties that are communicated from the DEM to the CFD side (e.g. “omega”). (default: empty list)
partVectorFluxName = list of the names of the generic vector-valued DEM quantities to be transferred to the CFD side and written to file. Use this list for properties that are communicated from the CFD to the DEM side. (default: empty list)

Examples

IOModel colorIO;

colorIOProps
{
    partScalarName
    (
        "color"
        "id"
    );
    partScalarFluxName
    (
        "convectiveHeatFlux"
    );
    partVectorName ( "omega" );
}

Description

The colorIO-model is based on the basicIO model. It allows to write to file additional scalar properties defined on the DEM side. This may include, for example, the particle type, ID, force components, etc.

Using the partScalarFluxName list the user can register additional variables to be communicated to the DEM side if they are required by Aspherix.

Restrictions

Note

This model can only handle scalar and (three-dimensional) vector quantities.