Revision history [back]

Thank you for your comprehensive response, Mathew. I put my takes here as a new answer. I'll pick your answer as the best answer though. I am using the OpenStudio source code and the following notes are based on that.

1. So, one can still use other languages to write measures as long as proper language bindings are selected in CMake, while configuring and generating OpenStudio. More explanations could be find in here.

2. & 4. The measures use the source codes indirectly through the API and respective language bindings (Ruby, Python, and etc.). However, I'm still not sure what are we referring to as "API". Is the the whole subroutines and modules used for generating the OpenStudio?

3. I am still trying to set up Ruby to try the code provided by Mathew, however, I get some errors shown below that I might put it in a separate question, unless there is any quick comment on that in here.

As Jason and Mathew mentioned, using "gbXMLtoIDF" is still an option (the source code is also available when downloading the OpenStudio source code). However, after considering all options I'd rather go with writing a measure in Ruby and use OSW to automate running all the measures.

Thanks again, guys!

Thank you for your comprehensive response, Mathew. Matthew. I put my takes here as a new answer. I'll pick your answer as the best answer though. I am using the OpenStudio source code and the following notes are based on that.

1. So, one can still use other languages to write measures as long as proper language bindings are selected in CMake, while configuring and generating OpenStudio. More explanations could be find in here.

2. & 4. The measures use the source codes indirectly through the API and respective language bindings (Ruby, Python, and etc.). However, I'm still not sure what are we referring to as "API". Is the the whole subroutines and modules used for generating the OpenStudio?

3. I am still trying to set up Ruby to try the code provided by Mathew, however, I get some errors shown below that I might put it in a separate question, unless there is any quick comment on that in here.

As Jason and Mathew mentioned, using "gbXMLtoIDF" is still an option (the source code is also available when downloading the OpenStudio source code). However, after considering all options I'd rather go with writing a measure in Ruby and use OSW to automate running all the measures.

Thanks again, guys!

Thank you for your comprehensive response, Matthew. I put my takes here as a new answer. I'll pick your answer as the best answer though. I am using the OpenStudio source code and the following notes are based on that.

1. So, one can still use other languages to write measures as long as proper language bindings are selected in CMake, while configuring and generating OpenStudio. More explanations could be find in here.

2. & 4. The measures use the source codes indirectly through the API and respective language bindings (Ruby, Python, and etc.). However, I'm still not sure what are we referring to as "API". Is the the whole subroutines and modules used for generating the OpenStudio?

3. I am still trying to set up Ruby to try the code provided by Mathew, however, I get some errors shown below that I might put it in a separate question, unless there is any quick comment on that in here.

As Jason and Mathew Matthew mentioned, using "gbXMLtoIDF" is still an option (the source code is also available when downloading the OpenStudio source code). However, after considering all options I'd rather go with writing a measure in Ruby and use OSW to automate running all the measures.

Thanks again, guys!