Phase 2 Starting Point

[dzalkind]

Purpose

The goal of this branch is to update the subtrees (OpenFAST, ROSCO, WISDEM, RAFT) and fix all the issues before making new changes in Phase 2. We can start on this branch for any new Phase 2 developments.

There are a few glue code and usability updates I added from working on the IEA-22 RWT. A summary of the changes are as follows.

Major changes:

• Update MoorPy subtree: https://github.com/NREL/MoorPy/tree/dev
• Update RAFT subtree: https://github.com/dzalkind/RAFT/tree/ctopt
• Update ROSCO subtree: (v2.8.0)
• Update WISDEM subtree (was dz_floatse, should be nearly master now)
• Update pyHAMS subtree (actually conda installing this)

Minor changes:

• Updates to the CI for using mamba/miniconda, which builds the environments faster
• Path inputs given to modeling options are relative to that (modeling options) file
• Example 04 is now "under construction" until we resolve the issue with multiple water variable ballast containers
• FAST reader/writer updates and bug fixes
• GridWidth/Height will overwrite defaults if provided in DLC driver
• Re-allocate ballast into individual chambers for RAFT
• OpenFAST outputs will be placed with analysis outputs, by default
• Some optimization targets can be derived from either floatingse, RAFT, or OpenFAST

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

[yonghoonlee]

Hi Dan,
When do you anticipate to merge this PR into the develop branch?
Thank you.
Yong Hoon