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
We observed some fan powers were 0.0 in the PRM tests.
Tracing the code reveals that the pressure rise in the On/Off fans was set to 0 here. A 0.0 pressure rise results in 0.0 fan power.
Checking the cause in the baseline generation code indicates the zone designAirFlowRate was set to 0.0, so this might be a broad issue affecting all system types listed here.
Digging the cause of the 0 designAirFlowRate in the sizing script shows the query includes ReportName='Initialization Summary', which causes the val to be an empty list.
In 3.5.1 (Eplus 22), the Initialization Summary should have no space in between, as the image shows. Correcting this to ReportName='InitializationSummary' generates the correct outcome for PRMs running on 3.5.1.
This seems to be a much broader issue, as multiple routines reference this function. Any thoughts?
The text was updated successfully, but these errors were encountered:
Thanks for finding this. All of the methods in openstudio-standard's hvac_sizing will be native to OpenStudio in OS v3.6.0. We'll keep the calls in openstudio-standards for this release and maybe the next release, but will then remove them.
OS Version 3.5.1
We observed some fan powers were 0.0 in the PRM tests.
Tracing the code reveals that the pressure rise in the On/Off fans was set to 0 here. A 0.0 pressure rise results in 0.0 fan power.
Checking the cause in the baseline generation code indicates the zone designAirFlowRate was set to 0.0, so this might be a broad issue affecting all system types listed here.
Digging the cause of the 0 designAirFlowRate in the sizing script shows the query includes
ReportName='Initialization Summary'
, which causes theval
to be an empty list.In 3.5.1 (Eplus 22), the Initialization Summary should have no space in between, as the image shows. Correcting this to
ReportName='InitializationSummary'
generates the correct outcome for PRMs running on 3.5.1.This seems to be a much broader issue, as multiple routines reference this function. Any thoughts?
The text was updated successfully, but these errors were encountered: