Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unused Coefficients of Lift and Drag in blade_data.csv #110

Open
JonLock1689 opened this issue Jul 7, 2023 · 0 comments
Open

Unused Coefficients of Lift and Drag in blade_data.csv #110

JonLock1689 opened this issue Jul 7, 2023 · 0 comments

Comments

@JonLock1689
Copy link

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

  1. In blade_data.csv, edit one of the columns for lift coefficient, drag coefficient, or another parameter besides blade span, chord, and twist
  2. Add a row or subtract a row from one of the columns
  3. Run a demo case such as 6-alm_3p4_rwt.yaml
  4. 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant