Grasshopper

algorithmic modeling for Rhino

This post is about 10 days overdue, but as they say, better late than never! Also this is two posts in one post. If you're not interested in the news about the new releases scroll down to the end of the post.

10 days ago was the 4th anniversary of the release of the first version of Ladybug and as the title says, I wanted to share with you what 2017 entails for Ladybug Analysis Tools (previously known as Ladybug + Honeybee).

In December 20016 at the AEC Tech Hackathon, I gave a presentation which pretty much covers all I need to write here. I’m copying the links to the videos so you can watch them and I will just highlight the most important topics. Here are the slides that I used for this presentation.

The first major release of 2017 is a new version of the original Ladybug + Honeybee plugins, which will hereafter be referred to as the legacy version of Ladybug Analysis Tools. Now that the plugins have been fully connected to the major open source engines and databases, the majority of changes represent “icing on the cake.” There are a number of new components related to maximizing the visual capabilities of Rhino, including contour map visualizations, components to make rendered animations, texture mapping components for transparent meshes (and connections to VR programs), and stereographic sky projections. Furthermore, the last of the thermal comfort models for local discomfort (drafts and radiant asymmetry) have been incorporated along with components that help calculate discomfort from given geometric and thermal criteria (a simplified downdraft model and a view factor component). There have been a few extensions of OpenStudio/E+ capabilities to get out HVAC system sizing results and to request/search through the hundreds of outputs that E+ offers. Finally, there are a few workflow improvements, including changes to use less memory when building large energy models and a workflow to import HBZones from gbXML. Chris has been leading the development for the legacy version during the last year or so and he deserves all the credits. There is no way to thank him enough for what he does on a daily basis. I can only say that we are all so lucky to have him around!

After the release of the legacy plugin, the next major release of 2017 will be the public release of Butterfly, which is already long overdue. If you are watching the project on GitHub, you should already know that we are very close and are trying to make the final improvements before the release. The release will have its own separate release notes. For now, I want to thank Theodore Galanos and everyone who helped us with their suggestions during the development process. There would be no Butterfly if it wasn’t for Theodore.

Butterfly’s release will be followed by the release of Honeybee[+]. The first release of Honeybee[+] supports most of the functionalities in the current version of Honeybee for daylight simulation plus it addresses many of the current limitations for annual daylight modeling by using Radiance 3-phase method. It should also support Grasshopper both on Windows and Mac as well as Dynamo. There is much more about Honeybee[+] which again will be included in a separate post. I want to thank Sarith Subramaniam and everyone who helped us with testing the code during the development. Honeybee[+] won’t have most of its features if it wasn’t for Sarith.

I also want to thank everyone on the forum who helps other users with questions and solutions. That’s how I and the rest of the developers get the time to focus on the new developments. Yet I didn’t get a chance to update the graph for this year but you know who you are. Thank you!

Finally, I am posting a modified draft from last year February. Chris and I drafted this post last year but never posted it as I was waiting for the “right time” to post it. The “right time” would be when we have free time to answer all the questions but that time seems not to come! We will do our best to reply to your comments as much as we can. Here is that post:

----

Even though we receive comments and ideas from many of you on a daily basis Tim's recent comment [it was recent at the time!] made me think that we should, once more, explicitly ask for your comments while developing the new version of Ladybug (and at some point Honeybee), and also collect the ongoing ones in a single place.

So post your comments, suggestions and wishes here and let us know what can we do to make Ladybug and Honeybee better. Any type of comments are welcome as far as you tell us why you think it is important. Here are a couple of questions to get you started:

- What is currently missing? Why do you think that missing feature is important?

- If you could only change one thing, what would it be and why?

- What do you like the most about Ladybug + Honeybee that you don't want to change in the new release?

- What kind of bottlenecks do you run into? - What have you done with Ladybug + Honeybee that you think it should/could have been done much simpler if we could have made a couple of changes?

- What do you think will be essential/missing from Ladybug for Dynamo?

- ...

Your turn! Let us know your thoughts!

Views: 3064

Replies are closed for this discussion.

Replies to This Discussion

Will do! I was not aware of the new components! This is a reminder to me that a "Pulse" project can be really helpful to be able to keep track of changes like this. Thanks for the clarification.

Thankyou very Mostapha for posting the news yet to come and for the all good work the whole team you've been doing (personally I have to specially thanks to Chris Mackey for helping me in this forum with some issues!). Ladybug + Honeybee have become part of the essentials tools I use in everyday work.

I agree with Aurelien Keller that it would be nice if some ventilation and lighting components had some more information about how to use them. I'm starting to use these components and I find quite difficult sometimes! 

happy 4th birthday!

Mostapha, Chris and all,

Happy ladybug+honeybee anniversary. Thank you all for this great effort, happy to know about using VR connection with LB+HB.  I'm very lucky to be a part of this motivating & inspiring forum, I learnt a lot from you and you are motivating me to work harder to follow the Lb+Hb updates.   

for my small wish list :)   

- I wish that some of the simulations take less time, especially radiation analysis & comfort shade benefit evaluator, as I tried many v.good PCs to run them but it was difficult and the building was too simple to have all that time.   

- for large scale & high rise buildings, I wish that we can have a simpler way to define them in HB, as I should build every zone as surfaces " walls, floors, ceiling " so I can have a thermal zone and get my results without errors. I know that's the right way to define the zone but it takes time, especially in the final performance evaluation of the building with all of its details.   

- Recently, I was working on a large scale building consists of 4 stories with different design plans, but fortunately, I had a building block to copy and mirror and I found the Hbmirror & Hbmove very useful. I used it to move and mirror that block with many thermal zones which are moved with its names & I had some errors, I'm not sure that I used it in the right way. But I wish that there's a tool can help me copy or mirror thermal zones with its properties to make the process of defining the building's zones easier.   

wish you all success, happiness & the best,

Mona   

RSS

About

Translate

Search

© 2019   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service