Testing a list of options using Honeybee / E+

Hi all,

I'm trying to test a bunch of different geometry options (different window to wall ratios, etc) in Honeybee and E+ for daylight factor, energy performance, etcetera.

However when I want to input a list of options - say 0.2, 0.4 and 0.6 WWR - See attachment - for the South Facade I only get one result, as the glazingCreator component only creates one surface, and the runDaylightAnalysis component combines all the inputs into one geometry for testing.

There a few ways around it:

Do an optimisation study using Galapagos
Make a list of input options and iterate with Anemone, or Hoopsnake

But they all don't exactly do what I want and can be quite a bit of hassle. Is there an easier way to do it?

Attachments:

Screenshot_WWR_options.png, 230 KB

Replies are closed for this discussion.

Replies to This Discussion

Permalink Reply by Örn Erlendsson on October 23, 2014 at 11:13am

Hi Chris and Mostapha, sorry for the late reply. I've been busy at work. I tried connecting the "WriteRAD" and "RunRAD" to the same boolean toggle as you suggested, and that seems to work. Thanks!

Brute Force seems to require more than one slider as an input, while runItAll only requires one slider to run, so in that case RunItAll is better for this particular case. :)

It always great to see how quickly you respond! Thank you for that. Looking forward to the next update!

Permalink Reply by Örn Erlendsson on August 28, 2015 at 3:23am

Hi Chris and Mostapha!

Where are we on the matter of including the runItAll component in Honeybee as Mostapha sugested in his reply?

I am currently writing a method document for my office and in one of the chapters I describe the process of running multiple iterations. I would really like to be able to include the runItAll compoment.

I know that TT Toolbox's Brute Force does the same thing. There is however an issue with the Brute force component since it requires at least two sliders while your runItAll component allows for just one slider, which is why I prefer it over TTT.

I actually use the runItAll component quite a lot in my projects.

Permalink Reply by Mostapha Sadeghipour Roudsari on August 28, 2015 at 3:39am

Hi Orn. Haven't made so much progress but these two links might help: https://github.com/mostaphaRoudsari/ladybug/issues/95#issuecomment-...

Permalink Reply by Örn Erlendsson on August 28, 2015 at 6:25am

Thanks Mostapha! I will look into that :)

Permalink Reply by Mostapha Sadeghipour Roudsari on October 25, 2014 at 9:59pm

Hi Orn,

I'm not sure why Brute Force doesn't work with a single slider. Probably because you can animate a single slider.

In any case to write a runAll component shouldn't be that hard and I added it to Ladybug issues (https://github.com/mostaphaRoudsari/ladybug/issues/95) so we can address it at some point.

Mostapha

Permalink Reply by Örn Erlendsson on October 31, 2014 at 5:22am

Hi Mostapha,

That's great news! Thank you.

Permalink Reply by Theodoros Galanos on February 9, 2015 at 4:44am

Hi Chris,

Is it easy to go over the file for me? I'm very interested in performing such an evaluation and even though I can understand the geometry part, the glazing part is hard to decipher.

What do the labels 'connect before' and 'connect after' the simulation mean? Is there a specific way of doing the simulation (i.e. steps)? Thank you very much in advance!

Kind regards,

Theodore.