-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
move diag_table/field_table from input directory to tests/parm in the repository #644
Comments
@BinLiu-NOAA I noticed in your last commit, the field_table was changed back to the one in input directory (input-data-20210930/FV3_hafs_input_data/field_table), while in the PR #870 the field_table is from ufs-weather-model/tests/parm/field_table/field_table_hafs. I am not removing all the field_tables in the input directory, but the HAFS tests will change due to the difference in the two field_tables. Do you want to change the ufs-weather-model/tests/parm/field_table/field_table_hafs to input-data-20210930/FV3_hafs_input_data/field_table? |
@junwang-noaa, please help to delete the FV3_hafs_input_data/field_table file when preparing a new version INPUT DATA. We would like to use this one (ufs-weather-model/tests/parm/field_table/field_table_hafs) instead. BTW, please also help to delete this FV3_hafs_regional_input_data directory (which is no longer needed). Thanks! |
Bin, thanks for the clarification on the field_table.
The FV3_hafs_regional_input_data is deleted in the input
directory input-data-20211015 on hera, the input data directory will be
synced to other platforms when all the testing is done.
…On Wed, Nov 10, 2021 at 8:48 AM Bin Liu ***@***.***> wrote:
@junwang-noaa <https://github.com/junwang-noaa>, please help to delete
the FV3_hafs_input_data/field_table file when preparing a new version INPUT
DATA. We would like to use this one
(ufs-weather-model/tests/parm/field_table/field_table_hafs) instead. BTW,
please also help to delete this FV3_hafs_regional_input_data directory
(which is no longer needed). Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#644 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI7D6TIL2FWWKAZDFXCFV3DULJZ2RANCNFSM46XN53FQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Thanks @junwang-noaa! |
@junwang-noaa we could remove all of the older WW3_input_data_* directories, except for the most recent one if you are working to clean-up and create a new input directory. |
Sure, I will keep only the WW3_input_data_20211101 in the latest input data
repository.
…On Wed, Nov 10, 2021 at 9:38 AM Jessica Meixner ***@***.***> wrote:
@junwang-noaa <https://github.com/junwang-noaa> we could remove all of
the older WW3_input_data_* directories, except for the most recent one if
you are working to clean-up and create a new input directory.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#644 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI7D6TLJYGJH5NMYZNX5WV3ULJ7WHANCNFSM46XN53FQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
* Add FV3_GFS_v15_thompson_mynn_lam3km * Add a we2e test for thompson_mynn_lam3km * Update namelist files * Add MERRA2 data * Fix typos * Move the SDF line in scripts * remove change of nstf_name
Description
Currently the diag_table and field_table are located in the input data directory. There are some discussion to move those small model test related configuration files to test/parm directory so that updates in those files can be better tracked.
Another updates are to clean up the template variable replacement. Currently there are two different ways to replace the variable values in the template, it would be good if we can clean them up to avoid confusion.
Solution
Related to
Directly reference any issues or PRs in this or other repositories that this is related to, and describe how they are related. Example:
The text was updated successfully, but these errors were encountered: