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

Revision history [back]

How to efficiently use OpenStudio for parametric analysis?

I am struggling on how to use OpenStudio and PAT to analyze energy efficiency measures coming from eQuest.

For example, I want to run a daylighting measure combined with adding skylights to a warehouse building. In eQuest, I can add a "whole building measure" in the wizard, and add the skylights and daylighting controls to the model. In OpenStudio, I believe the only way to run this measure would be to manually add in the skylights as a different model

Another example, I want to run a measure for electrification of gas-fired unit heaters and replace them with electric unit heaters. In equest this is simple to add a measure to replace the fuel type to electricity. In OpenStudio, I would need to make a secondary model with electric unit heaters.

Am I missing something with my assumptions above? I realize that OpenStudio has a lot of advantages in terms of automating analysis, but writing measures in Ruby for all the measures not covered in the BCL seems like a big hurdle. I am hoping I am wrong, because I want to work to move my organization to use OpenStudio instead of eQuest, but I think this may limit my ability to get engineers to adopt it.

How to efficiently use OpenStudio for parametric analysis?

I am struggling on how to use OpenStudio and PAT to analyze energy efficiency measures coming from eQuest.

For example, I want to run a daylighting measure combined with adding skylights to a warehouse building. In eQuest, I can add a "whole building measure" in the wizard, and add the skylights and daylighting controls to the model. In OpenStudio, I believe the only way to run this measure would be to manually add in the skylights as a different model

Another example, I want to run a measure for electrification of gas-fired unit heaters and replace them with electric unit heaters. In equest this is simple to add a measure to replace the fuel type to electricity. In OpenStudio, I would need to make a secondary model with electric unit heaters.

Am I missing something with my assumptions above? I realize that OpenStudio has a lot of advantages in terms of automating analysis, but writing measures in Ruby for all the measures not covered in the BCL seems like a big hurdle. I am hoping I am wrong, because I want to work to move my organization to use OpenStudio instead of eQuest, but I think this may limit my ability to get engineers to adopt it.