pep4life's profile - activity

Hi, I've searched Unmet Hours for some direction on my question and found only 3 posts.
My goal is to place daylight shelves on the equator-facing wall of a single room, to obtain even light distribution. I only want to see if this will actually work, by installing them, running a simulation, and then studying the DC maps. I altered an existing measure (as understood from this post) to add a single light shelf, and although the measure runs, no light shelves are actually added.

Here's what has happened between my goal and my problem:

With some background in Python, I did some Ruby tutorials and started studying some measures for structure and hierarchy, in particular, the ''AddOverhangsByProjectionFactor' and 'AEDGSmallToMediumOfficeFenestrationAndDaylightingControls' measures. I would like only to see if adding light shelves will in fact help me reach my goal, so I'm not after extra functionality. So I started really small to get a single light shelf on one wall, naming the targeted SubSurface inside the .rb file itself. Studying the SDK documentation and the Measure Writing Guide on Git and on OS website, and taking cues from the measures I studied, addDaylightingDeviceShelf() seemed a good method to choose. But since this method returns an 'OptionalDaylightingShelf'; thus, I checked if it was empty and finding it wasn't, I tried to use the "get" method to see what the variable was pointing to. But the .get method called on this object is not recognized. (However, the measure does run without calling the "get" method, although without any light shelves inserted into the model.)

Here is my code trying the get method (I include the entire measure, so that if anything is missed, it will be obvious):

# start the measure

class AddDaylightShelvesToEquatorFacingWall < OpenStudio::Ruleset::ModelUserScript

# define the name that the user will see ... human readable def name return "Add Daylight Shelves to Equator-facing Wall" # "Add Remove Or Replace Window Overhangs" end

# human readable description def description return "This measure adds daylighting shelves to the equator-facing wall, or to wall specified by the user, at the user-specified width.
Daylighting shelves are useful in creating occupant comfort, both visual and thermal, thus increasing work productivity.
Daylight shelves bounce daylight off ceiling surfaces, thus pushing light further into a building and reducing the need for artificial lighting at certain times of day. If properly designed, they can help to reduce the excessive use of blinds for glare protection, and thus allow for occupant view and more effective use of a space. In combination with exterior shading, daylight shelves evenly distribute light and avoid stark light/dark contrasts and glare over the work plane. Daylighting shelves require high floor to ceiling heights to be effective, given the requirement for daylighting windows (above the daylight shelves positioned above eye level) in addition to view windows below. Note that in some jurisdictions, daylight shelves have a maximum width requirement, due to coordination with sprinkler code requirements. Upper surface of shelves must have high reflectance." end ... (more)

Is it possible to delete a space infiltration effective leakage area object (SIELAO) in OpenStudio 1.12.0? I'm using the 90.1-2010 mid-rise apartment template and have built a model with 56 suites and 8 corridors, each assigned a thermal zone. I have connected my thermal zones to VAV with reheat for the corridors and a simple HVAC air loop (added OA system, var fan, and diffusers to an empty air loop) for the apartment suites which are heated via in-floor radiant heating (after reading this great post: https://unmethours.com/question/9177/...). I initially assigned a SIELAO to each of my two space types, but was getting errors like this:

Program Version,EnergyPlus, Version 8.5.0-c87e61b44b, YMD=2016.10.26 09:04,IDD_Version 8.5.0 *** IDF Context for following error/warning message: *** Note -- lines truncated at 300 characters, if necessary... *** 31135 ZoneInfiltration:EffectiveLeakageArea, *** indicated Name=Space Infiltration Effective Leakage Area 1 *** Only last 2 lines before error line shown..... *** 31136 Space Infiltration Effective Leakage Area 1, !- Name *** 31137 , !- Zone Name * Severe * IP: IDF line~31137 Error detected in Object=ZONEINFILTRATION:EFFECTIVELEAKAGEAREA, name=SPACE INFILTRATION EFFECTIVE LEAKAGE AREA 1 * ~~~ * Field [Zone Name] is required but was blank *** IDF Context for following error/warning message: *** Note -- lines truncated at 300 characters, if necessary... *** 31180 ZoneInfiltration:EffectiveLeakageArea, *** indicated Name=Space Infiltration Effective Leakage Area 2 *** Only last 2 lines before error line shown..... *** 31181 Space Infiltration Effective Leakage Area 2, !- Name *** 31182 , !- Zone Name * Severe * IP: IDF line~31182 Error detected in Object=ZONEINFILTRATION:EFFECTIVELEAKAGEAREA, name=SPACE INFILTRATION EFFECTIVE LEAKAGE AREA 2 * ~~~ * Field [Zone Name] is required but was blank * Warning * IP: Note -- Some missing fields have been filled with defaults. See the audit output file for details. * Severe * IP: Blank "required" fields found in input * Severe * IP: Out of "range" values and/or blank required fields found in input * Fatal * IP: Errors occurred on processing IDF file. Preceding condition(s) cause termination. ...Summary of Errors that led to program termination: ..... Reference severe error count=4 ..... Last severe error=IP: Out of "range" values and/or blank required fields found in input *** Warning: Node connection errors not checked - most system input has not been read (see previous warning). *** Fatal error -- final processing. Program exited before simulations began. See previous error messages. *** EnergyPlus Warmup Error Summary. During Warmup: 0 Warning; 0 Severe Errors. *** EnergyPlus Sizing Error Summary. During Sizing: 0 Warning; 0 Severe Errors. *** EnergyPlus Terminated--Fatal Error Detected. 1 Warning; 4 Severe Errors; Elapsed Time=00hr 00min 0.97sec

I then read a post that said it was better to assign them to the spaces directly. So I assigned them to each of my 64 spaces in the spaces properties tab under Air Flow; so then I had 64 SIELAOs for my spaces and still 2 in my space types - a total of 66 SIELAOs. I then tried deleting the SIELAOs from my space types tab simply by deleting the object names from my space types tab (haven't ... (more)