Revision history [back]

Yes, OpenStudio has Glare Sensor objects you can place in your model, which will calculate vertical illuminance as well as Daylight Glare Probability Simplified (DGPs), which is based on vertical eye illuminance. The DGPs is calculated for every glare sensor view, for every hour, and is saved to the space's daylighting results directory. Results are stored in the format: (month),(day),(time),(DGPs), e.g.:

1,1,08:00:00,0.1855886095523

1,1,09:00:00,0.18451802954957

1,1,10:00:00,0.2000663350443

1,1,11:00:00,0.20581065771419998

1,1,12:00:00,0.1969010569402

1,1,13:00:00,0.1863662052781

If you had multiple glare sensors in the space (or multiple views per glare sensor), you'd just have a longer array of DGPs values following the mon/day/hr bits. You could take this data and plot it for an annual overview. There are some caveats:

• A big missing tooth in the dataset is the spatial (coordinate) data
• DGP-simplified is technically only reliable for views where there is no direct sun, since the spatial/positional aspect of the flux is lost to the integral (illuminance)

We hope to resolve these issues for v1.8.0 as Larry states above. We will offer true DGP reporting (based on a simple image -- good enough to resolve position indices), and include spatial data with it, allowing for far more robust reporting, as well as allowing for glare to be used as a control signal.

Yes, OpenStudio has Glare Sensor objects you can place in your model, which will calculate vertical illuminance as well as Daylight Glare Probability Simplified (DGPs), which is based on vertical eye illuminance. The DGPs is calculated for every glare sensor view, for every hour, and is saved to the space's daylighting results directory. Results are stored in the format: (month),(day),(time),(DGPs), e.g.:

1,1,08:00:00,0.1855886095523

1,1,09:00:00,0.18451802954957

1,1,10:00:00,0.2000663350443

1,1,11:00:00,0.20581065771419998

1,1,12:00:00,0.1969010569402

1,1,13:00:00,0.1863662052781

If you had multiple glare sensors in the space (or multiple views per glare sensor), you'd just have a longer array of DGPs values following the mon/day/hr bits. You could take this data and plot it for an annual overview. There are some caveats:

• A big missing tooth in the dataset is the spatial (coordinate) data
• DGP-simplified is technically only reliable for views where there is no direct sun, since the spatial/positional aspect of the flux is lost to the integral (illuminance)

We hope to resolve these issues for v1.8.0 as Larry states above. We will offer true DGP reporting (based on a simple image -- good enough to resolve position indices), and include spatial data with it, allowing for far more robust reporting, as well as allowing for glare to be used as a control signal.

Yes, OpenStudio has Glare Sensor objects you can place in your model, which will calculate vertical illuminance as well as Daylight Glare Probability Simplified (DGPs), which is based on vertical eye illuminance. The DGPs is calculated for every glare sensor view, for every hour, and is saved to the space's daylighting results directory. Results are stored in the format: (month),(day),(time),(DGPs), e.g.:

1,1,08:00:00,0.1855886095523

1,1,09:00:00,0.18451802954957

1,1,10:00:00,0.2000663350443

1,1,11:00:00,0.20581065771419998

1,1,12:00:00,0.1969010569402

1,1,13:00:00,0.1863662052781

If you had multiple glare sensors in the space (or multiple views per glare sensor), you'd just have a longer array of DGPs values following the mon/day/hr bits. You could take this data and plot it for an annual overview. There are some caveats:

• A big missing tooth in the dataset is the spatial (coordinate) data
• DGP-simplified is technically only reliable for views where there is no direct sun, since the spatial/positional aspect of the flux is lost to the integral (illuminance)

We hope to resolve these issues for v1.8.0 as Larry states above. We will offer true DGP reporting (based on a simple image -- good enough to resolve position indices), and include spatial data with it, allowing for far more robust reporting, as well as allowing for glare to be used as a control signal.

P.S. @TaylorRoberts, the illuminance maps are intended for computing the spatial distribution of the daylight flux, hence the name. This is not the same thing as glare, tho technically you can get useful daylight illuminance (UDI) from these maps, and UDI can serve as a proxy for glare. See this paper for some great info on this, and -- as always -- some more caveats: http://infoscience.epfl.ch/record/179939

Yes, OpenStudio has Glare Sensor objects you can place in your model, which will calculate vertical illuminance as well as Daylight Glare Probability Simplified (DGPs), which is based on vertical eye illuminance. The DGPs is calculated for every glare sensor view, for every hour, and is saved to the space's daylighting results directory. Results are stored in the format: (month),(day),(time),(DGPs), e.g.:

1,1,08:00:00,0.1855886095523

1,1,09:00:00,0.18451802954957

1,1,10:00:00,0.2000663350443

1,1,11:00:00,0.20581065771419998

1,1,12:00:00,0.1969010569402

1,1,13:00:00,0.1863662052781

If you had multiple glare sensors in the space (or multiple views per glare sensor), you'd just have a longer array of DGPs values following the mon/day/hr bits. You could take this data and plot it for an annual overview. There are some caveats:

• A big missing tooth in the dataset is the spatial (coordinate) data
• DGP-simplified is technically only reliable for views where there is no direct sun, since the spatial/positional aspect of the flux is lost to the integral (illuminance)

We hope to resolve these issues for v1.8.0 as Larry states above. We will offer true DGP reporting (based on a simple image -- good enough to resolve position indices), and include spatial data with it, allowing for far more robust reporting, as well as allowing for glare to be used as a control signal.

P.S. @TaylorRoberts, the illuminance maps are intended for computing the spatial distribution of the daylight flux, hence the name. This is not the same thing as glare, tho technically you can get useful daylight illuminance (UDI) from these maps, and UDI can serve as a proxy for glare. See this paper for some great info on this, and -- as always -- some more caveats: http://infoscience.epfl.ch/record/179939