Annual Daylight Glare Probability for multiple Test_points

[mikkel]

@LaFleur

Through the GH read file component, not display the 8760 values for each sensor, but I was able to see it via the note pad

But I have no idea how to handle this file format to be able to display the result, for example through the _LB HourlyPlot. Any suggest?

A custom Python component that reads the results line by line while skipping the Radiance header.

@LaFleur

How I read in the Tutorial “sGA will give us a single value to summarize the extent to which the space is free of glare. We will calculate the fraction of the space that exceeds 40% DGP for no more than 5% of occupied hours”, I understand that this value is a average result between the all analyzed sonsors/directionsPoint, in that case I see a discrepancy.

It is correct that taking the average will give you sGA_40%. If you want that, you can average the output of occupied_ga just fine. But in the tutorial sGA_40%,5% is calculated. It basically says that we only count the view directions where no more than 5% of occupied hours exceeds the DGP threshold.

[Asisnath]

It is working seamlessly. Thank you @mikkel for this update

[mikkel]

Since there is a growing interest in the method, I added the DGP and sGA thresholds as parameter inputs, and tidied up the Python file… at least somewhat.

imagelessglare.zip (5.7 KB)
imagelessGlare_Test.gh (539.9 KB)

[Asisnath]

I found a small bug @mikkel. When a folder location is provided to "run radiance component it fails to run without even starting the radiance batch window. Once the file path is removed it runs fine. I have no white spaces on the file path. Here is the .gh file for refence imagelessGlare_Test.gh (536.6 KB)

[Asisnath]

One more thing to report. Once file path was removed and after finishing the simulation, the legend preview below is not legible. The earlier Version of your script was working fine for both cases. For your reference I am using Rhino 7.

[mikkel]

@Asisnath

I found a small bug @mikkel. When a folder location is provided to "run radiance component it fails to run without even starting the radiance batch window. Once the file path is removed it runs fine. I have no white spaces on the file path. Here is the .gh file for refence imagelessGlare_Test.gh (536.6 KB)

I think it might be because you have a “&” sign in the folder path. At least I was not able to run the batch file with a “&” sign in the path. Can you try a different path?

Unfortunately I don’t know what’s going on in the other issue related to the legend.

[Asisnath]

@mikkel You are correct, It has the “&” sign that was creating problem. I didn’t knew “&” is also an exception for radiance. Thank you for pointing out.

For second issue I could solve it by replacing latest LBT heat map from its legacy counterpart.

Thank you again for the help. Hope this is included in LBT version shortly!

[LaFleur]

Hallo dear @mikkel,

I took your last file and added the LBT’s new PIT method, for a comparison.
I was hoping you could take a look at it.

To simplify everything I have selected only the sensor 158 and created the view only for the direction that can be seen in the vector.

.

After the imageless analysis I have extrapolated from the views…scene…default.dgp, only the results of the analysis of the sensor 158 which looks in the view direction. (This can be found in the attached file “views…scene…default-AllSensors.dgp”).
Than I read the analysis result and extrapolate, at 12 noon every 21st day of every month the DGP result.

after this, for exactly the same days and times, I rendered the view for the Sensor 158, through the new LBT1.3.0 _PIT-View and made the comparison of the values.
In the folder you will find the comparison table and the various rendered images.

In the Grasshopper file, everything inside the red groups has been added or modified by me.

If I have not done anything wrong, as you will notice there are some inconsistencies.

https://fspit2storage.blob.core.windows.net/fspwinappblobs/20211004/f20550bb-c601-4c45-a8d4-da974d8f8bf4/for_Mikkel.zip

Best regards

[mikkel]

Hi @LaFleur,

One thing I noticed is that you used the “HB CIE Standard Sky” for the PIT renderings, while the imageless results are based on the epw. The differences between the two glare methods can probably partly be explained by the use of a different sky for the renderings. Using “HB Climatebased Sky” will give you a better basis of comparison with the imageless results.

EDIT: Btw, if you only need to analyse one view direction for the imageless method, you can create an analysis grid with only one point and one direction.

[LaFleur]

Hallo @mikkel ,
I hadn’t thought about the different kind of sky-Type.

This is the updated result.

I am happy with the result.
Thank you so much for all your work

[LaFleur]

Dear @mikkel,
If I can afford, I would have a request to implement the script and a question about one component.

Having already the possibility of being able to analyze so many sensors and directions at the same time, in my opinion would be optimal, to be able to extrapolate the values for example of a single direction (per example the point 80) directly in the _readImagelssGlare component.

At the moment to do it, I need to read and extrapolate from the file “views…scene…default”, the string with the values of the desired sensor, save and convert it so that it is readable in GH.
I can understand that it can be complicated, but in my opinion it would be a great addition.

I have a question about the sGA value.

I can’t understand the decimal handling of the value.
If the Treshold is 5% (right according to the EN 17037), why your input is 0.05?
Shouldn’t the final result be 6% and not 0.6?, ie that 6% of the occupied hours has a DGP greater than 0.45, and in this case is 1% over the treshold?

I don’t wish I misunderstood something

Thanks for all
Greetings

[mikkel]

@LaFleur

Having already the possibility of being able to analyze so many sensors and directions at the same time, in my opinion would be optimal, to be able to extrapolate the values for example of a single direction (per example the point 80) directly in the _readImagelssGlare component.

At the moment to do it, I need to read and extrapolate from the file “views…scene…default”, the string with the values of the desired sensor, save and convert it so that it is readable in GH.
I can understand that it can be complicated, but in my opinion it would be a great addition.

I agree that this option would be great to have, but it is unlikely that I will add for now. There is an open issue for this recipe, and when the time comes for implementation, we can look through this forum post (which is linked to in the issue).

@LaFleur

If the Treshold is 5% (right according to the EN 17037), why your input is 0.05?

I have used this Radiance pipeline to calculate sGA. The 0.05 is just the decimal value of 5%.

[chkuen_1063175952]

hello, i want to know this imageless DGP calculate system how to replace the origin system that included illuminance simulation. And has this been published in a journal?

[Hristo]

Hi all,

since some time has passed after this discussion, has anyone been able to recreate this “recipe” in LBT?

[vinicius_petrucci]

Could you help me with the interpretation of the results?

Value - SGA_40%.5%

Corresponds to the percentage of sensors / orientations that meet the criterion, from SGA_40%.5% [Espaço, area ]
or the percentage of the hours (eg 90% of the time) is the criterion met in the sensors regardless of the orientation? [Tempo]

visualization chart

Could you clarify what is being measured in the graph in percentage SGA or DGP?
good results are blue and bad results are red?
blue means there is not glare 100 percent of the time and red means there is glare 90 to 100 percent of the time?

would there be a way to place the results numerically in the meshes

?

[mikkel]

Hi @vinicius_petrucci,

@vinicius_petrucci

Corresponds to the percentage of sensors / orientations that meet the criterion, from SGA_40%.5% [Espaço, area ]
or the percentage of the hours (eg 90% of the time) is the criterion met in the sensors regardless of the orientation? [Tempo]

It is the percentage of sensors that meets the criterion.

@vinicius_petrucci

Could you clarify what is being measured in the graph in percentage SGA or DGP?
good results are blue and bad results are red?

It is the fraction of hours where there is no glare, in this case glare occurs at DGP = 40%. Yes, blue means less glare. If the glare autonomy is 100% for a given sensor, then there is no hours where the DGP is 40% or more, i.e., it is free of glare 100% of the hours.

[mikkel]

@vinicius_petrucci

would there be a way to place the results numerically in the meshes

See the attached file.
imagelessGlare_meshresults.gh (539.2 KB)

[vinicius_petrucci]

Mikkel

Thank you very much for the clarifications. and for sharing this method of analysis, until then I believed that there were only methods with images.

this one without image, seems to me much more useful.

[Asisnath]

@chris. Any update on implementation of imageless glare of miltiple test points!

[chris]

There’s no official LBT version of this recipe yet but we have to implement it for our work at some point in the next couple of months. You’ll know when it’s been added to the development version of the plugin when you see this issue closed:

Add commands needed for Imageless Glare Recipe