[WIP] is there a way to save fully specified honeybee thermal zones in a component for reuse?

May I ask if there is a way to save the honeybee thermal zones with adjacency solved, which may take a long time for large model, zone program, loads, etc., all defined so as to save the time to open the file next time or reuse it for different workflow?

Thanks!

Replies are closed for this discussion.

Replies to This Discussion

Permalink Reply by Mostapha Sadeghipour Roudsari on February 5, 2016 at 8:11pm

Hi Grasshope,

I have been thinking about this and was waiting for someone to ask for it so I go ahead and implement it. Interesting that no one ever asked about this!

Check the attached file. There are two components that let you dump the objects to a file and load them back from the file. In this case once you have a large model already worked out you can save it and next time load it from the file. I have tested it for small models but let me know how it will work on a large model.

Attachments:

dumpObjects.gh, 469 KB

Permalink Reply by Theodoros Galanos on February 5, 2016 at 8:27pm

Wow this is amazing! Can't wait to test it out!

Mostapha could we use these for parametric optimizations? Put it right after the part that won't change anymore so that the whole chain won't be re-run/re-read? Perhaps there's no need, I'll test it out soon!

Kind regards,

Theodore.

Permalink Reply by Grasshope on February 5, 2016 at 10:43pm

Thank you very much, Mostapha!

These two component are very handy and they shall increase the efficiency of energy modeling workflow significantly which involves intensive thermal zone geometry preparation calculation!

Permalink Reply by Grasshope on February 6, 2016 at 8:16am

Hi Mostapha, I found the following problem with the 2 components:

1. use the 1st component to save the .HB file

2. disable the write HB file component

3. save the GH file, close and reopen GH and Rhino, then open the GH file again,

4. the .HB file cannot be loaded by the 2nd component

it seems that the Load component only works when the write component is activated.

Appreciate if you can kindly check if you can duplicate the error.

Thanks!

Permalink Reply by Mostapha Sadeghipour Roudsari on February 6, 2016 at 11:03am

Ah! I see where the problem is. I over-simplified the issue last night. It can be actually pretty hard as cPickle has limitations on de-serializing. Let me think about it more.

PS: You may want to change the topic to "[Maybe] is there..." until I get this fix! ;)

Permalink Reply by Mostapha Sadeghipour Roudsari on February 12, 2016 at 11:19pm

Hi Grasshope and Theodore. Let's see if I get it right this time!

PS: Grasshope please also consider these component as a gratitude to your recent post.

Attachments:

dumpObjects_001.gh, 481 KB

Permalink Reply by Grasshope on February 13, 2016 at 11:34pm

Dear Mostapha, thank you very much!

Apologize for my late replay as I was rushing a conference paper in the past few days.

Permalink Reply by Abraham Yezioro on February 14, 2016 at 1:13am

Hi Mostapha,

I tried it and get some trouble.

The process i tried is:

Save/dump the HBZones into a file.

Open a new GH file and uplad the previous saved file.

There i get this : 1. Solution exception:KeyError

Runtime error (KeyNotFoundException): KeyError
Traceback:
line 136, in updateHoneybeeObjects, "<string>"
line 155, in loadHBObjects, "<string>"
line 177, in main, "<string>"
line 180, in script

Is this process supposed to be valid? Or both dump/upload must work inside the same file?

Thanks,

-A.

Permalink Reply by Mostapha Sadeghipour Roudsari on February 14, 2016 at 6:03am

Hi Abraham, This is how it is supposed to work. I can't recreate the error. Can you share your .hb file with me? Thanks.

Permalink Reply by Abraham Yezioro on February 14, 2016 at 6:22am

Sure.

Here it is.

I dumped it after some E+ settings components. Can this be the cause?

-A.

Attachments:

testSaba.HB, 888 KB

Permalink Reply by Mostapha Sadeghipour Roudsari on February 14, 2016 at 8:36am

Thanks Abraham! The issue was with the exporter. Let's try once more.

You'll still get an error since the component doesn't package schedules and construction/materials which we can add later but if the materials are loaded into library then it should work fine.

Once we have that in place, this will open up new opportunities. For instance you can break down the process and have a definition on a different machine waiting for the file to run the calculations while you're working on your model locally. #collaboration #cloud #rain

Attachments: