Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Python EMS actuators

Hello,

I am familiarizing myself and playing around with the Python EMS API and using E+ as a library. I am comfortable with the workflow and API itself - I am using this for RL algorithms. I have successfully been able to play around with calling various sensor values using DataExchange and .rdd file with Output:Variable's.

However, I have been having trouble understanding how to implement actuators. Getting an actuator's handle is a bit more complicated. My .idf does not contain any EMS actuators so I am trying to define an arbitrary HVAC actuator object(s) myself, however, I do not understand how to do this well enough - I do not know how to find/implement the various required actuator fields (I have not found documentation explaining the 'syntax' of IDFs, it's still a bit ambiguous how the naming convention and fields work). Likewise, I am confused by the arguments required for getting an actuator's handle for the API: component type (category), control type (name), and actuator key (instance).

Any help would be appreciated.

Python EMS actuators

Hello,

I am familiarizing myself and playing around with the Python EMS API and using E+ as a library. I am comfortable with the workflow and API itself - I am using this for RL algorithms. I have successfully been able to play around with calling various sensor values using DataExchange and .rdd file with Output:Variable's.

However, I have been having trouble understanding how to implement actuators. Getting an actuator's handle is a bit more complicated. My .idf does not contain any EMS actuators so I am trying to define an arbitrary HVAC actuator object(s) myself, however, I do not understand how to do this well enough - I do not know how to find/implement the various required actuator fields (I have not found documentation explaining the 'syntax' of IDFs, it's still a bit ambiguous how the naming convention and fields work). Likewise, I am confused by the arguments required for getting an actuator's handle for the API: component type (category), control type (name), and actuator key (instance).

Any help would be appreciated.