Edit me

This libray offers the opportunity to connect OpenFOAM with FMUs in two ways

  • generate an FMU from an OpenFOAM case
  • run FMUs in OpenFOAM

run FMUs within an OpenFOAM solver

One of the biggest feature of OpenFOAM is that it can be easily extended by linking new libraries to the solver at runtime. One example are functionObjects that are loaded at runtime and have to be placed in the system/controlDict in the functions dictionary. To run FMUs in OpenFOAM, the FMUSimulator needs to be copied into the controlDict:


        type            FMUSimulator; // execute functionObjects FMUSimualtor
        libs            (pyFMUSim); // load "libpyFMUSim.so"
        pyClassName     controlledTemperature; // execute python class controlledTemperature
        pyFileName      controlledTemperature; // load file controlledTemperature.py

With this entry, the OpenFOAM-solver loads the library pyFMUSIM - short for libpyFMUSIM.so - that specifies a new implementation of the functionObject FMUSimulator. Under the hood FMUSimulator embeds a python interpreter that manages the FMUs. The embedded python interpreter simplifies the installation through pip or conda and the user can choose from multiple frameworks such as pyfmi, fmpy or omsimulator. Another huge advantage is that the user can connect multiple FMUs in python and test them before connecting them to OpenFOAM. After sucessfully testing the FMU System, the FMUSimulator will call the class pyClassName in pyFileName that is assumed to be located in the root of the OpenFOAM case. The class looks as follows:

import FMU4FOAM
from OMSimulator import OMSimulator

class controlledTemperature(FMU4FOAM.FMUBase):

    def __init__(self,endTime,filename):
        self.oms = OMSimulator()
        self.oms.addSystem("model.root", self.oms.system_wc)

        # instantiate FMUs
        self.oms.addSubModel("model.root.system1", "ControlledTemperatureCoupled.fmu")

        # simulation settings
        self.oms.setResultFile("model", "controlledTemperature.csv")
        self.oms.setStopTime("model", endTime)
        # self.oms.setFixedStepSize("model.root", 1e-7)

        self.oms.setReal("model.root.system1.Tin", 298)
        self.oms.setReal("model.root.system1.dTin", 0)


    def setVar(self, key: str, val: float) -> None:
        return self.oms.setReal(key,val)

    def getVar(self, key: str) -> float:
        return self.oms.getReal(key)[0]

    def stepUntil(self,t):
        self.oms.setReal("model.root.system1.dTin", 0)

    def __del__(self):

It consists of a constructor that initializes the simulation, a destructor that finalizes the simulation and a method that advances the FMU system in time called stepUntil. The data transfer between OpenFOAM and the FMUs is handled by FMUBase with the method from_OF and to_OF and requires the definition of setVar and getVar:

    class FMUBase(ABC):


    def setVar(key: str,val: float) -> None:

    def getVar(key: str) -> float:

    def from_OF(self,dumped_input_json : str):
        ext_inputs = json.loads(dumped_input_json)
        for k in self.coupleData.from_OF:
            var = (k,ext_inputs[k])

    def to_OF(self) -> str:
        d = {}
        for k in self.coupleData.to_OF:
            d[k] = self.getValue(self.getVar,k)
        return str(json.dumps(d))

It is possible to overload this function and replace it by custom solutions that fit the user’s needs but in most cases it should be sufficient to specify the FMU.json in the root of the OpenFOAM case:

    "mapping": [["Tin","model.root.system1.Tin"],
    "from_OF": {"Tin":"REAL",
    "to_OF":   {"Qout":"REAL"}

The FMU.json has to have three entries:

  • mapping : List of all OpenFOAM variables —-> FMU variables
  • from_OF : List of the variables and its types computed by OpenFOAM
  • to_OF : List of the variables and its types computed by the FMU

NOTE: from_OF and to_OF the OpenFOAM variable names need to be specified and the mapping assumes OF to FMU