You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I've been modifying WindSE for a cross-code validation with STARCCM+, I've seen that many of the columns in blade_data.csv aren't used. In a recent meeting with one of the developers, I've learnt that the angle of attack is used in the source code to compute the lift coefficients and drag coefficients in the rows. Yet, the code gives me an index error when I delete the data. In the ComputeTurbineForce subroutine of ProblemManager.py, some columns are specified for blade span, twist, and chord which are read from blade_data.csv; however, the other columns are ignored with the exception of expected column length. By the way, some files in the source code are missing from the repository in GitHub, such as ActuatorLine.py in the turbine_types folder.
Steps to reproduce issue
Please provide a minimum working example (MWE) if possible
In blade_data.csv, edit one of the columns for lift coefficient, drag coefficient, or another parameter besides blade span, chord, and twist
Add a row or subtract a row from one of the columns
Run a demo case such as 6-alm_3p4_rwt.yaml
Refer to the lines of source code given in the error message
Current behavior
…
Expected behavior
The columns for data beside blade span, chord, and twist shouldn't lead to any error message as these data aren't used in the current code
Code versions
List versions only if relevant
Python
…
The text was updated successfully, but these errors were encountered:
Description
As I've been modifying WindSE for a cross-code validation with STARCCM+, I've seen that many of the columns in blade_data.csv aren't used. In a recent meeting with one of the developers, I've learnt that the angle of attack is used in the source code to compute the lift coefficients and drag coefficients in the rows. Yet, the code gives me an index error when I delete the data. In the ComputeTurbineForce subroutine of ProblemManager.py, some columns are specified for blade span, twist, and chord which are read from blade_data.csv; however, the other columns are ignored with the exception of expected column length. By the way, some files in the source code are missing from the repository in GitHub, such as ActuatorLine.py in the turbine_types folder.
Steps to reproduce issue
Please provide a minimum working example (MWE) if possible
Current behavior
…
Expected behavior
The columns for data beside blade span, chord, and twist shouldn't lead to any error message as these data aren't used in the current code
Code versions
List versions only if relevant
The text was updated successfully, but these errors were encountered: