You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Model: The model with Spawn.
I exported the model by Dymola 2023 to FMU (Co-simulation, 64-bit).
I could run this FMU in Python for a whole day.
I could also run this FMU in a timestep and then continue it for another.
But I could not run this FMU at the same timestep by reset () and initialize ().
The console will report "Writing tabular output file results using HTML format.", and then no reaction anymore.
I test the model without Spawn in the same framework. The FMU could be simulated in the same timestep by reset () and initialize().
I'm wondering if that's because EnergyPlus's FMU doesn't be initialized even though I give commands "FMU.reset ()" and "FMU. initialize()" to the total FMU for the model with Spawn.
I tried to manually load the EnergyPlus's FMU generated by Spawn.exe in this process and initialize it. But it doesn't work.
Maybe they are two different instances from the same EnergyPlus FMU.
Expected behavior
The expected behavior is the model could be run again during the same timestep for optimization control like MPC.
Screenshots
If applicable, add screenshots to help explain your problem.
The FMU setting.
The model with Spawn can not be reset and initialized by initialize() or enter_initialization_mode() and exit_initialization_mode().
The model without Spawn can be reset and initialized by initialize().
Version
Modelica Buildings Library: [9.0.0]
Modelica simulation environment: Dymola 2023
Operating system: Windows 10
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Because the EnergyPlus binaries do not allow saving and reinitializing the state, Modelica models with the Spawn coupling can't be used in such a workflow. If you need this capability, you will need to model the envelope in Modelica.
Because the EnergyPlus binaries do not allow saving and reinitializing the state, Modelica models with the Spawn coupling can't be used in such a workflow. If you need this capability, you will need to model the envelope in Modelica.
Describe the bug
Model: The model with Spawn.
I exported the model by Dymola 2023 to FMU (Co-simulation, 64-bit).
I could run this FMU in Python for a whole day.
I could also run this FMU in a timestep and then continue it for another.
But I could not run this FMU at the same timestep by reset () and initialize ().
The console will report "Writing tabular output file results using HTML format.", and then no reaction anymore.
I test the model without Spawn in the same framework. The FMU could be simulated in the same timestep by reset () and initialize().
I'm wondering if that's because EnergyPlus's FMU doesn't be initialized even though I give commands "FMU.reset ()" and "FMU. initialize()" to the total FMU for the model with Spawn.
I tried to manually load the EnergyPlus's FMU generated by Spawn.exe in this process and initialize it. But it doesn't work.
Maybe they are two different instances from the same EnergyPlus FMU.
Expected behavior
The expected behavior is the model could be run again during the same timestep for optimization control like MPC.
Screenshots
If applicable, add screenshots to help explain your problem.
The FMU setting.
The model with Spawn can not be reset and initialized by initialize() or enter_initialization_mode() and exit_initialization_mode().
The model without Spawn can be reset and initialized by initialize().
Version
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: