|North||_north_||Input a vector to be used as a true North direction for the wind rose or a number between 0 and 360 that represents the degrees off from the y-axis to make North. The default North direction is set to the Y-axis (0 degrees).||Goo|
|Hourly Wind Direction||_hourlyWindDirection||The list of hourly wind direction data from the Import epw component.||Goo|
|Hourly Wind Speed||_hourlyWindSpeed||The list of hourly wind speed data from the Import epw component.||Goo|
|Annual Hourly Data||annualHourlyData_||An optional list of hourly data from the Import epw component, which will be overlaid on wind rose (e.g. dryBulbTemperature)||Goo|
|Analysis Period||_analysisPeriod_||An optional analysis period from the Analysis Period component.||Goo|
|Conditional Statement||conditionalStatement_||This input allows users to remove data that does not fit specific conditions or criteria from the wind rose. To use this input correctly, hourly data, such as temperature or humidity, must be plugged into the annualHourlyData_ input. The conditional statement input here should be a valid condition statement in Python, such as "a>25" or "b<80" (without quotation marks).
The current version of this component accepts "and" and "or" operators. To visualize the hourly data, only lowercase 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 the WindBoundaryProfile component, the variable "a" always represents windSpeed. For example, if you have hourly dry bulb temperature connected as the second list, and relative humidity connected as the third list (both to the annualHourlyData_ input), and you want to plot the data for the time period when temperature is between 18C and 23C, and humidity is less than 80%, the conditional statement should be written as “18||Goo|
|Num Of Directions||_numOfDirections_||A number of cardinal directions with which to divide up the data in wind rose. Values must be greater than 4 since you can have no fewer than 4 cardinal directions.||Goo|
|Center Point||_centerPoint_||Input a point here to change the location of the wind rose in the Rhino scene. The default is set to the Rhino model origin (0,0,0).||Goo|
|Max Frequency||maxFrequency_||An optional number between 1 and 100 that represents the maximum percentage of hours that the outer-most ring of the wind rose represents. By default, this value is set by the wind direction with the largest number of hours (the highest frequency) but you may want to change this if you have several wind roses that you want to compare to each other. For example, if you have wind roses for different months or seasons, which each have different maximum frequencies.||Goo|
|Show Frequency||showFrequency_||Connect boolean and set it to True to display frequency of wind coming from each direction. By default, these values will be displayed in gray color. ||Goo|
|Show Average Velocity||showAverageVelocity_||Connect boolean and set it to True to display average wind velocity in m/s for wind coming from each direction. If a conditional statement is connected to the conditionalStatement_ input, a beaufort number is plotted(in square brackets) along with the average velocities. This number indicates the effect caused by wind of average velocity coming from that partcular direction. By default, these values will be displayed in black color.||Goo|
|Scale||_scale_||Input a number here to change the scale of the wind rose. The default is set to 1.||Goo|
|Legend Par||legendPar_||Optional legend parameters from the Ladybug Legend Parameters component.||Goo|
|Bake It||bakeIt_||An integer that tells the component if/how to bake the bojects in the Rhino scene. The default is set to 0. Choose from the following options:
0 (or False) - No geometry will be baked into the Rhino scene (this is the default).
1 (or True) - The geometry will be baked into the Rhino scene as a colored hatch and Rhino text objects, which facilitates easy export to PDF or vector-editing programs.
2 - The geometry will be baked into the Rhino scene as colored meshes, which is useful for recording the results of paramteric runs as light Rhino geometry.||Goo|
|Run It||_runIt||Set this value to "True" to run the component and generate a wind rose in the Rhino scene.||Goo|