Is there a way to input a shade control schedule into DIVA for grasshopper? DIVA for rhino has built in shade controls but I can't seem to find that for the grasshopper version.
It would be great to be able to input a custom shade schedule. That would allow me to control the shades with a simple direct sun estimation or any custom schedule to fit the project. Heavy annual glare calcs take too long for what I need. In the end, I want to run a single DIVA-GH calc of UDI, DA etc. that accounts for basic internal shades. Does anyone know of a way?
Thanks in advance.
here's a possible workaround to implement a simple dynamic shading system in Diva-for-Grasshopper. However, it requires post processing to generate new Daysim coefficients files.
I haven't tried to adjust the Daysim coefficient files before but will look into it. I am worried about the command that Alstan recommended running (gen_dc *.hea -paste) because I don't know how I would do that in the grasshopper environment.
What do you think about this solution for an all grasshopper workflow:
- run two climate based DIVA runs, one with shades, one without.
- Bring in both .ill data sets using the TT Toolbox Excel reader node.
- Create a shade schedule using the solar vector. This can be set up to close shades if the sun penetrates more than a critical depth into the space. Or a zero bounce DIVA run could be calculated at a single point located at a critical depth into the space.
- Cull opposite parts of .ill data sets using the shade schedule to get a shades up hourly data set and a shades down hourly data set.
- combine culled data sets and analyze
This seems excessive but it should work entirely within grasshopper, which is nice. What do you think? Are there ways to speed this up while staying in grasshopper? Do you have any recommendations on the shade schedule to improve accuracy?
the procedure explained in that post in mostly done outside Grasshopper, running Daysim simulations on modified *.dc files and then using a script (e.g. in Matlab) to combine the *.ill files.
Your workflow seems fine to deal with with small data sets. However, I am not sure that the solar angle is an enough accurate method to define a blind schedule. Also it can be problematic when more windows/orientations are included. Lightswitch 2002 uses 50 W/m2 ‘hitting workplane’ as blind trigger. Here there are some other references.
I hope this help.
Thanks for the references. I think I will stay within grasshopper for now but I might need to try your method if the data sets get too large for GH. Our direct sun penetration studies can calculate when direct sun hits critical areas so I feel okay about using that as a rough shade schedule but I'll need to adjust for users leaving the shades down, as your references suggest.
I appreciate your input.