algorithmic modeling for Rhino

gbXML generation problems - using Honeybee and GrizzlyBear

Hi Mostapha, Chien Si and all,


Firstly, I would like to thank Mostapha for your reply and your kind help!


In order to link GH and DesignBuilder, I have being trying to generate the gbXML format from GH models using Honeybee and GrizzlyBear via some simplified building geometries (like indoor stadium and simple boxes), but I encountered some problems showed in the following images.


Could you please let me know how I can solve these problems? I have attached the rhino and gh files I'm using and also left my questions in the files.


Thank you all in advance!



Views: 2645


Replies are closed for this discussion.

Replies to This Discussion

Hi Ding,

Please check the attached file for the newest version of the file. The issues with area and schedule are also solved. Did you ever heard back from DesignBuilder team?



Hi Chris,


Thank you very much for your kind help!

Actually I found this problem by chance and felt a little bit odd, so reported this to you. Thanks again for your work.




Hi Chien,


Thank you so much for fixing GrizzlyBear!


I have just heard back from DesignBuilder team, as you might expect, that the DB gbxml import mechanism are not reading the constructions/schedules data from the xml file at the moment.


However, as my reply above, I was wondering if the gbXML file generated from Honeybee Zones and GrizzlyBear includes(defines) the information regarding these "holes" or "virtual partitions"? In other words, is it possible to automatically generated "holes" or "virtual partitions" (which allow airflow between thermal zones) in DB when importing the gbXML file (generated by Honeybee Zones and GrizzlyBear)?


Alternatively, can we just use Energyplus related components in Honeybee to get each different temperature of the subdivided thermal zones which compose the large thermal zone and allow airflow between them? How to achieve this? (Share surfaces between the subdivided thermal zones should be carefully treated to approximate the situation of airflow through "holes")

Grateful for all your help!




Hi Chien,


Thank you again for your time and your kind help!


In case we have different understandings of the term "air wall", maybe I should make it more clear regarding what I called "air walls" or "virtual partitions" as follows:

What I mean "air walls" here, is derived from the description of the E+ documentation with the header of "Air wall, Open air connection between zones". (Page 17,

As I understand, the term "air wall" used in E+ here refers to a description of something like "boundary condition" between adjacent interzone heat transfer surfaces, but not a kind of "construction or material" (like air space resistance or air gaps within a wall/double glazing window).

The main purpose of introducing the "air wall", is to simulate or approximate the airflow/convection/natural ventilation effect between multiple thermal zones which are connected by a large opening.


In my previous tests, using HBzones and GB, I managed to create the gbXML file which can be successfully imported to DB (without assigning any constructions within HB). And the adjacency condition can be recognized automatically by DB, even when I did not use the "Solve adjacencies" component in HB - shared surfaces between multiple thermal zones are recognized automatically by BD as "internal - partition"(which are standard partitions, but not virtual partitions).

In order to create/approximate "virtual partition", I need to manually draw a "hole" in the standard partition surface (fig.1&2). Again, the reason why we want to use "virtual partitions"(or "air wall") is that it allows airflow between multiple thermal zones which are connected by large openings and we could get different temperature of the each subdivided thermal zone which compose a large thermal zone.


My question is, if there is a possible way to simulate/approximate this kind of "virtual partitions"(or "air wall") in HBzones or in GB? If so, I would like to test if DB recognizes it or not. Actually, we expect that there is no need to involve any manual operations (like drawing a "hole" in the standard partition surface) in DB, due to an automatic optimization loop.


Thank you!






Hi Ding,

I am working on similar approach to produce gbXML form GH. Here is my example that works well in TAS. Can you please test it and import into DesignBuilder and share your image from import.

1. Regarding your post I agree that would be good to have air in the main list... but as far I am aware there is option to assign air construction right now, I manage to do it when wasa using TAS I am applying to each building element correct construction within TAS

2. Also I think that would be good to have two types of floors: groundFloor and ExposedFloor


Hi Ding and Michal,

Ding, As Michal said you can create a hole (e.g. air wall) in Honeybee. Honeybee won't take care of mixing the air between the zones which shouldn't be an issue in your case since you can handle that in DB.

Michal, There is currently 3 different types floor, ground floor and exposed floor. You should get them all correctly. Is it not happening right now?







  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service