-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrated Workflow Aragog-Honeybee-Butterfly #112
Comments
Thanks @mdengusiak , For the below-grade walls, the best way to address this would be to wait for OpenStudio to fix the bug. For air walls, I can probably get to to work now but it will need some development. Let me see how it imports. I'd expect skylights and curtainwalls to work with the current implentatiom but I will check. What is an opaque window? Do you mean a spandrel panel? Those should justbe modeled as opaque surfaces with a poor R-value. Door objects are not implemented in Honeybee and we typically recommend people model them as normal opaque wall surfaces with a door construction. I'll see if we can get this conversion to happen with gbXML. Different materials for shade surfaces should already be implemented but I will check. |
|
however if we make them opaque they become part of wall and take over details from solid Curtain wall there they belowg. This is OK when we have ONE type of solid panels in curtain wall but when we have two or more we need to make them transparent to gbXML keep panels as different types SolidPanel1, SolidPanel2.... this is a bit cofusing... but can explain via call in more details I attached here aslo file
|
Did you have a chance to look at my file and think about solution how to solve -air type in radiance? |
I'm sorry @mdengusiak , |
@chriswmackey |
Whenever you get there, we can map bitmaps and even videos of bitmaps to any and all surfaces Rad Viewer Bitmap Read Me |
@chriswmackey |
Looking back at this issue, I think we dumped way too many issues into one such that I now have a really hard time understanding what we were trying to do here. The below-grade bug has been fixed as OpenStudio team notes here: I am going to address the air wall capabilities and then close out of this issue. If you want to discuss some other things, we can open another issue here. A few final things to note:
|
I apologize that it has taken so long for me to test this. All of my attempts to import the air walls have resulted in a successful import when I compile the code from the Grasshopper python editor but a full crash of Rhino when I don't have it compiled this way (essentially, how every user will run the component). There is something about this gbXML import that creates odd race conditions or stack overflows or something like that. I may test it on a different system and see if I get the same result. |
@chriswmackey thanks |
I think that I may have to give up on this one. I have been trying to avoid a full crash of Rhino for the last 3 hours and it seems I can't find any way of bringing in the air walls that avoids this crash. If anyone is able to get this grasshopper script to run with the london-office.xml and does not experience a crash of Rhino, please let me know: Alternatively, if anyone has some thoughts on the code that is in there to bring in Air Walls, I am all ears. |
@chriswmackey @theo-armour
thanks for amazing team work.... and lets try to build on this :)
I prepared for you file with all cases.
Would be good to test workflow on this example and log all issues with Openstudio, Radiace, Openfaom etc,
@chriswmackey
I would like to confirm that we covered and elements works as epxected:
@theo-armour
LondonOffice_ver01.zip
The text was updated successfully, but these errors were encountered: