You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that I see how easy it is to write EnergyPlus measures, we should definitely convert the whole class of nonOSFeatures in the OpenStudio component into EnergyPlus measures. This will allow the instructions for writing additional features to be carried over into the resulting OpenStudio model. This will also open up whole new workflows that start in Honeybee and end by editing things in OpenStudio (creating custom HVAC in OS, for example). Finally, I am realizing from work experience that this will make things much easier to coordinate between architects working in Honeybee and engineers that are using OpenStudio. If I can get this implemented, I'd say we've finally built a strong bridge to OpenStudio on the Legacy version of Honeybee and I can lay down my keyboard for a bit.
The text was updated successfully, but these errors were encountered:
I started doing this as you can see from the measures that I have written here: https://github.com/mostaphaRoudsari/honeybee/tree/master/resources/measures
However, I have realized that there are some downsides to going with this route at the moment and so I'm going to save the full implementation of this for HB+. If anyone wants to start tackling the measure-writing process, though, this will be useful no matter the version of HB that anyone is using.
Now that I see how easy it is to write EnergyPlus measures, we should definitely convert the whole class of nonOSFeatures in the OpenStudio component into EnergyPlus measures. This will allow the instructions for writing additional features to be carried over into the resulting OpenStudio model. This will also open up whole new workflows that start in Honeybee and end by editing things in OpenStudio (creating custom HVAC in OS, for example). Finally, I am realizing from work experience that this will make things much easier to coordinate between architects working in Honeybee and engineers that are using OpenStudio. If I can get this implemented, I'd say we've finally built a strong bridge to OpenStudio on the Legacy version of Honeybee and I can lay down my keyboard for a bit.
The text was updated successfully, but these errors were encountered: