Openstudio daylighting measure

asked 2014-12-31 09:32:48 -0600

keb

723 ●2 ●9

updated 2017-08-20 15:07:44 -0600

__AmirRoth__

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

I am using PAT with a base model that has no windows. I'm running a WWR measure for each cardinal direction and then three Add Daylight Sensor measures for specific space types. I run the baseline, baseline w/o sensors, baseline w/sensors as my three design alternatives primarily to see how much savings there are with adding the daylight sensors versus no sensors. Results are the same though. I've looked at the generated osm files in these two design alternatives and the windows are generated as expected in both, as are the sensors placed in the last design alternative. I review the PAT outputs on the Run tab for each of these alternatives as well: while the space types for the daylight sensors are shown as being recognized, there is an NA or Not Applied reported for each daylight sensor measure. I'm confused why on the one hand all space types are recognized for sensor placement, but they are Not Applied. At the same time, sensors are actually placed in the model as reflected in the osm file for the alternative that has the place sensor measures.

edit retag flag offensive close merge delete

add a comment

answered 2014-12-31 10:43:15 -0600

David Goldwasser

20395 ●94 ●14 http://www.openstudio.net/

updated 2014-12-31 11:06:25 -0600

Typical output from the measure you are using should look like this. I expect in your case the zones are not getting associated with the sensors. I was able to re-create this, I'll trouble-shoot it and update the measure.

**MEASURE APPLICABILITY**
0 = Success
**INITIAL CONDITION**
20 spaces are assigned to space type 'ASHRAE_189.1-2009_ClimateZone 4-8_LargeHotel_GuestRoom'.
**FINAL CONDITION**
Added daylighting controls to 15 spaces, covering 6000 ft^2. Initial year costs associated with the daylighting controls is $75.
**INFO MESSAGES**
Cost for daylight sensors was added to spaces. The cost will remain in the model unless the space is removed. Removing only the sensor will not remove the cost.
**WARNING MESSAGES**
Space 'Space 107' has no exterior natural lighting. No sensor will be added.
Space 'Space 207' has no exterior natural lighting. No sensor will be added.
Space 'Space 109' has no exterior natural lighting. No sensor will be added.
Space 'Space 208' has no exterior natural lighting. No sensor will be added.
Space 'Space 108' has no exterior natural lighting. No sensor will be added.
Thermal zone 'Thermal Zone: Space 101 - Plus' had more than two spaces with sensors. Only two sensors were associated with the thermal zone.
Thermal zone 'Thermal Zone: Space 201 - Plus' had more than two spaces with sensors. Only two sensors were associated with the thermal zone.
Thermal zone 'Thermal Zone: Space 206 - Plus' had more than two spaces with sensors. Only two sensors were associated with the thermal zone.
**ERROR MESSAGES**

*Update:* @Kent Beason I found the measure is falsely triggering NA if there isn't a cause. That is a mistake. i'll fix and update to BCL later today. In the mean time if you add a a non 0 value to the "Material and Installation Cost per Space for Daylight Sensor" the measure will finish running and you will get a final condition (and the daylight sensors will be associated with the thermal zones).

edit flag offensive delete link

Comments

Hi David, Thank you for the info. So even though I can tell by visual inspection of the model itself that the sensors are placed, you suspect that the measure is not associating the sensors to the zones, and the update should be the remedy? The output I see stops short of the "added daylighting controls..."

keb ( 2014-12-31 11:05:30 -0600 )edit

I thought a measure status of "NA" was supposed to return the original untouched model, but it seems that it is returning a model that was run half way through the measure. I'll follow up on that behavior and may file a bug.

David Goldwasser ( 2014-12-31 11:09:02 -0600 )edit

Thanks for the 'update' above. I was recalling that I have run this measure successfully in the past (which added confusion), but now that you mention the M/I costs, I realize that I had input estimated costs for lifecycle in the past. In this case, I was just looking at the energy so I didn't mess with the cost. I'll try with the non-zero values.

keb ( 2014-12-31 11:28:48 -0600 )edit

Thanks for pointing out the error. Fix is up on BCL, but may take a few minutes for search to pickup the update. When it does, you will be able to update it from wihin the app using "Find Measures".

David Goldwasser ( 2014-12-31 11:36:41 -0600 )edit

Very useful info David and i want to thank you because this answer reduce my lifecycle cost.