First time here? Check out the Help page!
1 | initial version |
The OpenStudio CLI allows you to take a user specified seed model and weather file, and string together one or more measures.
There are a number of example workflows, but here is one I've used recently that has some different model articulation workflows that pull measures from other code repositories. You can checkout this repository and others mentioned in the readme file.
I'll update this answer with information about why the OpenStudio Application is being unresponsive for you.
2 | No.2 Revision |
The OpenStudio CLI allows you to take a user specified seed model and weather file, and string together one or more measures.
There are a number of example workflows, but here is one I've used recently that has some different model articulation workflows that pull measures from other code repositories. You can checkout this repository and others mentioned in the readme file.
I'll update this answer Updated Answer regarding apply measure now responsiveness:
It seems like most of the time is due to forward translation of the model that occurs to pass workspace (IDF) to the arguments section of the measures. Forward translation has validation performance that is non-linear related to model size. I would also point out that with information about why the OpenStudio Application is being unresponsive a model of 1300 zones and 13,000 spaces you may want to try to by script as much as possible and avoid GUI's. The space tab and surfaces sub tab would almost certainly not perform or perform well with this model. Another question to ask is to confirm that the level of detail of the model is appropriate for you.
3 | No.3 Revision |
The OpenStudio CLI allows you to take a user specified seed model and weather file, and string together one or more measures.
There are a number of example workflows, but here is one I've used recently that has some different model articulation workflows that pull measures from other code repositories. You can checkout this repository and others mentioned in the readme file.
Updated Answer regarding apply measure now responsiveness:
It seems like most of the time is due to forward translation of the model that occurs to pass workspace (IDF) to the arguments section of the measures. Forward translation has validation performance that is non-linear related to model size. I would also point out that with a model of 1300 zones and 13,000 spaces you may want to try to by script as much as possible and avoid GUI's. The space tab and surfaces sub tab would almost certainly not perform or perform well with this model. Another question to ask is to confirm that the level of detail of the model is appropriate for the use case. Are there this many zones because there is a need for the energy model simulation, or did it for example just come in from an architectural model that had this level of detail? I would expect the runtime in EnergyPlus to also be very long, not sure if you have done test runs yet?