I’m working on an annual daylight simulation involving three windows: one static and two dynamic. I’m trying to assign multiple states to the dynamic windows, but for some reason, the simulation doesn’t seem to reflect the changes between states correctly.
When I run the simulation with only one state, it works. However, switching to another state doesn’t produce any noticeable difference in the results, which makes me think the dynamic behavior isn’t being applied properly.
I’m fairly new to this workflow and not sure where the issue might be. I’d really appreciate any help or suggestions!
When using aperture groups we need to link the groups to the grids. Right now this is only possible if you create the grids with the HB Sensor Grid from Rooms component. There is a workaround though; you can check my message in this topic. You can add a grid and a room to the custom Python script. If you do this all the aperture groups in the room will be used in the ray tracing of the grid.
Thanks for the response. The problem was related to the grids, the one you told me didn’t solved my problem but the things explained in here did.
I have another question about how HB Annual Daylight works with dynamic groups. At first, it creates the data without taking the dynamic groups into account, and then, during the post-processing, it applies the effects of these groups. I want to understand if the analysis is being done correctly, because I’m not completely sure.
This workflow is the basis for a more complex project. In my case, the dynamic apertures change according to BSDF files that vary with the position of the sun, so I have many BSDF files that I need to assign at each moment of the day and during the simulation. The problem is that I will have many states, and from what I’ve been researching, it seems quite complicated to manage. That’s why I was thinking of dividing the year into several simulations, each with a limited number of states linked to specific BSDFs. However, I’m not sure if this methodology will work properly.
The illuminance will be calculated for each state of the aperture group resulting in annual illuminance matrices for each state. This is done in the recipe. In the post-processing we select which state to use for each hour – so we pick the illuminance values from the illuminance matrices according to the dynamic schedule.
So if I generate a heat map after running only the hb an annual daylight simulation, does it actually represent meaningful data or are the values only truly significant after post-processing the simulation results?
I still have an issue: I have three windows—two of them are dynamic, and one is static.
I managed to partially solve the problem by adding this script
and now the simulations seem to respond correctly when I only have the two dynamics windows. On the right, I have the post-processed simulation results, and on the left, the raw output from the HB Annual Daylight component. These were run using only the dynamic windows, both in the open and closed states.
What I still don’t understand is why things don’t work properly when I also include the static window. If I uncomment the line of code related to the static window and connect all three windows to the model, the results barely change when I modify the schedule. I expected a clearer difference, but it’s almost negligible.
I do not understand what I am doing wrong.
About the other question I am trying to simulate 20 states but I do not know if they are a lot.
The recipe don’t know how to post-process the states, so it will just select the first state for every hour.
Maybe this is because the static aperture is so large that there is a constant high level of illuminance, so adding the smaller dynamic apertures will not make a huge difference when looking at daylight autonomy.
That should be fine. In any case you will not be able to calculate the annual metrics for all 20 states if you split the simulation into e.g. 5 simulation with 4 states each.
