Hi Everyone. Started testing the new plugins of Honeybee. I ran the 1st simulation single-family energy model and was successful with the generation of results with my timezone weather files.
Comparing to Honeybee Legacy: Export to OS component, The new HB to OS model doesn’t have an input to open studio application. That functionality in legacy was super useful while understanding the HVAC components graphically on OS application. Is it deliberately removed?
Or am I missing a component that is present in the new library that I should explore for that?
Hi @Asisnath, the new Honeybee ships with OpenStudioSDK only, which doesn’t include the OpenStudioApp (this has been separated from NREL’s OpenStudio project).
OpenStudioApp is not required for user to run energy model from Honeybee, so this “HB to OS model” component doesn’t have “openOpenStudio” input. But I agree that it is really helpful to use it for checking HVAC systems.
Another thing that is worth noting is some measures and “add_str_” won’t be translated into osm file, which would cause some confusions when getting different simulation results from OpenStudioApp than what’s from Grasshopper Honeybee.
But, maybe it is worth to add a separate component like “OpenOpenStudio” for checking purpose.
Hello @MingboPeng. I agree to you that now OS is divided into 2 part one Sdk and one OS app. Currently I have installed both of them. I think if we can have a component that can access the OS file created from OS Sdk when we write it before running and visualise it with a component that opens OS app provided the OS application is installed.
Hey @Asisnath ,
Sorry for the late response here and thank you for raising this question as it’s been something that I have been thinking about and I believe that I have a much more elegant and reusable strategy compared to legacy. I just added two new utility components to the Ladybug Extra tab that handle the opening of files and directories, which you can get on your machine by running the “LB Versioner” component. After you restart Grasshopper you will find here (circled in red):
One of them opens the directory where any file is located (in either Windows Explorer or Mac Finder depending on your operating system). The other opens files in whatever application is associated with the file extension. So, if you have associated .osm files with the OpenStudio application on your machine, they will open there. If you have .idf files associated with the IDF Editor, they will open there. And so on. Here’s a video showing how the components are intended to work:
This way, the components can work however you set up your file associations on your machine (if there are multiple programs that can open a given file type) and it can be used for many more file types beyond .osm.
On a tangential note, after OpenStudio 3.0, this is the location where you should get the latest OpenStudio Application (if you didn’t know it already):
As Mingbo says, we aren’t planning to make the installation of the OS application an official part of the install process but hopefully those components are flexible enough to satisfy your needs.
2 Likes
@chris Thanks you for this add on. It was really needed to continue with our way of doing simulation as we were doing in legacy version. Much appriciated. As you have mentioned I can see OS has released a newer version for support to OS sdk 3.0.1. Thank you again for this update.