Conversation
Co-authored-by: Gillian Petro <96886803+gspetro-NOAA@users.noreply.github.com>
Co-authored-by: Gillian Petro <96886803+gspetro-NOAA@users.noreply.github.com>
| - Coupled :term:`ATM` - :term:`MOM6`- :term:`WW3` - :term:`CMEPS` | ||
| * - HAFS-ALL | ||
| - Coupled :term:`CDEPS` - :term:`ATM` - :term:`HYCOM` - :term:`WW3` - :term:`CMEPS` | ||
| - Coupled :term:`CDEPS` - :term:`ATM` - :term:`WW3` - :term:`CMEPS` |
There was a problem hiding this comment.
| - Coupled :term:`CDEPS` - :term:`ATM` - :term:`WW3` - :term:`CMEPS` | |
| - Coupled :term:`CDEPS` - :term:`ATM` - :term:`MOM6` - :term:`WW3` - :term:`CMEPS` |
Doesn't make sense to have a hurricane test with no ocean model ;) MOM6 replaces HYCOM in tests that aren't deleted.
There was a problem hiding this comment.
There are tests with "hafs" in the name which do not include OCN. There are several ATM only as well as an ATM-WAV.
There was a problem hiding this comment.
Yes, we list ATM and ATMW as separate configurations in this table near the top, and HAFS, HAFSW, HAFS-MOM6W, and HAFS-ALL are each listed, but @jdkublnick we are missing HAFS-MOM6. And I would think HAFS-ALL would switch from HYCOM to MOM6, right? That's the edit I was trying to make here. But I'm also wondering if this entire table may have outlived its usefulness... I mean, in theory, people could build experiments for any combination of WM components if they wanted, and the existing list in CMakeLists.txt just keeps expanding. It might make more sense to nix the list and send them to the relevant file for the list of APPs. And/or to rt.conf to see what particular tests are compiled with which -DAPP flag. If we keep the list, I think the key for @jdkublnick is going to be to check the tests for each relevant compile in rt.conf rather than just taking out HYCOM and assuming it'll still be valid and non-redundant (unless you can think of a better way?).
There was a problem hiding this comment.
@jdkublnick It looks like the details on each APP and what components are available with each are listed in cmake/configure_apps.cmake. Maybe Denise has a different suggestion, but that looks to me like the clearest place to get the full list of APPs and corresponding components. It might be best just to go over this whole table and makes sure everything's covered and accurate/up-to-date.
| * - hycom1_25.nc | ||
| - vertical coordinate thickness defining 25 vertical levels | ||
| - 9.00, 5.00 | ||
| - | ||
| * - hycom1_75_800m.nc | ||
| * - hycom1_75_800m.nc |
There was a problem hiding this comment.
@DeniseWorthen Are these two files used by MOM6 despite their name? They're listed in the MOM6 section of the docs.
There was a problem hiding this comment.
Yes, despite the name, they are used by MOM6 to set the vertical grid.
There was a problem hiding this comment.
It could be good to look at changing that... Not a pressing issue, but maybe next time there's a new input data directory for other reasons, it could be considered? 🤔 Not sure to what extent changing the naming would have an outsized impact on other code/tests tho, so if we need to keep it as-is, that's fine.
| * - hycom_YYYYMM_surf_nolev.nc | ||
| - MOM6 forcing file for year YYYY and month MM | ||
| - ✔ |
There was a problem hiding this comment.
@DeniseWorthen @NickSzapiro-NOAA Is this file still used by CICE? The description indicates that despite the name, it's a MOM6 forcing file.
There was a problem hiding this comment.
Sorry ... where do you see this is related to CICE? Usage in RTs seems more CDEPS docn ocn_data
There was a problem hiding this comment.
Oops, you're right! I scrolled up too far. It was a CDEPS thing; wondering if it still is.
There was a problem hiding this comment.
I imagine these are SSTs from a Hycom run and are now "data" input coupled to ATM in RT
| @@ -390,7 +389,7 @@ Lastly, the :wm-repo:`test configuration file <blob/develop/tests/tests/hafs_reg | |||
| export INPUT_NML=input_regional_hafs.nml.IN | |||
| export MODEL_CONFIGURE=model_configure_hafs.IN | |||
| export UFS_CONFIGURE=ufs.configure.hafs_atm_ocn_wav.IN | |||
| export FV3_RUN="hafs_fv3_run.IN hycom_hat10_run.IN hafs_ww3_run.IN" | |||
There was a problem hiding this comment.
I think in this section of the docs, you actually need to copy-paste from a different test because the test that this sample is based on (hafs_regional_atm_ocn_wav) is getting deleted in Denise's PR, and even if it weren't, you probably can't just omit that file. It would likely need a replacement, tho I'd have to look into it further.
Her PR adds: tests/tests/hafs_regional_storm_following_1nest_atm_ocn_wav_mom6_debug
So maybe you could look at the configuration for that one?
Commit Queue Requirements:
test_changes.listindicates which tests, if any, are changed by this PR. Committest_changes.list, even if it is empty.Description:
Purging hycom documentation from User's Guide.
Commit Message:
Priority:
Git Tracking
UFSWM:
Sub component Pull Requests:
UFSWM Blocking Dependencies:
Documentation:
Changes
Regression Test Changes (Please commit test_changes.list):
Input data Changes:
Library Changes/Upgrades:
Testing Log: