refresh tabular data

[gbarter]

Purpose

Not quite sure what happened to the tabular data, but it was fishy. Simply refreshing based on current WISDEM outputs.

Type of change

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (non-backwards-compatible fix or feature)
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Documentation update
• Maintenance update
• Other (please describe)

Testing

• I have run existing tests which pass locally with my changes
• I have added new tests or examples that prove my fix is effective or that my feature works
• I have added necessary documentation

[jennirinker]

Thanks for fixing the pitch curve @gbarter !

Before we merge, I have a question about how we want to consider the pitch curve in the minimum-rotor-speed region. Applying a minimum rotor speed changes the TSR away from the design TSR and therefore lowers the Cp. To maximize Cp in the minimum-rotor-speed region, at DTU we find that we often need to introduce a non-zero pitch. This is why the pitch curve in, e.g. the onshore opt file has a non-zero pitch at low wind speeds.

My question is thus:

• For the IEA 15 MW, do we want to have an optimal (non-zero) steady pitch curve in the minimum-rotor-speed region or hold the pitch to zero for all wind speeds below rated?

If we are changing to a zero pitch, I need to change settings in many HAWC2 files.

[gbarter]

@jennirinker - You are 100% correct. Thank you for flagging that. Pietro and I caught the problem in our rotor performance scheduler and I have submitted a correction to the table.

[jennirinker]

Thanks for fixing!

1 small issue I see is that the pitch curve (and power curve) in the Excel table is very different from what we have in the HAWC opt file.

Are you using ElastoDyn or BeamDyn to calculate said pitch curve? We might consider adding to the FAQ some discussion about discrepancies in the pitch curve for linear (ElastoDyn) vs. nonlinear (BeamDyn/HAWC) blades.

What do you think? Do we need to check why the Excel pitch/power don't match HAWCStab2 steady results, or is it fine as-is?