|Epw File||_epwFile||Input an .epw file path by using the "File Path" parameter, or Ladybug's "Open EPW And STAT Weather Files" component.||Goo|
|Wind Factor||_windFactor||Division of cfd simulation's wind speed values, and annual average wind speed value from the weather data (.epw file) at 10 meters height.
They are used to normalize against the weather data (.epw file), given that a CFD simulation with the exact .epw file wind speed and direction has not been performed.
_windFactor data should be supplied into different branches corresponding to different directions for which the cfd simulation has been performed.
For example: the first branch holds windFactors for all analysis points for wind direction 0. Second branch would hold windFactors for all analysis points for wind direction 20. Third branch would hold windFactors for all analysis points for wind direction 40 ... and so on.||Goo|
|Analysis Geometry||_analysisGeometry||Input a mesh for whose face centroids the cfd simulation has been performed.
The number of mesh face centroids needs to be equal to the number of values in each of the _windFactor branches.||Goo|
|Pedestrian Type||pedestrianType_||Choose the pedestrian type used at the analysis location:
0 = typical pedestrian (20 m/s)
1 = sensitive pedestrian (15 m/s): elderly people, cyclists, children.
This input is used to analyse pedestrian safety.
If not supplied, the 0 (typical pedestrian) will be used by default.||Goo|
|North Cfd||northCfd_||Input a vector to be used as a Cfd simulation's true North direction, or a number between 0 and 360 that represents the clockwise degrees off from the Y-axis.
If not supplied, default North Cfd direction will be set to the Y-axis (0 degrees).||Goo|
|North||north_||Input a vector to be used as Rhino's true North direction, or a number between 0 and 360 that represents the clockwise degrees off from the Y-axis.
If not supplied, default North direction will be set to the Y-axis (0 degrees).||Goo|
|Legend Par||legendPar_||Optional legend parameters from the Ladybug "Legend Parameters" component.
|Result Gradient||resultGradient_||Choose whether or not the resulting geometry-values will be created as a gradient-float or not.
It allows the following two inputs:
True - the resulting pedestrianComfortMesh, pedestrianSafetyMesh will be created as a gradient, and the pedestrianComfortCategory, pedestrianSafetyCategory will be outputed as float values.
False - the resulting pedestrianComfortMesh, pedestrianSafetyMesh will NOT be created as a gradient, and the pedestrianComfortCategory, pedestrianSafetyCategory will be outputed as integer values.
If not supplied, no gradient (integer values) will be set by default.||Goo|
|Analysis Period||analysisPeriod_||An optional analysis period from the "Analysis Period" component.
This input can be useful in cases where certain areas show higher pedestrianComfortCategory than required. For example: when analysis is run for the whole year period, the component shows that a certain location does not fulfill the comfort criteria for sitting.
However if we perform the analysis for the period from late spring to early autumn (when the sitting is suppose to happen), the comfort criteria for sitting can be fulfilled.
If not supplied, the whole year period will be used as an analysis period.||Goo|
|_________________||Script variable PedestrianWindComfort||Goo|
|Annual Hourly Data||annualHourlyData_||An optional list of hourly data from Ladybug's "Import epw" component (e.g. windSpeed), which will be used for "conditionalStatement_".||Goo|
|Conditional Statement||conditionalStatement_||This input allows users to calculate the Pedestrian wind comfort component results only for those annualHourlyData_ values which fit specific conditions or criteria. To use this input correctly, hourly data, such as windSpeed or windDirection, must be plugged into the "annualHourlyData_" input. The conditional statement input here should be a valid condition statement in Python, such as "a>4" or "b<90" (without the quotation marks).
conditionalStatement_ accepts "and" and "or" operators. To visualize the hourly data, English letters should be used as variables, and each letter alphabetically corresponds to each of the lists (in their respective order): "a" always represents the 1st list, "b" always represents the 2nd list, etc.
For example, if you have an hourly windSpeed connected as the first list, and windDirection connected as the second list (both to the annualHourlyData_ input), and you want to plot the data for the time period when windSpeed is larger than 4m/s and windDirection is southerly, the conditionalStatement_ should be written as "a>4 and b==180" (without the quotation marks).||Goo|
|_________________||Script variable HorizonAngles||Goo|
|Bake It||bakeIt_||Set to "True" to bake the pedestrianComfortMesh, pedestrianSafetyMesh, legend, legend2 into the Rhino scene.
If not supplied default value "False" will be used.||Goo|