daylight autonomy

asked 2015-03-25 07:01:45 -0600

eldav
181 ●5

updated 2017-05-04 08:53:09 -0600

__AmirRoth__

4436 ●5 ●17 http://bleedinggreenna...

Hi,

when I run my model with OS and use radiance as the daylighting engine, in the daylighting metrics.csv I have 4727 hours for the whole year, but my model is an office and the working hours are (8am to 5pm). So, the daylight autonomy should be calculated due to these hours. How can I receive the right value for Daylight autonomy and UDI?

Space101: DA(500.0) Daylit Hours 1573.43 4727 0.332861752 Space101: DA(500.0) Occupied Hours 0 0 NaN Space101: DA(500.0) Daylit and Occupied Hours 0 0 NaN Space101: conDA(500.0) Daylit Hours 2781.693774 4727 0.588469172 Space101: conDA(500.0) Occupied Hours 0 0 NaN Space101: conDA(500.0) Daylit and Occupied Hours 0 0 NaN Space101: UDI Daylit Hours 3321.31 4727 0.702625873 Space101: UDI Occupied Hours 0 0 NaN Space_101: UDI Daylit and Occupied Hours 0 0 NaN

edit retag flag offensive close merge delete

Comments

@rpg777 can you answer this one?

macumber ( 2015-03-25 13:48:56 -0600 )edit

add a comment

answered 2015-03-26 09:40:58 -0600

rpg777
6980 ●6 ●15 http://openstudio.net/

updated 2015-04-06 11:30:36 -0600

macumber

11968 ●22 ●21 http://automaticmagic.com/

@eldav, OpenStudio takes occupied hours directly from the OSM's schedule(s), using those (as well as "all daylit hours") in its metrics calcs. In the results you've included here it appears you don't have an occupancy schedule assigned to Space101 at all, which is causing your metrics to be mis-reported (occupied hours = zero is making the metrics calculator unhappy). You need to attach an occupancy schedule (AKA "people schedule") to your model. You can set schedules globally, and then override/refine them at the space level to define the 8am-5pm schedule you are looking for in this example. You can get a nice set of starter schedules from the templates; see this page for more details.