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
1. All days of week are applied to ScheduleRules (Priority # schedules). This can be seen in (2) below, but not sure if the gbXML file has weekday/end schedules. The gbXMLStandard Test Model 2016.xml has weekday/end schedules, which shows the issue definitively. As a fix, these should follow the occupancy schedules.
When looking at a couple OpenStudio models, it seems that some models have the priority of the schedules to always setback the thermostat resulting in incorrect energy values - sizing does not seem to be affected. A customer model is attached showing the setback issue.
Note, the 26.1C (79F) is the setback temperature in the model as the design setpoint is 74F and the setback is assumed to be 5F higher than the design.
Strangely, the opposite behavior where the building uses the regular operating hours for everyday of the week (reduced schedule for weekends is missing) is also observed at times. There seems to be an issue with the priority being assigned to the schedules in the translation to OpenStudio
Some of the (7) Sample_gbXML_Files produced different conditioned EUIs because of different conditioned areas (total area and total energy are the same). The difference is due to which thermal zone has Ideal Air Loads.
Additional Issues
(1) The models end up with only one thermal zone with Ideal Air Loads, which is not the one with setpoint schedules (see image below), and (2) the models are missing HVAC systems. Will investigate these further and open separate issue(s).
Issues
gbXMLStandard Test Model 2016.xml
has weekday/end schedules, which shows the issue definitively. As a fix, these should follow the occupancy schedules.gbxml-to-openstudio/measures/advanced_import_gbxml/resources/os_lib_adv_import.rb
Lines 242 to 248 in 2f19a4a
Improvements
The text was updated successfully, but these errors were encountered: