Grasshopper

algorithmic modeling for Rhino

Hello,

I am working on an energy model in HoneyBee and I to use specific materials which I didnt find in the Energy plus Library. I followed Chris' tutorial 18 - Honeybee Energy Modeling - Constructions Part 4: Making Custom Materials but it is giving me the following error:

1. layer_1 is not a valid material name/definition.
Create the material first and try again.

I attach an image where you can see how i have it set up.

Thank you! 

Views: 1047

Attachments:

Replies to This Discussion

Hi Blanca.

I am sorry for getting back so late.  I have not been able to replicate your error on my system and it is working fine for me:

Can you upload your grasshopper file and I can take a look at it to see what is the problem?

-Chris

Hi Chris,

I even tried on a completely new file, just creating the material and the same error happened.

Thanks!

Attachments:

Hi Blanca,

It looks like the ability to plug a full material text string into the EPConstruction component was something that we added just after the last stable release.  If you use the Honeybee_Update Honeybee and Ladybug_Update Ladybug components to sync your grasshopper components with the most recent version on the LB+HB github, you will find that your file will work correctly with these updated components (see attached for a working GH file).

The protocol before we added this feature was that you had to plug the material into the AddToEnergyPlusLibrary component and connect the name of the new material to the EPConstruction component.  This old method will work for you if you do not want to upgrade the the version on the github and want to continue using the last stable release.

Hope that helps,

-Chris

Attachments:

Thank you Chris! I used the "old" protocol, bc if I updated LB +HB to the most recent version it said there was an error in my WWR Script! Have the whole model working now though

Thanks!!

Glad it worked out. To clarify about updating, the updateThisFile input on the UpdateHoneybee component only works for updating components on your canvass where the names of the inputs and outputs have not changed between versions.  Otherwise, you need to replace the component manually.  This is probably why your WWR component was not working.

RSS

About

Translate

Search

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service