Integrated Workflow Aragog-Honeybee-Butterfly

[mdengusiak]

@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:

1. Wall Below Grade
2. Air - is like null sruface allow air to travel between zones
   • if SurfaceType is Air - can we remove this from Radiance?
3. rooflight
4. curtain panels
5. opaque windows
6. solid and opaque doors internal/extrnal
7. we need to be able to apply different material to different shade elements ie. external shade, desk, suspended ceiling...we could import as shade but would be amazing if we could read material fro gbXML so when I set up different reflectance will be picked up

@theo-armour

1. this file is already fixed but we need to allow users to chage Surface Type by CADObject Groups... so if we select whole CADObejct Group we can change type for all surfaces in this group
2. how can we control windows, doors to be transparent/ opaque

LondonOffice_ver01.zip

[chriswmackey]

Thanks @mdengusiak , I'll check the file when I get the chance.

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.

[mdengusiak]

@chriswmackey

1. below-grade walls - OpenStudio to fix , Agreed, did you log issues with them?
2. "Air " - yes adjustment to code is needed here, this would allow us simulation daylight atriums etc... "Air " acts as a thermal zone boundary for EnergyPlus, but is ignored by Radiance. I guess this is first thing we should try to solve
3. Yes, spandrel panel I guess need to explain how revit works...will try to prepare few cases with different curtain wall set up
4. Doors, we need to use doors in revit.. hmmm I would recommend that we replace in your import step doors into solid walls with name from Door: just use CADObjectID without element ID part so in this example would be Doors_ver01: SIM_INT_SLD, so we can apply correct Uvalue... to different doors

[chriswmackey]

@mdengusiak ,

1. Yes I logged the issue with OpenStudio team here: https://github.com/NREL/OpenStudio/issues/3121
2. Can you upload a gbXML file that has air walls within it? I don't know how/if gbXML has a specific tag for air walls but I know EnergyPlus/OpenStudio does not have a specific surface type for air walls so it may be up to us to recognize them and assign correct parameters from Honeybee.
3. Is there a special gbXML surface type for spandrel? Or do you just define spandrel panels the same way that you would an opaque wall? Again, as you said, and example file would be helpful.
4. I think we can probably treat doors as normal HBSurfaces but our ability to do this will depend on how OpenStudio imports the doors from the gbXML. If all of the coordinate info of the door makes it into OpenStudio file, we should have no issue.

[mdengusiak]

@chriswmackey

1. excellent, thanks I can see they have infrastructure in place

2. File is uploaded in first post above LondonOffice_ver01.zip see surfaces as Type - Air I think there is Air-Wall material in OpenStudio but we could assign this in Honeybee Here is reference from Forum link

3. these two panels are solid...but from name...so I call them in Revit Solid panels in order for gbXML to export as seperate panels...it is required in revit to make them transparent

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 summary is: we prefer to use method above to make sure that panels are exported from revit correctly

I attached here aslo file LondonOffice_ver02 with second option I describe... LondonOffice_TwoCases.zip

4. Doors exist in Openstudio I can see type and also materials, we have internal and external solid and transparent. If "Surface type" field is set to "GlassDoor". Then it will allow you to use transparent materials. If you use the "Door" type, you can only assign opaque materials to it.

[mdengusiak]

@chriswmackey

Did you have a chance to look at my file and think about solution how to solve -air type in radiance?

[chriswmackey]

I'm sorry @mdengusiak , I have not yet gotten the chance to look at it and I'm about 2 weeks behind on checking the github and forum. Hopefully, once I get back from this workshop, I'll have some time and I'll try to address the air walls.

[mdengusiak]

@chriswmackey this sounds great, thanks a lot this would be great step. With current Rad Viewer would be amazing stuff to test

[theo-armour]

@chriswmackey @mdengusiak

Whenever you get there, we can map bitmaps and even videos of bitmaps to any and all surfaces

Rad Viewer Bitmap Read Me

[mdengusiak]

@chriswmackey Hi did you have a chance to look and address the air walls?

[chriswmackey]

@mdengusiak ,

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: https://github.com/NREL/OpenStudio/issues/3121

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:

• Honeybee Legacy will never support doors unless someone else is motivated to add them in. Mostapha and I aren't planning to add them until HB+
• E+ context surfaces do not support the assigning of reflectance values (only transmittance).
• Pulling off RadMaterials from the reflectance of E+ surfaces is definitely something that we can do.

[chriswmackey]

@mdengusiak ,

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.

[michaldengusiak]

@chriswmackey thanks

[chriswmackey]

@mdengusiak ,

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: https://drive.google.com/file/d/11-xr8UQ7GvQvUTb9-kP1JUYjHxjiSgn2/view?usp=sharing

Alternatively, if anyone has some thoughts on the code that is in there to bring in Air Walls, I am all ears.