Skip to content
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

update IC/LBC file paths to match new IC/LBC file structure #766

Merged
merged 3 commits into from
May 26, 2022
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 6 additions & 7 deletions ush/config.community.sh
Original file line number Diff line number Diff line change
Expand Up @@ -15,12 +15,12 @@ DO_ENSEMBLE="FALSE"
NUM_ENS_MEMBERS="2"

CCPP_PHYS_SUITE="FV3_GFS_v16"
FCST_LEN_HRS="48"
FCST_LEN_HRS="6"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JeffBeck-NOAA Do you remember why we had decided to set this to 48 hours originally?

Copy link
Collaborator

@JeffBeck-NOAA JeffBeck-NOAA May 19, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The GST was chosen as 20190615 with a 00Z initialization and 48-hr forecast length to cover two full diurnal cycles, including two days with significant severe storm reports in various parts of the country. There is an increased demand by NWS and NSSL for CAM systems to be run into day two (24-48 hrs) time frames for forecast guidance relative to hazardous weather. The preliminary configuration of the RRFS (the main operational instantiation of the SRW App) will be run out to 60 hrs, four times a day.

Since the GST in the config.community.sh script uses a 25-km domain, I would advocate to keep the 00Z initialization with a 48-hr forecast. That's very computationally inexpensive. It also provides the general user with two days of forecasts to plot/compare.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@EdwardSnyder-NOAA Have you been getting failures later (after 6 hours) into the forecast? Just trying to understand the comment in the PR:

The forecast length was reduced to increase the likelihood of a successful model run.

Copy link
Collaborator

@gsketefian gsketefian May 19, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, I just saw your explanation to @chan-hoo.

LBC_SPEC_INTVL_HRS="6"

DATE_FIRST_CYCL="20190615"
DATE_LAST_CYCL="20190615"
CYCL_HRS=( "00" )
CYCL_HRS=( "18" )
natalie-perlin marked this conversation as resolved.
Show resolved Hide resolved

EXTRN_MDL_NAME_ICS="FV3GFS"
EXTRN_MDL_NAME_LBCS="FV3GFS"
Expand Down Expand Up @@ -59,8 +59,7 @@ RUN_TASK_VX_ENSPOINT="FALSE"
# if on another platform, using other dates, other external models, etc.
# Uncomment the following EXTRN_MDL_*_ICS/LBCS only when USE_USER_STAGED_EXTRN_FILES=TRUE
#
#EXTRN_MDL_SOURCE_BASEDIR_ICS="/scratch2/BMC/det/UFS_SRW_app/v1p0/model_data/FV3GFS"
#EXTRN_MDL_FILES_ICS=( "gfs.pgrb2.0p25.f000" )
#EXTRN_MDL_SOURCE_BASEDIR_LBCS="/path/to/model_data/FV3GFS"
#EXTRN_MDL_FILES_LBCS=( "gfs.pgrb2.0p25.f006" "gfs.pgrb2.0p25.f012" "gfs.pgrb2.0p25.f018" "gfs.pgrb2.0p25.f024" \
# "gfs.pgrb2.0p25.f030" "gfs.pgrb2.0p25.f036" "gfs.pgrb2.0p25.f042" "gfs.pgrb2.0p25.f048" )
#EXTRN_MDL_SOURCE_BASEDIR_ICS="/scratch2/BMC/det/UFS_SRW_App/develop/input_model_data/FV3GFS/grib2/2019061518"
#EXTRN_MDL_FILES_ICS=( "gfs.t18z.pgrb2.0p25.f000" )
#EXTRN_MDL_SOURCE_BASEDIR_LBCS="/scratch2/BMC/det/UFS_SRW_App/develop/input_model_data/FV3GFS/grib2/2019061518"
#EXTRN_MDL_FILES_LBCS=( "gfs.t18z.pgrb2.0p25.f006" )
gspetro-NOAA marked this conversation as resolved.
Show resolved Hide resolved