Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
If by running OpenStudio measures independently of OpenStudio you mean independently of OpenStudio Server, there is always the option of calling the Command Line Interface directly, but you lose the scalability, queue management, and sampling algorithms that come with OpenStudio Server. You would also need to write a script to alter copies of a template OSW to sweep the parameter space. Since the OSW is structured as a JSON file so it can be edited with a custom API.
As an example of a simple OSW parametric run you can look at the BESTEST-GSR repository that we use for our BESTEST workflow. This runs OSW's on multiple cores, and creates a summary CSV from simulation results.
As far as server deployment documentation if you want to give that another try, the wiki on openstudio-sever github page is a good place to look. I will say that the vast majority of users who run algorithmic PAT analyses, use the EC2 functionality built with PAT. You can save internal development time, but then have to pay Amazon for that service.
| | 2 | No.2 Revision |
If by running OpenStudio measures independently of OpenStudio you mean independently of OpenStudio Server, there is always the option of calling the Command Line Interface directly, but you lose the scalability, queue management, and sampling algorithms that come with OpenStudio Server. You would also need to write a script to alter copies of a template OSW to sweep the parameter space. Since the OSW is structured as a JSON file so it can be edited with without a custom API.
As an example of a simple OSW parametric run you can look at the BESTEST-GSR repository that we use for our BESTEST workflow. This runs OSW's on multiple cores, and creates a summary CSV from simulation results.
As far as server deployment documentation if you want to give that another try, the wiki on openstudio-sever github page is a good place to look. I will say that the vast majority of users who run algorithmic PAT analyses, use the EC2 functionality built with PAT. You can save internal development time, but then have to pay Amazon for that service.
| | 3 | No.3 Revision |
If by running OpenStudio measures independently of OpenStudio you mean independently of OpenStudio Server, there is always the option of calling the Command Line Interface directly, but you lose the scalability, queue management, and sampling algorithms that come with OpenStudio Server. You would also need to write a script to alter copies of a template OSW to sweep the parameter space. Since the OSW is structured as a JSON file so it can be edited without a custom API.
As an example of a simple OSW parametric run you can look at the BESTEST-GSR repository that we use for our BESTEST workflow. This runs OSW's on multiple cores, and creates a summary CSV from simulation results.
As far as server deployment documentation if you want to give that another try, the wiki on openstudio-sever github page is a good place to look. I will say that the vast majority of users who run algorithmic PAT analyses, use the EC2 functionality built into with PAT. You can save internal development time, but then have to pay Amazon for that service.
