The core functionality of the Region of Interest (ROI), in a Pedestrian Wind Comfort (PWC) simulation, is to define the area or the domain around the main building/region over which the pedestrian comfort should be evaluated. Additionally, it is used to automate the size and the orientation of the simulation domain reducing efforts drastically.
It is mandatory and an important step in the PWC analysis and needs to be accessed at the very beginning of the simulation just after importing the geometry.
Region of Interest Parameters
The ROI setup looks as follows:
As can be seen from Figure 1, the parameters it includes are Disc radius, Centre point, Ground height, and North angle.
Additionally, under Advanced settings, there is the option to make the Wind tunnel size larger than the default or to make a completely customized wind tunnelby defining the extensions in each direction. These parameters are discussed in detail below.
Disk Radius and Center Point
Region of interest can only be specified in the form of a disk. Hence, Disk radius defines the radius of that disk that will be used to show the results of the simulation. As obvious, the Center point defines the center of that disk in x- and y-coordinates.
Ground height defines the wind tunnel floor height. There are two scenarios:
If the terrain is flat or there is no topology, you can define the desired ground height value.
If there is an uneven topology, leave the default ground height, and a convenient value is automatically captured by the platform.
All the geometries imported to the SimScale Workbench for a PWC analysis are, by default, aligned such that the +y axis represents the north direction. However, if this convention was not followed in the construction of your geometry, the angle (degrees/radians) may be altered here allowing for north to be realigned.
Under Advanced settings, the size of the wind tunnel can be adjusted. For an automated approach, select ‘Moderate’ or ‘Large’. The dimensions used in these cases are:
$$ H, S, I = 3h $$
$$O = 9h$$
$$ H, S, I = 5h$$
$$O = 15h$$
where \(S\) is the side extension, \(I\) is the inflow extension, \(O\) is the outflow extension and \(H\) is the height extension. The height of the tallest building is defined by \(h\) (calculated from the Ground height specified above) and is taken from the CAD geometry information. This is indicated in the below diagram with \(r\) being the disk radius:
For more control, the user can select Custom under which the extensions described previously, \(H\), \(S\), \(I\), and \(O\) defined explicitly from zero (tight box around the region of interest) onward. Smaller wind tunnels will likely reduce accuracy and should be used with caution, the benefit being reduced computational resources and faster computing speeds. Customized settings should only be used by experienced users following best practices in wind sensitivity studies.
Visually Inspecting the Domain
If a topology is present, it should extend beyond the limits of the wind tunnel for all wind directions. This can be done by clicking on the eye icon on the right end of the workbench (Figure 3) to visualize the flow domain/wind tunnel and observing the green disk in relation to the floor (Figure 4).
As stated before, the default flow domain is shown in the north direction (+y axis) but will be rotated based on the number of wind directions specified for the analysis.
It is advised that the extension should be outside the green circle everywhere, which, in the above example is not true and should be revised. You can read more about why we stipulate this requirement here. Furthermore, you can read how to do this in Rhino with a worked example.
The wind comfort evaluation is done over the specified region of interest only, as shown in Figure 5:
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.