Dear all,

We are running grid-based Daylight Autonomy simulations. Our model includes multiple rooms with different orientations and different shading systems.

I have a few questions:

- shading controls:

We are using detailed shading controls with automated glare control. We are planning to define a new shading group for each orientation+shading system. This would result in about 8 shading groups. I read somewhere that the detailed shading controls are still under development and I can only define 2 groups. Is this feature ready to go or stay away for now?

- results: plot of shading controls

When running the Daylight Autonomy simulations, I get the DAYsim results page, but do not see the plots for the hourly shading schedules (as shown here:http://diva4rhino.com/user-guide/rhino/advanced-shading). How can I generate these plots?

Alternatively, I can find these values also in the exported files. Can I generate this type of plot with excel?

- visualizing results: node values

Is it possible to change the font size of the node values?

Also, the reading direction of the node values (front/back) is not consequent with regard to the direction of the plane on which the nodes are located?

- node groups:

When visualizing results, is it possible to display only one node group and blend out the others?

Thanks a lot!

Sarah

Views: 123

Reply to This

Replies to This Discussion

Dear all,

I will give some feedback on my own questions and add one more:

- results: plot of shading controls:

I increased the external lux threshold in the Glare Control from 10000 to 25000 lux, and now I get a nice graph for each of the two shading groups annual schedule. So far, case closed. 

- new question regarding the .ill file

As I understand it, the .ill-file contains the illuminance on each node without use of shading. Is it somehow possible to store the local illuminances taking into account shading? What I need, is the cummulative illuminance (lux-hours/year) in each node.

Thanks,

Sarah

Dear all,

I continue talking to myself. :-)

Would still very much appreciate some feedback..

Found in previous discussions:

In the C:\DIVA\Temp folder the SG0BS0.ill file, which stands for ShadingGroup0-BlindState0, show the annual illumination when the blinds are down.

I have a model with 2 shading groups which have each three possible states: open, half-open and closed. This results in 9 different theoretical illuminance situations:

- group 1 open AND group 2 open

- group 1 open AND group 2 half-open

- group 1 open AND group 2 closed

- group 1 half-open AND group 2 open

- etc.

I find 5 .ill files:

Filename.ill -> all shading open

SG0BS0.ill -> shading group 1, half open (group 2?)

SG0BS1.ill -> shading group 1, closed (group 2?)

SG1BS0.ill -> shading group 2, half open (group 1?)

SG1BS1.ill -> shading group 2, closed (group 1?)

Correct?

I know from the Rhinofilename.intgain.120lx detailed dynamic shading.csv file what the shading states are for each group at each hour. 6 out of 9 theoretical combinations actually occur.

Where I am stuck, is how to know the illuminance in one point taking into account the actual shading state for each group.

Thanks for any input!

Sarah

Dear Diva-users,

I am really stuck with this, and would really appreciate some feedback!

The main question: How do find the actual illuminance in each point during the year, taking into account the actual shading state and the available .ill files??

Thanks,

Sarah

Hi Sarah,

Apologies for the late reply.

I read somewhere that the detailed shading controls are still under development and I can only define 2 groups. Is this feature ready to go or stay away for now?

In DIVA-Grasshopper you can have multiple shading groups, but in the Rhino toolbar which uses Daysim to operate the controls, only two shading groups are possible.

How can I generate these plots? Alternatively, I can find these values also in the exported files. Can I generate this type of plot with excel?

The plots should be generated automatically unless something is going wrong with the scripts that generate them. After running the simulations with dynamic shading enabled, you should see a few text outputs in the Rhino command history (you may have to drag it to be several lines deep).

  • Running command, c:\DIVA\Python27\python.exe c:\DIVA\Scripts\diva-climate-based_falsecolor-intgaincsv.py "C:\DIVA\temp\3\\3_intgain.csv" "C:\Users\Alstan\Desktop\test1\3 April 17 base model 2 - DIVA\Grid-Based\3.300lx conceptual dynamic shading"

Open a command prompt and try to run that command above. If you report the error, it should give some insight into what is happening. 

Is it possible to change the font size of the node values?

Also, the reading direction of the node values (front/back) is not consequent with regard to the direction of the plane on which the nodes are located?

No, unfortunately not. Also the orientation of the nodes labels sometimes being wrong is an unfortunate bug that I am well behind on trying to fix. Apologies about that.

When visualizing results, is it possible to display only one node group and blend out the others?

Yes -- you can use the 'Hide' command in Rhino to do so.

As I understand it, the .ill-file contains the illuminance on each node without use of shading. Is it somehow possible to store the local illuminances taking into account shading? What I need, is the cummulative illuminance (lux-hours/year) in each node.

Yes, but you'd have to assemble it yourself using the Filename_intgain_shading.csv in the .\Filename - DIVA\Grid Based\ folder after the results. Generally the best way to do so would be a computational script that picks the correct illuminance value from each ILL file based on the results in the CSV file.

I have a model with 2 shading groups which have each three possible states: open, half-open and closed. This results in 9 different theoretical illuminance situations: [but]  I find 5 .ill files:

The answer to this one is explained in detail here: http://daysim.ning.com/page/daysim-header-file-keyword-advanced-dyn...

(It's a little disappointing, I know.)

Best,

Alstan

Dear Alstan,

Thanks for your feedback! At least it confirms my assumptions so far. :-)

I have now simplified my model to 2 shading groups and only two states (open/closed) per shading group (so total 4 states).

To get the illuminances for all possible combinations, I can run 2 simulations:

- one simulation with the two shading groups -> gives me the shading controls and the illuminances for both or at least one shading group open.

- one simulation with all blinds in one shading group -> gives me the illuminances for all closed.

By combining the shading controls and the four illuminance files, I can sort out the values I need. Mission accomplished, although with a bit of a detour. :-)

To check:

- the daylight autonomy results (% of the year) do take into account the complete shading controls?

- the temporal illuminance map of one point gives the illuminance over the year without shading?

Kind regards,

Sarah

- the daylight autonomy results (% of the year) do take into account the complete shading controls?

Yes! Absolutely they do.

- the temporal illuminance map of one point gives the illuminance over the year without shading?

Yes, this is also correct.

Best,

Alstan

I think I am running into a bug with the detailed shading controls. I have a room with a shading group on the north and on the south side. They are controlled by glare control: facade sensors north/south, as well as interior nodes on a table near the north and south windows. I have triple checked the shades, layers, nodes etc.

After running the simulation with 6 ambient bounces, I get exactly the same open/closed schedule for both shading groups, which is unreallistic, to say the least.

I manually checked the controls:

- south exterior: 390 times above threshold

- south interior: never above threshold

- north extorior: never above threshold

- north interior: never above threshold

Therefore: south should close 390 times, north should remain open all year.

The open/closed schedule from the simulation matches with the manually generated controls for south. For the north, it has then somehow used the results from the south as well. (shading group  1 = north, shading group 2 = south)

Anyone familiar with this bug?

I am rerunning the simulation, with adapted controls for the north, so that it closed at least once with the given irradiance data.

Thanks,

Sarah

Update: I continue to get wrong results for the north orientation and accurate results for the south.

When comparing when the shades close in the north with the current irradiance values on the control nodes, it just doesn't make sense..

To make sure I understand it correctly:

Automated Glare control:

- glare control threshold = exterior node -> if one of the ref. exterior nodes lies above this value, the shades will close

- glazing state: on = interior nodes -> if one of the ref. interior nodes is above this value, this state is activated

- glazing state: off = interior nodes -> if one of the ref. interior nodes sinks below this value, the state switches to the next more open state

I have the following controls:

- glare control: 30'000 lx

- glazing state: off 300 lx, on 3'000 lx

However, the shade closes when

- interior nodes: 190-250 lx

- exterior nodes: 5'700-6'600 lx

What am I missing?

Thanks,

Sarah



Sarah Leenknegt said:

I think I am running into a bug with the detailed shading controls. I have a room with a shading group on the north and on the south side. They are controlled by glare control: facade sensors north/south, as well as interior nodes on a table near the north and south windows. I have triple checked the shades, layers, nodes etc.

After running the simulation with 6 ambient bounces, I get exactly the same open/closed schedule for both shading groups, which is unreallistic, to say the least.

I manually checked the controls:

- south exterior: 390 times above threshold

- south interior: never above threshold

- north extorior: never above threshold

- north interior: never above threshold

Therefore: south should close 390 times, north should remain open all year.

The open/closed schedule from the simulation matches with the manually generated controls for south. For the north, it has then somehow used the results from the south as well. (shading group  1 = north, shading group 2 = south)

Anyone familiar with this bug?

I am rerunning the simulation, with adapted controls for the north, so that it closed at least once with the given irradiance data.

Thanks,

Sarah

Reply to Discussion

RSS

© 2017   Created by jeff niemasz.   Powered by

Badges  |  Report an Issue  |  Terms of Service