Dear @mikkel I need your precoius time and patience for my question.
I know that the topic has been discussed over and over again, but I don´t find a post to find the right answer, based on the current version of LBT.
Thanks the addition on the LBT v.1.7, finally I want to create the work-around for a annual daylight simulation, with dynamic blinds states, based with a predefined hourly schedule, but I can’t get to the goal. Your temporary version with the Light-Path and State python script, is no longer working after the updates.
For this example I have 2 rooms, and only in one I will activated the blinds geometries.
I have create a Aperture Group for each Window and give for the Room1 Window Sud a schedules with two states (0= blinds-off, 1= blinds rotate 45°) and for the Windows Room 1: Ost and Room 2: Sud a schedules with only blinds-off hours.
Is there a way to read that the AnnualDaylight component has simulated multiple states?
Are there any Radiance parameters that require particular attention for the annual analysis?
This is because your model is not room-based (your model is made orphaned faces, shades and apertures). So when the model is written to a Radiance folder it will fail to connect the aperture groups to the sensor grids.
If you do not want to create a room, there is also the option to set one of the properties (light_path) in the sensor grids manually. This property is calculated automatically for room-based models, and this how the aperture groups are connected to the sensor grids. As you can see below the property is a list of lists.
No. But if you look in the results folder in your directory you should see a sub-folder for each Aperture Group, and in there you there are sub-folders for each state of the Aperture Group.
We are trying to run the 2 phase daylighting script with a similar method to your file above. We are assuming 2 states - One with a translucent modifier for blinds over the aperture group and One with the blinds open. When we run the daylight simulation without the Enhanced 2-phase method, the run annual daylight component runs smoothly and provides an output result. However, the Post processing component AnnualtoData fails as its not able to find the required files to convert to data.
The results folder doesnt contain .ill files as seen in the image. However, the .ill files are generated in another sub folder under the Annual Daylight folder.
I’ve check for permission issues but there seems to be none.
I have run Rhino as an Administrator just to check if there are any access issues.
I’ve tried copying the .ill files and sun up hours text file into another folder and providing that input using a Readfile component. It does not seem to work.
You did not add the aperture groups to the model – you only added the apertures. I replaced the apertures with the aperture groups, but I was not able to test it since the geometry was not internalized in the file. Let me know if this works.
I have a similar issue and when I run the daylight simulation with the dynamic schedule, there is no change in the DA and sDA results. I am considering 5 different states where state 0 is no shading, and state 1 to 4 is with fabric shading with 4 different heights.
I already have a room-based model.
I also connected the aperture group to the model (based on your previous comments) but when I do this the DA and sDA results becomes zero.
Thanks a lot for your reply. After checking the post you mentioned, I almost solve the problem, and the sDA values are different.
my issue now is that the value is becoming too low after I run with the Dynamic schedule (the dynamic schedule considers the fabric to move in four different heights where the full height will actually never happen.)
I am just wondering if the way I connected the states is wrong. because I needed to have the 0 state as no shading so I added another “HB Dynamic State” without a shading geometry connected to it to to have as the default state which is state 0 and no shading situation. I also did another thing which is connecting the xml file of the glass to the state geometry of state 0 and the window surface as the geometry to it but this also makes the same problem.
I am also not sure if there is any other part I am doing wrong.
The states are set up correctly – and you added the empty state as the first one (0), which is correct when you want a state which is identical to the parent aperture without any added shading or changed modifier.
Try to increase the Radiance parameters with HB Radiance Parameter. _recipe_type should be 2 for annual-daylight. You can set ambient bounces to 6 – there is likely no benefit in setting it higher for this model. Change the detail_level or add “-ab 6” in additional_par.
I also noticed that the file glz_sol_ctl.xml is generated with Quarter Klems resolution. Maybe it will not make a difference in this case, but here is how to make a Full Klems resolution BSDF in WINDOW. I assume the workflow has not changed in WINDOW.
I have also encountered a similar issue when running “HB Dynamic Apertures Group” for dynamically controlled Venetian blinds. The blinds have three states (with varying heights and angles) and a schedule integrated into the workflow that defines the selected state for each timestep. However, despite modifying the grid assignments for the room, I still do not get reasonable outputs from my simulation. I would appreciate your help.
You should start by moving the model or geometry closer to origin. Since you have a room object you can create the grid from the room instead of from a surface. If so you don’t need to edit the grid with the custom Python component. The real issue is probably the first item. You can see more examples here.
In the attached file I have moved the model to origin, but I suggest you move the original geometry if possible.
