Revision history [back]

Hi everyone. I am using the new EnergyPlus Python API in version 9.4. When I set the callback_begin_zone_timestep_after_init_heat_balance function from the Runtime API, I set a function to run when the simulation starts. In this way, with the Data Transfer API I obtain information on each time step and execute actions according to some calculations.

My problem starts when the Warming process is executed. During this initial stage of the simulation, the callback function is also executed, which I would like to avoid, because it hinders the information that I generate and then do a post-processing.

Is there a way to identify the beginning and the end of the Warming with the EnergyPlus Python API? Or any alternative to execute the callback function after the Warming process finishes? Thanks

Hi everyone. I am using the new EnergyPlus Python API in version 9.4. When I set the callback_begin_zone_timestep_after_init_heat_balance function from the Runtime API, I set a function to run when the simulation starts. In this way, with the Data Transfer API I obtain information on each time step and execute actions according to some calculations.

My problem starts when the Warming process is executed. During this initial stage of the simulation, the callback function is also executed, which I would like to avoid, because it hinders the information that I generate and then do a post-processing.

Is there a way to identify the beginning and the end of the Warming with the EnergyPlus Python API? Or any alternative to execute the callback function after the Warming process finishes? Thanks