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
This is issue is already discussed somewhat as issue 1 in #1395.
In OpenStudio v3.3.0 and above, most 90.1-2016 and 90.1-2019 models will fail at runtime with an error like this:
`Invalid Actuated Component Unique Name =CAFETERIA_ZN_1_FLR_1 ZN PRIMARYSCHOOL CAFETERIA LIGHTS Entered in EnergyManagementSystem:Actuator=CAFETERIA_ZN_1_FLR_1ZN_LIGHT1_ACTUATOR Component Unique key name not found Use Output:EnergyManagementSystem object to create .edd file for valid component names.\
It's from the way EMS actuators are translated in the forward translator from OS to E+. The relevant code is here and here.
Initially, this appeared as an OpenStudio issue. But as I describe in this comment, EnergyPlus is actually right in it's failure, as the code in early versions were actuating the same component.
The issue is that the lights object is defined at the SpaceType level and shared among many spaces / zones. The EMS control needs to operate on one unique lights object per zone/space.
@lymereJ@weilixu I'll take a shot at addressing this and @ you when I've got it refactored within the next day or so.
The text was updated successfully, but these errors were encountered:
This is issue is already discussed somewhat as issue 1 in #1395.
In OpenStudio v3.3.0 and above, most 90.1-2016 and 90.1-2019 models will fail at runtime with an error like this:
`Invalid Actuated Component Unique Name =CAFETERIA_ZN_1_FLR_1 ZN PRIMARYSCHOOL CAFETERIA LIGHTS Entered in EnergyManagementSystem:Actuator=CAFETERIA_ZN_1_FLR_1ZN_LIGHT1_ACTUATOR Component Unique key name not found Use Output:EnergyManagementSystem object to create .edd file for valid component names.\
It's from the way EMS actuators are translated in the forward translator from OS to E+. The relevant code is here and here.
Initially, this appeared as an OpenStudio issue. But as I describe in this comment, EnergyPlus is actually right in it's failure, as the code in early versions were actuating the same component.
The issue is that the lights object is defined at the SpaceType level and shared among many spaces / zones. The EMS control needs to operate on one unique lights object per zone/space.
@lymereJ @weilixu I'll take a shot at addressing this and @ you when I've got it refactored within the next day or so.
The text was updated successfully, but these errors were encountered: