I am running a basic test for a shading scheme with advanced shading control:
interior sensor: on the floor next to the glass (highlighted below)
Shading Group 1 State 1: curtains pulled at the corner, solid surface, reflectance 0.18, when there is NO direct sunlight on the sensor (illuminance<10000 lux).
Shading Group 1 State 2: curtains along the glass, trans surface, transmittance 0.2, when there is direct sunlight on the sensor (illuminance>=10000 lux).
After the run I checked the ill files in the folder and the shading schedule in the intgain.csv file and found some inconsistency, taking Jan 1st as an example
In the intgain.csv, the shading schedule shows the curtain only covers the glass (state 2) at 9.5,11.5,13.5.
But in the ILL file with no dynamic shading, the sensor point (first column after hour) illuminance is above 10000 lux from 10 to 15. So the shading schedule should be 1 from 9.5 to 14.5, right? Or am I missing something here?
I’m trying to get the lux hours/accumulated illuminance for the test point, but there is no ILL file that actually combined the ill, state-1 ill, and state-2 ill together based on the shading schedule? (My understanding is the “read annual result I” visualizes the Daylight Autonomy based on the advanced shading schedule but didn’t generate another ill file?)
I was doing it in Excel and found the difference between shading schedule and the sensor reading. Please let me know if I made any mistakes in the simulation setting! Any comments on a better data processing method would be much appreciated!
Two quick comments:
What are the illuminance value for the first state of the shading [0.5]?
Keep in mind that Daysim is using a light switch model that tries to consider human behavior and lighting controls as well as illuminance values. Make sure you’re setting up the desired shadingControl.
2.1. If you don’t assign the control honeybee will assign a default one for you. Hover over the input to be able to read the default assumptions.
2.2. Based on the source code it does it regardless of control mode and based on user behavior (active vs passive).
Thanks! To 2.1: yes I noticed that if I don’t assign any min/max Illuminance for DSShadingState, the shade will be the manually controlled. Other than that and glare control recipe, I didn’t find any other input to specify the control mode. Please let me know if I’m missing something here.
Over the weekend I tried different settings of min/max illuminance, and found something wrong with my setting:
Ideally State 1 is only in use between 1-9999 lux and State 2 is only in use when it’s above 10000 lux (on the sensor point). However in the component, the min illuminance is for the blind to open, and max illuminance is for the blind to close.
If I set State 1 (min 0 max 1), State 1 will be in use when it’s above 1 lux; Then I set State 2 (min 9999 max 10000), State 2 will be in use when it’s above 10000 lux; Then from the inter gain csv file, I found State 2 stays even after the illuminance dropped back to less than 9999 lux.
Based on the daysim example, State 2 should go back to State 1 when the sensor illuminance drops below the min illuminance set. Am I doing something wrong that led to this error?
Thanks so much!
hello, i have a question how can you know when will the shading state 1 open and when will the shading state 2 open from the intgain.csv you generate from daysim.
sorry，i just want to konw what’s the meaning of 0.5 in the intgain.csv you got?