Dear @mikkel,
Thank you for the Grasshopper script. I would like to ask you a question if it is possible. Regarding the usage of sky vector instead of sky metric, in what way I can read the DGP values for all the test points at certain hour on a certain day. As you can see in the attached image, the reading component shows “1. Solution exception:invalid literal for float(): -nan(ind)”.
Thank you very much.
Best regards.
Hi @Clarence,
If you run the recipe with a point-in-time sky vector, the reading component is not useful, but if you only care about the DGP values you can find them in the file called views..scene..default.dgp.
Hi @mikkel,
Sorry for the late reply. I understand now. I am facing another issue about how to combine a dynamic shading schedule in the imageless glare simulation. I have several shading panels and their annual shading schedules but I am not sure how to include them in the simulation.
Sorry for bothering you again and I am looking forward to your reply.
Thank you very much.
Best regards.
Hi @Clarence,
Since the recipe only works for static models, you have to run it multiple times with different models to get the results of dynamic shadings. You would then have to combine the raw results yourself for all the different simulations based on your schedule.
Very nice recipe. Thanks!
But I got one error message from below. Any idea?
I have the file named below
Hi @YD,
The error message suggests that the files are not in the right place. If you did follow the instructions in this post I am not sure why you get that error.
It seems like you have run a simulation? Your folder is polluted with the results, but I would suggest not to put anything in this folder besides __init__.py and gridbased.py.
Hi @mikkel,
I got it now and I will try this method! Thank you very much 
Best regards.
Clarence Wang
Hi Mikkel,
thank you for your reply. It works now when only two files in the folder.
And does the number higher (blue color) means better? How do we change analysis period?
Hi @YD,
Yes, blue (or a higher %) is better. 100% means that the view is free of glare 100% of the hours.
The easiest way is to change the schedule to fit your analysis period. It will still calculate DGP for the whole year (annual sky matrix) but the schedule will make sure that it only considers the occupied hours (within your analysis period) in the glare autonomy.
Hi @mikkel,
Thanks for your reply. I have tried that way, but it seemed not working. Any idea? Can we apply different analysis month?
You didn’t internalize the geometry, so I was not able to recreate the issue. I did try with a different geometry but that worked fine. Can you check if you are able to run the following file as it is:
imagelessGlare_Test.gh (539.9 KB)
Hi @YD,
Ah, I think I know now. The analysis period is not behaving as I expected. If you check the written schedule file, you will probably see that it got all zeros, i.e., no occupancy. You can use the other occupancy component from HB[+] to generate a valid schedule manually. But if you want the short analysis period as you showed in the image (just a single day 9-17) I am not sure the occupied glare autonomy makes much sense.
Hi @mikkel ,
thank you for your reply, but I didn’t find the component… I tried to adjust period form the python script for that component, and it works for at least two-day period.
Hi,
I see that the imageles glare analysis is already implemented in LBT.
VERY COOL!!
Thanks for that,
-A.
Great news!
Does anyone have an example file of a working recipe?
I did a quick try and got a lot of mistakes.
Hi @Hristo,
You can download a sample file here: honeybee-grasshopper-radiance/annual_glare.gh at master · ladybug-tools/honeybee-grasshopper-radiance · GitHub
