Make thompson_mynn_lam3km ccpp suite available #644
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| # | ||
| # TEST PURPOSE/DESCRIPTION: | ||
| # ------------------------ | ||
| # | ||
| # This test is to ensure that the workflow running in community mode | ||
| # completes successfully on the RRFS_CONUS_3km grid using the GFS_v15_ | ||
| # thompson_mynn_lam3km physics suite with ICs and LBCs derived from FV3GFS. | ||
| # | ||
|
|
||
| RUN_ENVIR="community" | ||
| PREEXISTING_DIR_METHOD="rename" | ||
|
|
||
| PREDEF_GRID_NAME="RRFS_CONUS_3km" | ||
| CCPP_PHYS_SUITE="FV3_GFS_v15_thompson_mynn_lam3km" | ||
|
|
||
| EXTRN_MDL_NAME_ICS="FV3GFS" | ||
| EXTRN_MDL_NAME_LBCS="FV3GFS" | ||
| USE_USER_STAGED_EXTRN_FILES="TRUE" | ||
|
|
||
| DATE_FIRST_CYCL="20190701" | ||
| DATE_LAST_CYCL="20190701" | ||
| CYCL_HRS=( "00" ) | ||
|
|
||
| FCST_LEN_HRS="6" | ||
| LBC_SPEC_INTVL_HRS="3" |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -593,6 +593,25 @@ fi | |
| # | ||
| #----------------------------------------------------------------------- | ||
| # | ||
| # Copy MERRA2 aerosol climatology data. | ||
|
Collaborator
There was a problem hiding this comment. @chan-hoo @JeffBeck-NOAA Question: Do these directories need to always be copied or only when using the thompson_mynn_lam3km suite? If the latter, can we wrap them in an if-statement that checks for the suite (i.e. in a new PR, or I can throw it in my current PR)? Just want to reduce the time it takes to generate a new experiment... Thanks.
Collaborator
Author
There was a problem hiding this comment. @gsketefian, Jili answered this question above: "the MERRA2 aero clim dataset is for the independent aerosol module/scheme and not particular for Thompson scheme."
Collaborator
There was a problem hiding this comment. @chan-hoo, is the MERRA2 aero clim dataset only used when running RRFS-CMAQ? If so, then, we may want something like DO_CMAQ="true" in the config.sh file to avoid copying these files unless it's being used.
Collaborator
Author
There was a problem hiding this comment. @JeffBeck-NOAA, No. Since RRFS-CMAQ is coupled with GFS v15, CCPP is not available. MERR2 is used in SRW App (FV3-LAM).
Collaborator
There was a problem hiding this comment. @chan-hoo, right, so CMAQ isn't in the picture. So what component of the SRW App uses the MERRA2 dataset?
Collaborator
Author
There was a problem hiding this comment. @JeffBeck-NOAA, if I understand correctly, it is used in thompson_mynn_lam3km now but it can be selected by other CCPP suites. @JiliDong-NOAA, is this correct? Can we turn it on/off in the fv3 namelist?
Collaborator
Author
There was a problem hiding this comment. @gsketefian @JeffBeck-NOAA , I'll put a flag to turn on/off MERRA2 like 'DO_MERRA' into the regional workflow soon. |
||
| # | ||
| #----------------------------------------------------------------------- | ||
| # | ||
| print_info_msg "$VERBOSE" " | ||
| Copying MERRA2 aerosol climatology data files from system directory | ||
| (FIXaer/FIXlut) to a subdirectory (FIXclim) in the experiment directory: | ||
| FIXaer = \"${FIXaer}\" | ||
| FIXlut = \"${FIXlut}\" | ||
| FIXclim = \"${FIXclim}\"" | ||
|
|
||
| check_for_preexist_dir_file "${FIXclim}" "delete" | ||
| mkdir_vrfy -p "${FIXclim}" | ||
|
|
||
| cp_vrfy "${FIXaer}/merra2.aerclim"*".nc" "${FIXclim}/" | ||
| cp_vrfy "${FIXlut}/optics"*".dat" "${FIXclim}/" | ||
| # | ||
| #----------------------------------------------------------------------- | ||
| # | ||
| # Copy templates of various input files to the experiment directory. | ||
| # | ||
| #----------------------------------------------------------------------- | ||
|
|
@@ -609,8 +628,7 @@ print_info_msg "$VERBOSE" " | |
| cp_vrfy "${FIELD_TABLE_TMPL_FP}" "${FIELD_TABLE_FP}" | ||
|
|
||
| print_info_msg "$VERBOSE" " | ||
| Copying the template NEMS configuration file to the experiment directory..." | ||
| cp_vrfy "${NEMS_CONFIG_TMPL_FP}" "${NEMS_CONFIG_FP}" | ||
| # | ||
| # Copy the CCPP physics suite definition file from its location in the | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -62,8 +62,6 @@ FV3_HRRR: | |
| kord_wz: 9 | ||
| nord_tr: 2 | ||
| nrows_blend: 10 | ||
| gfs_physics_nml: | ||
| <<: *gsd_sar_phys | ||
| cdmbgwd: [3.5, 1.0] | ||
|
|
@@ -287,6 +285,52 @@ FV3_GFS_v15p2: | |
| ldebug: False | ||
| surf_map_nml: | ||
|
|
||
| FV3_GFS_v15_thompson_mynn_lam3km: | ||
| atmos_model_nml: | ||
| avg_max_length: 3600.0 | ||
| fv_core_nml: | ||
| agrid_vel_rst: true | ||
| full_zs_filter: !!python/none | ||
| n_sponge: 9 | ||
| npz_type: '' | ||
| rf_fast: false | ||
| sg_cutoff: 10000.0 | ||
| vtdm4: 0.02 | ||
| gfs_physics_nml: | ||
| avg_max_length: 3600.0 | ||
| cdmbgwd: [0.88, 0.04] | ||
| do_deep: false | ||
| do_mynnsfclay: true | ||
| do_ugwp: false | ||
| fhswr: 900.0 | ||
| fhlwr: 900.0 | ||
| iaer: 1011 | ||
| iccn: 2 | ||
| icliq_sw: 2 | ||
| imfdeepcnv: 2 | ||
| imfshalcnv: 2 | ||
| iopt_alb: 2 | ||
| iopt_btr: 1 | ||
| iopt_crs: 1 | ||
| iopt_dveg: 2 | ||
| iopt_frz: 1 | ||
| iopt_inf: 1 | ||
| iopt_rad: 1 | ||
| iopt_run: 1 | ||
| iopt_sfc: 1 | ||
| iopt_snf: 4 | ||
| iopt_stc: 1 | ||
| iopt_tbot: 2 | ||
| iovr: 3 | ||
| ldiag_ugwp: false | ||
| lgfdlmprad: false | ||
| lsm: 1 | ||
| lsoil_lsm: !!python/none | ||
| ltaerosol: false | ||
| xkzminv: 0.3 | ||
| xkzm_m: 1.0 | ||
| xkzm_h: 1.0 | ||
|
|
||
| FV3_GFS_v16: | ||
|
Collaborator
There was a problem hiding this comment. @chan-hoo, This SDF won't work with RAP/HRRR-based ICs unless "nstf_name" is 2, 1, 0, 0, 0. Does it need to be 2, 0, 0, 0, 0, or can we change it?
Collaborator
There was a problem hiding this comment. I believe that switching the second flag in nstf_name from 0 to 1 means that the NSST data from the surface data file will not be read into the model. If this is not desired/needed, I don't see an issue with changing nstf_name to 2,1,0,0,0
Collaborator
Author
There was a problem hiding this comment. @BenjaminBlake-NOAA, do you have an answer to Jeff's comment? I'll test [2,1,0,0,0] with both FV3GFS and RAP/HRRR.
Collaborator
There was a problem hiding this comment. @chan-hoo I think we added comments at the same time :)
Collaborator
There was a problem hiding this comment. Thanks, @BenjaminBlake-NOAA, @chan-hoo, it looks like we need a switch in the workflow to change the values of nstf_name based on the external model data being used for ICs. Since we don't have that at the moment, the easiest solution is to set all suites to 2,1,0,0,0, in which case, I believe FV3 will spin up its own NSST values.
Collaborator
Author
There was a problem hiding this comment. Thanks, @BenjaminBlake-NOAA. I'll test them.
Collaborator
There was a problem hiding this comment. @JeffBeck-NOAA Yes I think that's right about FV3 spinning up its own NSST values
Collaborator
Author
There was a problem hiding this comment. @JeffBeck-NOAA, @BenjaminBlake-NOAA, both FV3GFS and RAP/HRRR works well with 2,1,0,0,0. |
||
| cires_ugwp_nml: | ||
| launch_level: 27 | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.