UW-586: Build driver for WaveWatchIII

[WeirAE]

Synopsis

Build driver for WaveWatchIII. As per discussion, scope is limited to "library" version for the coupled model. This also requires splitting the base Driver() methods and should not expose this driver to the CLI or API.

AC:
new driver introduced in CLI and API
JSON Schema validation capability
Documentation for CLI, API and landing page addition

Type

• Bug fix (corrects a known issue)
• Code maintenance (refactoring, etc. without behavior change)
• Documentation
• Enhancement (adds new functionality)
• Tooling (CI, code-quality, packaging, revision-control, etc.)

Impact

• This is a breaking change (changes existing functionality)
• This is a non-breaking change (existing functionality continues to work as expected)

Checklist

• I have added myself and any co-authors to the PR's Assignees list.
• I have reviewed the documentation and have made any updates necessitated by this change.

[benjamin-cash]

At least for the coupled application, ww3 also requires a directory named restart_wave in the run directory. I'm not sure if that is always true, but if so it should be part of provisioning the run directory.

[WeirAE]

@benjamin-cash Thank you! I hadn't seen that in the documentation, so I may have to rely on your hands-on experience to keep me honest here!

[christinaholtNOAA]

I took a second look at the code surrounding the new driver and provided a few comments. I didn't look at any of the tests in detail at this point.

[christinaholtNOAA]

@WeirAE I think this looks nice as far as pulling out a base class/subclass for the driver and stand-alone driver. I'm concerned a bit about the wording and getting the relationships right on how we name these classes. I think this kind of activity is closely related to discussions we've had regarding clean code, so I'm going to trigger some semantics questions in offline conversations.

[elcarpenterNOAA]

It seems to be missing the API and CLI documentation. Is that coming later, or in a separate PR?

[WeirAE]

@elcarpenterNOAA This one has been limited to just the coupled library mode, which should be fully disconnected from the API and CLI. Though it might be worth still putting something in place to cover it?

[christinaholtNOAA]

There are still a few things here that I'd like to see corrected.

[WeirAE]

Unresolved a few prior threads for ease of further discussion

[christinaholtNOAA]

Still just one more thing below, but this is looking good otherwise.

[christinaholtNOAA]

LGTM.