Feature/rrfs dev2#22
Conversation
…dules, xml generation
1. preprocess for METAR cloud 2. preprocess for NASA LaRC cloud 3. Standalone No-Var cloud analysis.
| test $(find <cyclestr offset="-{{ extrn_mdl_lbcs_offset_hrs }}:00:00">{{ extrn_mdl_sysbasedir_lbcs }}/@Y@m@d@H/postprd</cyclestr> \ | ||
| test $(find <cyclestr offset="-{{ extrn_mdl_lbcs_offset_hrs }}:00:00">{{ extrn_mdl_sysbasedir_lbcs }}/@Y@m@d@H/postprd/</cyclestr> \ | ||
| -name wrfnat_rr_[0-3][0-9].grib2 -mmin +5 | wc -l) \ | ||
| == 40 |
There was a problem hiding this comment.
This dependency is only satisfied if the RAP forecast length is 39 hours (0 thru 39 = 40 files), or if you just happen to catch it when wrfnat_rr_xx.grib2 files have been generated for 40 of the 52 hours. This will probably lead to a lot of missed dacycles. I think you need some logic in here to look for 52 files when processing 03,09,15,21z RAP, or 22 files at all other hours, or a way to look for only the RAP files required to provide LBCs for the given dacycle or full forecast
There was a problem hiding this comment.
Trevor,
I found this issue and manually changed this check to find smaller number of the RAP forecast files in dev2.
I will leave this problem to the future PR. We need to check the forecast length for boundary. We also should let this step start if certain time passed and the scripts should check older RAP cycles for the boundary.
Thanks,
Ming
|
I was able to get most of the pieces in your workflow PR to run successfully in real time. A complete test would take longer just because we don’t have a recent set of “RESTART” files available due to the downtime, so the analysis step fails for the DA cycles due to missing ICs. If you can confirm you got all of this to run successfully in your own tests, I’ll approve the PR to get things moving. Can you just briefly say how you get these runs started (it seems like you need an existing dev2 system or this won't work)? |
|
Also note that this PR depends on the ufs-srweather-app PR, because we need the install.sh fix in order to get the new DA executables where they need to be in /exec (NOAA-GSL/ufs-srweather-app#3) |
|
@hu5970 Could you resolve the conflicts before the review? I think many of them are duplicates from the previous PR. |
christinaholtNOAA
left a comment
There was a problem hiding this comment.
Most of the comments here are related to comments and the duplication of information. I only left a couple of comments, but please consider applying that notion to the other scripts where it makes sense.
| WORKDIR=${CYCLE_DIR}/novar_cldana | ||
| if [ -r ${WORKDIR} ]; then | ||
| rm -fr ${WORKDIR} | ||
| fi |
There was a problem hiding this comment.
This logic is not necessary (same is true in other jobs scripts).
| @@ -0,0 +1,315 @@ | |||
| #!/bin/bash | |||
There was a problem hiding this comment.
The name of this script uses yet another abbreviation of "analysis". Please consider renaming it to use "anl" for clarity and consistency. I'd suggest the same for the executable name, too.
| # | ||
| #----------------------------------------------------------------------- | ||
| # | ||
| # link/copy observation files to working directory |
There was a problem hiding this comment.
This comment is not accurate.
| #----------------------------------------------------------------------- | ||
| # | ||
| $APRUN ./process_Lightning_nc.exe < lightning.namelist > stdout 2>&1 || print_err_msg_exit "\ | ||
| Call to executable to run radar refl process returned with nonzero exit code." |
There was a problem hiding this comment.
This error comment is inaccurate.
|
@TrevorAlcott-NOAA @TrevorAlcott-NOAA Just updated the code based on the comments. Please review. Thanks. |
| @@ -0,0 +1,74 @@ | |||
| MACHINE="jet" | |||
There was a problem hiding this comment.
This file should not be included in this branch.
|
@christinaholtNOAA @TrevorAlcott-NOAA Do you have further review comments on this PR? |
Update dependences in FV3LAM_wflow.xml for cloud analysis.
christinaholtNOAA
left a comment
There was a problem hiding this comment.
@hu5970 Just a couple more comments on duplication of information. I think it looks good after this, though! :)
| The executable specified in EXEC does not exist: | ||
| EXEC = \"$EXEC\" | ||
| Build executable and rerun." | ||
| fi |
There was a problem hiding this comment.
This comment is relevant in many of the ex-scripts, and sometimes multiple times.
Since the name of the executable is left unchanged, please consider the following alternative to address the duplication of information (name of file is here multiple times):
cp_vrfy ${EXEC} ${WORKDIR}
There was a problem hiding this comment.
I will make the change in the next PR.
| else | ||
| print_info_msg "$VERBOSE" "Warning: ${obs_file} does not exist!" | ||
| fi | ||
|
|
There was a problem hiding this comment.
Please consider making the above section a loop to reduce the number of repeats. It's easier to maintain in the long run.
for obs_file in ${obs_files[@]} ; do
if [ -r "${obs_file}" ]; then
cp_vrfy "${obs_file}" $WORKDIR
else
print_info_msg "$VERBOSE" "Warning: ${obs_file} does not exist!"
fi
done
There was a problem hiding this comment.
Need more change here to make it work. Most of the observation files used in DA code have different name from their files name during generation. Need to pair the observation file name with the ones used in the DA first.
|
@christinaholtNOAA Your suggested changes are good. But please merge this PR first. I have another PR now and will make your suggested change in the new PR. Thanks, Ming |
Modify production generation job for real-time parallel
DESCRIPTION OF CHANGES:
This PR is to add the following data preprocess for RRFS:
This PR also adds two analysis applications for RRFS:
TESTS CONDUCTED:
The components are tested:
/mnt/lfs4/BMC/rtwbl/mhu/rrfs/dev2/RRFS_dev2
Will put those components to RRFS_dev2 soon.
ISSUE (optional):
The radar then and no-var cloud analysis are not used in the forecast step. Will link them into the cycling in next PR.
CONTRIBUTORS (optional):
Ming.Hu@noaa.gov