Multi-objective Optimization and Generic Control Design Variables

[dzalkind]

Purpose

Add features related to WEIS industry case studies focused on multi-objective optimization and generic control parameters. Updates include

• Multi-objective analysis visualization tool
• Run WEIS/OpenFAST without tuning ROSCO, just DISCON (examples/02_run_openfast_cases/modeling_options_no_tune.yaml)
• Make it so control DVs can be defined based on the string used in the ROSCO tuning yaml or DISCON (examples/05_control_optimization/rosco_opt_analysis.yaml)
• Multi-objective optimization examples using RAFT, OpenFAST

Things left TODO:

• Clean up examples (examples/01_simulate_own_openfast_model/dlc_sim_no_tune_modeling.yaml)
• Document/test running WEIS without ROSCO tuning (modeling_options_no_tune)
• Clean up @cfrontin 's analysis notebooks (e.g., examples/04_frequency_domain_analysis_design/analysis.ipynb)
• Set up and test MOO examples (RAFT, OpenFAST, e.g., examples/04_frequency_domain_analysis_design/iea22_raft_opt_analysis_mass_ptfmpitch_3obj.yaml)
• Remove old preprocessing notebooks (examples/16_postprocessing/Fatigue_Setup.ipynb)
• Check with @cfrontin about nsga2_weis (nsga2_weis/algo/algo_nsga2.py). Should be in WISDEM, might be a git artifact.
• Fix small merge file issues
• Decide what to do about surrogate modeling (weis/ftw/surrogate_model.py, @yonghoonlee, @cfrontin)
• Verify control parameters (ps_percent, TSR) can impact rotor design in WISDEM
• Add MOO example to WISDEM repo for testing?
• Figure out what to do with optional rosco inputs (tune_rosco.py)

Type of change

What types of change is it?
Select the appropriate type(s) that describe this PR

• 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

Explain the steps needed to test the new code to verify that it does indeed address the issue and produce the expected behavior.

Checklist

Put an x in the boxes that apply.

• 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