EnergyPlus™ is a whole building energy simulation program that engineers, architects, and researchers use to model both energy consumption and water use in buildings.
In calculating the Fanger thermal comfort values, such as PMV and PPD in a simulation run, the calculated PMV values look like if it is one time-step behind the corresponding temperature values (such as zone air temperature or zone radiant temperature). This is especially the case when the air temperature in a zone abruptly changes (e.g. when the thermostat setpoint changes).
The cause of the problem is that the calculation module uses as a saved zone air temperature value for the previous time step, which causes the calculated PMV lagging behind. The calculated PMV value is thus off from what is “supposed” to be, depending on how quickly the zone air temperature changes.
There is limited impact to the average users who do not need precise real-time thermal comfort information. Currently no workaround is available. The bug is expected to be fixed in future releases.
Details
Some additional details for this issue (if relevant):
Platform (Operating system, version) All
Version of EnergyPlus (if using an intermediate build, include SHA): 9.4, probably all
Helpdesk ticket number 15616
Checklist
Add to this list or remove from it as applicable. This is a simple templated set of guidelines.
Issue overview
In calculating the Fanger thermal comfort values, such as PMV and PPD in a simulation run, the calculated PMV values look like if it is one time-step behind the corresponding temperature values (such as zone air temperature or zone radiant temperature). This is especially the case when the air temperature in a zone abruptly changes (e.g. when the thermostat setpoint changes).
The cause of the problem is that the calculation module uses as a saved zone air temperature value for the previous time step, which causes the calculated PMV lagging behind. The calculated PMV value is thus off from what is “supposed” to be, depending on how quickly the zone air temperature changes.
There is limited impact to the average users who do not need precise real-time thermal comfort information. Currently no workaround is available. The bug is expected to be fixed in future releases.
Details
Some additional details for this issue (if relevant):
Checklist
Add to this list or remove from it as applicable. This is a simple templated set of guidelines.