Feature #1626 TCDiag updates to wrapper and basic use case#2248
Merged
georgemccabe merged 61 commits intodevelopfrom feature_1626_tc_diag_v2Jul 18, 2023
+234-85
Commits
Commits on Jun 14, 2023
- committed
- committed
- committed
- committed
- committed
- committed
- committed
- committed
- committed
handle failing comparison when NetCDF values are stored as a string, ci-run-diff, ci-skip-unit-tests
committed- committed
- committed
- committed
- committed
Commits on Jun 15, 2023
- committed
- committed
- committed
- committed
- committed
Commits on Jun 16, 2023
Commits on Jun 28, 2023
Commits on Jul 7, 2023
- committed
- committed
- committed
- committed
Commits on Jul 10, 2023
- committed
- committed
- committed
- committed
- committed
- committed
- committed
- committed
Commits on Jul 11, 2023
@georgemccabe It seems that the "old" FV3-GFS data used "L0", but now "Z0" might be the correct level. I'm about to try it to see if this works.
committed- committed
- committed
- committed
- committed
- committed
- committed
- committed
- committed
- committed
- committed
- committed
- committed
- committed
Commits on Jul 12, 2023
Commits on Jul 14, 2023
As per #1616, updated the documentation for the basic TCDiag use case to reflect the init time and lead times for this case. Also updated the expected output.
committedAs per #1626, fixing formatting of the introductory doc block which got split off from the main part.
committed- committed
@georgemccabe, as per #1626, changing the version of MET in the TCDiagConfig_wrapped to 11.1.0. Is this correct?
committed#1626. I think my previous attempt at a bulleted list for the novel features of the use case broke the documentation build. Trying this mod.
committed