First time here? Check out the Help page!
1 | initial version |
I would not recommend creating SU geometry in your model once there is OS geometry. These are different, require saving to the corresponding file type, and can sometimes cause errors in the OSM.
Instead of creating an entire 3D SU block, I would recommend drawing a 2D Shading Surface Group from the OS toolbar for each adjacent building. Just make sure the surface face is oriented the correct direction (inside/outside).
2 | No.2 Revision |
I would not recommend creating SU geometry in your model once there is OS geometry. These are different, require saving to the corresponding file type, and can sometimes cause errors in the OSM.
Instead of creating an entire 3D SU block, I would recommend drawing a 2D Shading Surface Group from the OS toolbar for each adjacent building. Just make sure the surface face is oriented the correct direction (inside/outside).building.
3 | No.3 Revision |
I would not recommend creating SU geometry in your model once there is OS geometry. These are different, require saving to the corresponding file type, and can sometimes cause errors in the OSM.
Instead of creating an entire 3D SU block, I would recommend drawing a vertical 2D New
Shading Surface Group Group from the OS toolbar for each adjacent building.
4 | No.4 Revision |
I would not recommend creating SU geometry in your model once there is OS geometry. These are different, require saving to the corresponding file type, and can sometimes cause errors in the OSM.
Instead of creating an entire 3D SU block, I would recommend drawing a vertical 2D New Shading Surface Group
from the OS toolbar for each adjacent building.
In OS 1.9.0 the Facility Shading subtab is working so I would recommend naming the shading surfaces - e.g. Adjacent Building North - and then confirming that they appear in the OS App.
5 | No.5 Revision |
I would not recommend creating SU geometry in your model once there is OS geometry. These are different, require saving to the corresponding file type, and can sometimes cause errors in the OSM.
Instead of creating an entire 3D SU block, I would recommend drawing a vertical 2D New Shading Surface Group
from the OS toolbar for each adjacent building.
In OS 1.9.0 the Facility
Shading > Shading subtab is working so I would recommend naming the shading surfaces - e.g. Adjacent Building North - and then confirming that they appear in the OS App.
6 | No.6 Revision |
I would not recommend creating SU geometry in your model once there is OS geometry. These are different, require saving to the corresponding file type, and can sometimes cause errors in the OSM.
Instead of creating an entire 3D SU block, I would recommend drawing a vertical 2D New Shading Surface Group
from the OS toolbar for each adjacent building.
In OS 1.9.0 the Facility > Shading
subtab is working so I would recommend naming the shading surfaces - e.g. Adjacent Building North - and then confirming that they appear in the OS App.
The OS:ShadingSurface
objects, which are unique to OS, are translated to EnergyPlus as follows:
Shading Surface Group connected to a Space:
Shading Surface Group not connected to a Space:
7 | No.7 Revision |
I would not recommend creating SU geometry in your model once there is OS geometry. These are different, require saving to the corresponding file type, and can sometimes cause errors in the OSM.
Instead of creating an entire 3D SU block, I would recommend drawing a vertical 2D New Shading Surface Group
from the OS toolbar for each adjacent building.
In OS 1.9.0 the Facility > Shading
subtab is working so I would recommend naming the shading surfaces - e.g. Adjacent Building North - and then confirming that they appear in the OS App.
The OS:ShadingSurface
objects, which are unique to OS, are translated to EnergyPlus as follows:
Shading Surface Group connected to a Space:
Shading Surface Group not connected to a Space:
8 | No.8 Revision |
I would not recommend creating SU geometry in your model once there is OS geometry. These are different, require saving to the corresponding file type, and can sometimes cause errors in the OSM.
Instead of creating an entire 3D SU block, I would recommend drawing a vertical 2D New Shading Surface Group
from the OS toolbar for each adjacent building.
In OS 1.9.0 the Facility > Shading
subtab is working so I would recommend naming the shading surfaces - e.g. Adjacent Building North - and then confirming that they appear in the OS App.
The OS:ShadingSurface
objects, which are unique to OS, are translated to EnergyPlus as follows:
Shading Surface Group connected to a Space:
Shading Surface Group not connected to a Space:
9 | No.9 Revision |
I would not recommend creating SU geometry in your model once there is OS geometry. These are different, require saving to the corresponding file type, and can sometimes cause errors in the OSM.
Instead of creating an entire 3D SU block, I would recommend drawing a vertical 2D New Shading Surface Group
from the OS toolbar for each adjacent building.
In OS 1.9.0 the Facility > Shading
subtab is working so I would recommend naming the shading surfaces - e.g. Adjacent Building North - and then confirming that they appear in the OS App.
The OS:ShadingSurface
objects, which are unique to OS, are translated to EnergyPlus as follows:
Shading Surface Group connected to a Space:Space - e.g. a window shade:
Shading Surface Group not connected to a Space:Space - e.g. an adjacent building:
10 | No.10 Revision |
I would not recommend creating SU geometry in your model once there is OS geometry. These are different, require saving to the corresponding file type, and can sometimes cause errors in the OSM.
Instead of creating an entire 3D SU block, I would recommend drawing a vertical 2D New Shading Surface Group
from the OS toolbar for each adjacent building.
In OS 1.9.0 the Facility > Shading
subtab is working so I would recommend naming the shading surfaces - e.g. Adjacent Building North - and then confirming that they appear in the OS App.
The OS:ShadingSurface
objects, which are unique to OS, are translated to EnergyPlus as follows:
Shading Surface Group connected to a Space - Space, e.g. a window shade:
Shading Surface Group not connected to a Space - Space, e.g. an adjacent building: