fv3-schema-update

[maddenp-noaa]

Synopsis

Updates to the FV3Forecast JSON Schema to try to track current code and documentation. Issues mentioned in UW-495 may still need to be addressed in the context of this PR.

Type

• Bug fix (corrects a known issue)
• Code maintenance (refactoring, etc. without behavior change)

Impact

• 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.

[christinaholtNOAA]

I'm realizing with this PR that we will likely want to brainstorm soon-ish how to deal with the interaction of the requirements of various drivers with each other just as a forward thinking exercise.

Here, it becomes evident in the parts that limit entries of a given section like the preprocessing: lateral_boundary_conditions: block. We will likely want more than that to be able to communicate the needs of that driver, but these are the bare minimum needed to complete a regional atmospheric uncoupled forecast. I tried to point out those bits in particular that are related to this concept.

[maddenp-noaa]

config.txt
Here's a YAML config that passes validation given the schema as of this writing. Please let me know if you see any issues.

My current plan is: Once we think the schema and general semantics are ok, I'll

1. Add more of the granular schema tests to shore up the FV3 schema, then
2. Do a separate PR to update the RST docs where they're impacted by the changes in this PR, then
3. Merge all of the in-progress graph-based-driver work and continue with that.

[christinaholtNOAA]

LGTM. Thanks for sticking with me through several iterations, and owning getting this into decent shape.