Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question

Revision history [back]

The output folder of an EnergyplusFMU is defined as Output_EPExport_+ the FMU instanceName (e.g. Output_EPExport_Slave1, Output_EPExport_Slave2). The instanceName is supposed to be unique across the FMUs. So if your FMUs have unique instance names then, their outputs should be written in different folders.

The output folder of an EnergyplusFMU is defined as Output_EPExport_+ the FMU instanceName (e.g. Output_EPExport_Slave1, Output_EPExport_Slave2). The In a co-simulation scenario, the instanceName of an FMU is supposed to be unique across the FMUs. So if your FMUs have unique instance names then, their outputs should be written in different folders. folders.

The output folder of an EnergyplusFMU is defined as Output_EPExport_+ the FMU instanceName (e.g. Output_EPExport_Slave1, Output_EPExport_Slave2). In a co-simulation scenario, the instanceName of an FMU is supposed to be unique across the FMUs. So if your FMUs have unique instance names then, their outputs should be written in different folders.

Addition when using pyFMI as the master simulator:

PyFMI doesn't seem to propagate the instanceName to the FMU when using the load_fmu() function. This leads the the challenges observed.

A workaround would be to load the FMU and then call the instantiate() function of PyFMI. This function can get as an argument the FMU instanceName. A potential implementation would look like this:

# The next line loads the FMU
model  = load_fmu('nameOfFMU.fmu')
# The next line passes the instance name to the FMU
model.instantiate('nameOfFMUInstanceName')
# You could the proceed with the `initialize()` method as done earlier

By adding the instantiate() method in the loop, you would avoid overriding the output directory folders

The output folder of an EnergyplusFMU is defined as Output_EPExport_+ the FMU instanceName (e.g. Output_EPExport_Slave1, Output_EPExport_Slave2). In a co-simulation scenario, the instanceName of an FMU is supposed to be unique across the FMUs. So if your FMUs have unique instance names then, their outputs should be written in different folders.

Addition when using pyFMI as the master simulator:

PyFMI doesn't seem to propagate the instanceName to the FMU when using the load_fmu() function. This leads the the challenges observed.

A workaround would be to load the FMU and then call the instantiate() function of PyFMI. This function can get as an argument the FMU instanceName. A potential implementation would look like this:

# The next line loads the FMU
model  = load_fmu('nameOfFMU.fmu')
# The next line passes the instance name to the FMU
model.instantiate('nameOfFMUInstanceName')
# You could the then proceed with the `initialize()` method as done earlier

By adding the instantiate() method in the loop, you would avoid overriding the output directory folders