Function objects are OpenFOAM utilities, designed to ease setups and enhance workflows by generating user-requested data both during runtime and post-processing, typically in the form of logging to the screen, or text, image and field files.

Function objects eliminate the need to store all runtime generated data, hence saving considerable resources. Furthermore, function objects are readily applied to batch-driven processes, improving reliability by standardising the sequence of operations and reducing the amount of manual interaction.

The output of most function objects, e.g. output fields, are stored on the mesh database to enable retrieval and chaining to other function objects and applications, e.g. using wallShearStress function object output in a fieldAverage function object to produce the wallShearStressMean field.

Usage🔗

Function objects can be executed using two methods:

• at run-time: via the functions sub-dictionary in the controlDict file;
• post-processing on time directories:
  • postProcess command-line utility, and
  • <application> -postProcess option available to solver applications.

Run-time🔗

Each function object should be listed inside the functions sub-dictionary of the controlDict file as shown in the following example:

functions    // sub-dictionary name under the system/controlDict file
{
    <userDefinedSubDictName1>
    {
        // Mandatory entries
        type                <functionObjectTypeName>;
        libs                (<libType>FunctionObjects);

        // Mandatory entries defined in <functionObjectType>
        ...

        // Optional entries defined in <functionObjectType>
        ...

        // Optional (inherited) entries
        region              region0;
        enabled             true;
        log                 true;
        timeStart           0;
        timeEnd             1000;
        executeControl      timeStep;
        executeInterval     1;
        writeControl        timeStep;
        writeInterval       1;
    }

    <userDefinedSubDictName2>
    {
        ...
    }

    ...

    <userDefinedSubDictNameN>
    {
        ...
    }
}

where the entries are described below:

The sub-dictionary name <userDefinedSubDictName> is chosen by the user, and is typically used as the name of the output directory for any data written by the function object.

As the base mandatory entry, the type entry defines the type of function object properties that follow. Function objects are packaged into separate libraries for flexibility and the libs entry is used to specify which library should be loaded.

Function object controls🔗

When applied at run-time, the objects are controlled according to the optional two time-based entries:

• executeControl: when the object is updated (for updating calculations or for management tasks),
• writeControl: when the object output is written (for writing the calculated data to disk).

If neither entries are present the object will execute and write every time step—which can create much more data than intended!

Values for these controls take the same type of values as the writeControl entry in the controlDict, with some additions:

For example, to set a Courant Number function object to evaluate every 2 time steps and write at every output time:

functions
{
    Co1
    {
        type                CourantNo;
        libs                (fieldFunctionObjects);
        executeControl      timeStep;
        executeInterval     2;
        writeControl        writeTime;
    }
}

Data derived from function objects are written to the case postProcessing directory or to the time directories, typically in a subdirectory with the same name as the object, e.g.

$FOAM_CASE/postProcessing/<functionObjectName>/<time>/<data>

$FOAM_CASE/<time>/<outField>

Many function objects create fields that can be stored for later use. To avoid potential name clashes in the database, the useNamePrefix entry can be used to prepend the name of the function object to the name of the output field, e.g. applied to a fieldAverage function object, a velocity mean field could be named fieldAverage1:UMean.

Post-processing on time directories🔗

Post-process utility

The standalone postProcess utility executes function objects on disk-based data in time directories. For more information, please see:

• postProcess utility.

Application post-processing

The -postProcess command-line option is available to all solvers, and operates similarly to the stand-alone postProcess utility. For example, having completed a simpleFoam calculation, the following will execute all function objects defined in the controlDict file for all time directories:

simpleFoam -postProcess

which will execute all function objects defined in the controlDict.

Options🔗

Function objects are grouped into libraries that perform similar operations or operate on similar object types:

• Field
• Forces
• Graphics
• Lagrangian
• Sampling
• Solvers
• Utilities

Further information🔗

Source code:

• $FOAM_SRC/OpenFOAM/db/functionObjects
• $FOAM_SRC/functionObjects

API:

• Source documentation