add and test FV3_RRFS_v1beta #270
Conversation
The capability to run RRFS_v1beta has been tested and added to the regional workflow. As drag_suite scheme was used in the SDF, additional topo files are required to run this suite. No scripts are available for creating these topo files automatically so far (Aug 17, 2020), the required files are put in a temporary dir (/scratch2/BMC/gsd-fv3-test/she/orog) for now.
|
@gsketefian Would it be appropriate to add this suite to one of the existing end-to-end test suites so that it gets regularly tested? |
|
This suite or the FV3_GFS_v16beta needs to be the out-of-the-box case.
…On Tue, Aug 18, 2020 at 1:28 PM Michael Kavulich ***@***.***> wrote:
@gsketefian <https://github.com/gsketefian> Would it be appropriate to
add this suite to one of the existing end-to-end test suites so that it
gets regularly tested?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<https://github.com/NOAA-EMC/regional_workflow/pull/270#issuecomment-675669390>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA3WNU22V7RJUQPAQDATNKDSBLI4HANCNFSM4QCLBFGQ>
.
|
mkavulich
left a comment
There was a problem hiding this comment.
The file config.sh should not be committed to the repository; please remove it from version control in your branch.
| JPgrid_WIDE_HALO_WIDTH=6 | ||
|
|
||
| DT_ATMOS="300" | ||
| DT_ATMOS="40" |
There was a problem hiding this comment.
We should not change the default timestep, this will change results for people unexpectedly. If you need a different timestep you can overwrite it in config.sh.
There was a problem hiding this comment.
@mkavulich I suggested Siwei commit this change. The default timestep is too long, and will fail for this pre-defined domain every time. A dt_atmos of 40 is what we should be using as the default for all pre-defined domains, since they all use the same vertical coordinate structure, and that is currently the limiting factor for stability.
There was a problem hiding this comment.
If that's the case then the change should definitely be noted in the PR message and broadcast more widely than just in this PR; it will change results for people who do not specify DT_ATMOS in their config.sh
There was a problem hiding this comment.
Thank you. I revoked the change on DT_ATMOS, and will be on a separate PR.
| raw_orog_fp="${raw_dir}/${raw_orog_fn}" | ||
| mv_vrfy "${raw_orog_fp_orig}" "${raw_orog_fp}" | ||
|
|
||
| # copy two files for drag_suite to the orog directory (temporary) |
There was a problem hiding this comment.
If they are necessary for running the case, these files should be added to the standard static/fix files on each official platform. We should not point to personal directories that could change unexpectedly.
There was a problem hiding this comment.
Thank you. We are waiting on Mike's script to replace those files, and will update this when it is ready.
@siwei-noaa When you issue a "git add" for files in your local branch, be careful of "git add -A", as that will add everything that has changed, and may not be what you want to commit. The config.sh file is one example, since it's a user-defined file used for specific experiment configuration. |
The file has been removed. |
Yes, whenever a new suite is added, a new WE2E test configuration should be added to test it regularly, especially an important one like this one @siwei-noaa Please create a new WE2E test for this scheme as follows. Start with the file regional_workflow/tests/config.regional_003.sh I'm happy to talk on the phone if these instructions are not clear. |
I agree -- probably should be this suite. But I suggest making that a separate PR. |
| @@ -244,6 +244,8 @@ Creating links in the FIXsar directory to the grid files..." | |||
| fns=( \ | |||
| "C*${DOT_OR_USCORE}oro_data.tile${TILE_RGNL}.halo${NH0}.nc" \ | |||
There was a problem hiding this comment.
@siwei-noaa Same comment as above for these lines. An "if [ "${CCPP_PHYS_SUITE}" = "FV3_RRFS_v1beta" ]" statement should be added for the oro_data_??.tile* files in this block. After the initial "if" statement, an "else" clause would have the original oro_data.tile* files, so that those would be defined for anything other than FV3_RRFS_v1beta.
There was a problem hiding this comment.
In testing, will commit if it works.
… into develop Update local develop branch from upstream develop branch
Merege the latest upstream branch to my feature branch
| fi | ||
|
|
||
| # two files for drag_suite scheme | ||
| if [ "${CCPP_PHYS_SUITE}" = "FV3_RRFS_v1beta" ]; then |
There was a problem hiding this comment.
@siwei-noaa, one last bug in this block of code. All ${FIXsar} variables are now ${FIXLAM} in the community workflow. Once that change is in, I think we'll be ready to merge.
DESCRIPTION OF CHANGES:
The SDF FV3_RRFS_v1beta has been merged into the ufs-weather-model. The regional workflow does not have capability/configurations for running this new SDF. Such capability was added and tested in this request.
It should be noted that two topographic files are required to run FV3_RRFS_v1beta as "drag_suite" scheme is used. So far (Aug 17, 2020), no scripts for automatic creating the required files, and they are copied from a temporary directory.
TESTS CONDUCTED:
CONTRIBUTORS:
Dr. Michael Toy (NOAA/GSL) provided the required topographic files for using "drag_suite" scheme.