Revision history [back]

Hi everyone

I have a workflow question about the Python EMS workflow. I noticed that after working on Python plugin file, we still need to declare variables in EP+ .idf file, such as PythonPlugin:**** . If the workflow starts from OpenStuido, each time a new EP+.idf would generated by OpenStudio. That means we need to manually change the .idf to build the interface with Python Plugins? One possible alternative way is to use EP+ measure in OpenStudio to automate this step. Does this suggest each Python Plugin need a measure file? I also notice the epJSON Input Schema available in API 0.2. Could we use this to create something similar as EP+ measure?

For Python as library in EP+, I have a similar question. If we want to work with control algorithm and need to manipulate the sensors/actuators, we still have to add these sensors/actuators as we did with Erl? or write measures?

I just feel this workflow might be optimized somewhere.

Thanks

Wei

Hi everyone

I have a workflow question about the Python EMS workflow. EMS. I noticed that after working on Python plugin file, we still need to declare variables in EP+ .idf file, such as PythonPlugin:**** . If the workflow starts from OpenStuido, each time a new EP+.idf would generated by OpenStudio. That means we need to manually change the .idf to build the interface with Python Plugins? One possible alternative way is to use EP+ measure in OpenStudio to automate this step. Does this suggest each Python Plugin need a measure file? I also notice the epJSON Input Schema available in API 0.2. Could we use this to create something similar as EP+ measure?

For Python as library in EP+, I have a similar question. If we want to work with control algorithm and need to manipulate the sensors/actuators, we still have to add these sensors/actuators as we did with Erl? or write measures?

I just feel this workflow might be optimized somewhere.

Thanks

Wei Wei

Hi everyone

I have a workflow question about the Python EMS. I noticed that after working on Python plugin file, we still need to declare variables in EP+ .idf file, such as PythonPlugin:**** . If the workflow starts from OpenStuido, each time a new EP+.idf would be generated by OpenStudio. That means we need to manually change the .idf to build the interface with Python Plugins? One possible alternative way is to use EP+ measure in OpenStudio to automate this step. Does this suggest each Python Plugin need a measure file? I also notice the epJSON Input Schema available in API 0.2. Could we use this to create something similar as EP+ measure?

For Python as library in EP+, I have a similar question. If we want to work with control algorithm and need to manipulate the sensors/actuators, we still have to add these sensors/actuators as we did with Erl? or write measures?

I just feel this workflow might be optimized somewhere.

Thanks

Wei

Hi everyone

I have a workflow question about the Python EMS. I noticed that after working on Python plugin file, we still need to declare variables in EP+ .idf file, such as PythonPlugin:**** . If the workflow starts from OpenStuido, each time a new EP+.idf would be generated by OpenStudio. That means we need to manually change the .idf to build the interface with Python Plugins? One possible alternative way is to use EP+ measure in OpenStudio to automate this step. Does this suggest each Python Plugin need a measure file? I also notice the epJSON Input Schema available in API 0.2. Could we use this to create something similar as EP+ measure?

For Python as library in EP+, I have a similar question. If we want to work with control algorithm and need to manipulate the sensors/actuators, we still have to add these sensors/actuators as we did with Erl? or write measures?

I just feel this workflow might be optimized somewhere.

Thanks

Wei