Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
Can you post an example of one of these problematic OS:SubSurface definitions in your .osm file (CTRL-F in a text editor)? For a sub surface, one can leave blank its Outside Boundary Condition Object if its base surface faces the outdoors, for example. But for paired interzone base surfaces, 2x OS:SubSurfaces must also be paired and reference each other (each Outside Boundary Condition Object can't be left blank). OpenStudio will rely on setAdjacentSubSurface to accomplish this.
There is a bit more flexibility in native E+ as discussed here, but it looks like there's an error in the docs (there's no reason to reference an adjacent ceiling in there).
| | 2 | No.2 Revision |
Can you post an example of one of these problematic OS:SubSurface definitions in your .osm file (CTRL-F in a text editor)? For a sub surface, one can leave blank its Outside Boundary Condition Object if its base surface faces the outdoors, for example. But for paired interzone base surfaces, 2x OS:SubSurfaces must also be paired and , i.e. reference each other (each Outside Boundary Condition Object can't be left blank). OpenStudio will rely on setAdjacentSubSurface to accomplish this.
There is a bit more flexibility in native E+ as discussed here, but it looks like there's an error in the docs (there's no reason to reference an adjacent ceiling in there).
