-
Notifications
You must be signed in to change notification settings - Fork 58
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Update hycom.py and ww3.py to properly wait for GFS grib2 files and
with proper log/error information; The wallclock limits for jhafs_ocn_prep.ecf and jhafs_wav_prep.ecf are also updated as 30 min * Update exhafs_output.sh to use correct grib2 idx format for the swath grib2 file * Sync NCO SPA's (Simon Shiao) changes from HAFSv1 implementation testing - Update MAILTO in jhafs_output.ecf and JHAFS_OUTPUT as sdm@noaa.gov (same as HWRF) - Move the ecf/scripts/*.ecf into ecf/*.ecf - Some ecf manual information were added in jhafs_cleanup.ecf, jhafs_msg_check.ecf and launch/jhafs_launch.ecf - Latest modifications in hafs ecf suite definition files - Update parm/transfer/transfer_hafs_hfsb_1.list - Update to export NCP=cpfs for the gempak job (since the downstream MAG does not has the capability of wait/check the HAFS gempak products)
- Loading branch information
1 parent
762dde5
commit c4df479
Showing
50 changed files
with
15,170 additions
and
352 deletions.
There are no files selected for viewing
File renamed without changes.
File renamed without changes.
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,71 @@ | ||
#PBS -N %RUN%_msg_check_%CYC%%VER:""% | ||
#PBS -j oe | ||
#PBS -S /bin/bash | ||
#PBS -q %QUEUE% | ||
#PBS -A %PROJ%-%PROJENVIR% | ||
#PBS -l walltime=00:15:00 | ||
#PBS -l place=vscatter,select=1:ncpus=1:mpiprocs=1:ompthreads=1 | ||
#PBS -l debug=true | ||
|
||
model=hafs | ||
export NET="%NET%" | ||
export RUN="%RUN%" | ||
export cyc="%CYC%" | ||
%include <head.h> | ||
%include <envir-p1.h> | ||
|
||
export TOTAL_TASKS='1' | ||
export NCTSK='1' | ||
export OMP_THREADS='1' | ||
|
||
module list | ||
|
||
export EMAIL_SDM=YES | ||
export MAILFROM=${MAILFROM:-"nco.spa@noaa.gov"} | ||
export MAILTO=${MAILTO:-"sdm@noaa.gov,nco.spa@noaa.gov,ncep.sos@noaa.gov"} | ||
|
||
${HOMEhafs}/jobs/JHAFS_MSG_CHECK | ||
|
||
%include <tail.h> | ||
|
||
%manual | ||
TASK msg_check | ||
|
||
PURPOSE: Check for hurricane messages. | ||
|
||
This job will check if hurricane message files are generated in time, and if | ||
there is active storm while the messages is not present yet in the specic time | ||
closed to the cycle, an alert email will be sent out to SDM to alert for the | ||
setup_hurricane. | ||
|
||
|
||
TROUBLESHOOTING | ||
|
||
This job will rarely fail since it has little to do; it just sets up | ||
some directories and makes configuration files. If this job fails, it | ||
is likely due to a hardware or other system issue, with one exception... | ||
|
||
PROBLEM: Why is there no storm? | ||
|
||
The launcher does whatever the NOAA SDM tells it to do. The NOAA SDM | ||
uses a script called setup_hurricane to create message files read by | ||
the launcher job's JHAFS_LAUNCH script. If the launcher job decided | ||
not to run a storm, then that means the SDM told it not to. If there | ||
should have been a storm, then it likely means there was a | ||
communication problem, preventing data from getting from NHC or JTWC | ||
to the NOAA SDM. | ||
|
||
For NHC/CPHC storms, the NOAA SDM has a direct line to the on-call | ||
NHC/CPHC person, who can confirm the absence of a storm. It may then | ||
be possible to manually edit the message and nstorms files to add the | ||
storm in. Alternatively, you could rerun setup_hurricane, but that | ||
may change storm priorities. In that case, you must rerun the entire | ||
HAFS cycle (all storm slots). All of this is technical possibility; | ||
there may be procedural reasons why this cannot be done. | ||
|
||
For JTWC storms, the NOAA SDM has the direct line to the JTWC duty | ||
officer, but there isn't much that can be done. JTWC lacks any way to | ||
send vitals after the T+3 deadline. Hence, a JTWC storm that is | ||
missed, is missed. | ||
|
||
%end |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,96 @@ | ||
#PBS -N %RUN%%STORMNUM%_launch_%CYC%%VER:""% | ||
#PBS -j oe | ||
#PBS -S /bin/bash | ||
#PBS -q %QUEUE% | ||
#PBS -A %PROJ%-%PROJENVIR% | ||
#PBS -l walltime=00:15:00 | ||
#PBS -l place=vscatter,select=1:ncpus=1:mpiprocs=1:mem=10G | ||
#PBS -l debug=true | ||
|
||
model=hafs | ||
export NET="%NET%" | ||
export RUN="%RUN%" | ||
export cyc="%CYC%" | ||
%include <head.h> | ||
%include <envir-p1.h> | ||
|
||
export storm_num="%STORMNUM%" | ||
|
||
module load PrgEnv-intel/${PrgEnv_intel_ver} | ||
module load craype/${craype_ver} | ||
module load intel/${intel_ver} | ||
module load cray-mpich/${cray_mpich_ver} | ||
module load cray-pals/${cray_pals_ver} | ||
module load hdf5/${hdf5_ver} | ||
module load netcdf/${netcdf_ver} | ||
module load python/${python_ver} | ||
module load crtm/${crtm_ver} | ||
module load udunits/${udunits_ver} | ||
module load gsl/${gsl_ver} | ||
module load nco/${nco_ver} | ||
module list | ||
|
||
${HOMEhafs}/jobs/JHAFS_LAUNCH | ||
|
||
%include <tail.h> | ||
|
||
%manual | ||
TASK launch | ||
|
||
PURPOSE: Creates initial directory structure and configures the | ||
rest of the workflow for one storm. | ||
|
||
This job will delete and recreate the $DATA work area for one HAFS | ||
storm. It sets several flags to turn on and off parts of the | ||
workflow, or disable the entire workflow if there is no storm. All | ||
logic is triggered by the message file sent by the SDM via | ||
setup_hurricane. | ||
|
||
Labels: | ||
|
||
stormN - storm1-storm7 for HFSA, storm1-storm5 for HFSB; label tells | ||
whether a storm is to be run. IF the storm is to be run, it tells | ||
what the storm is, and who sent it (NHC or JTWC). | ||
|
||
Events: | ||
|
||
NoStorm - set if no storm is to be run. The rest of the workflow sees | ||
the event and automatically completes via ecFlow completion clauses. | ||
|
||
Ocean - for both HFSA and HFSB have ocean coupling with HYCOM | ||
|
||
Wave - for wave coupling, (only HFSA will run it for NHC basin storms) | ||
|
||
Analysis - for both HFSA and HFSB will set it for NHC basin storms; | ||
for HFSA with JTWC storms (data assimilation is turned off) | ||
|
||
TROUBLESHOOTING | ||
|
||
This job will rarely fail since it has little to do; it just sets up | ||
some directories and makes configuration files. If this job fails, it | ||
is likely due to a hardware or other system issue, with one exception... | ||
|
||
PROBLEM: Why is there no storm? | ||
|
||
The launcher does whatever the NOAA SDM tells it to do. The NOAA SDM | ||
uses a script called setup_hurricane to create message files read by | ||
the launcher job's JHAFS_LAUNCH script. If the launcher job decided | ||
not to run a storm, then that means the SDM told it not to. If there | ||
should have been a storm, then it likely means there was a | ||
communication problem, preventing data from getting from NHC or JTWC | ||
to the NOAA SDM. | ||
|
||
For NHC/CPHC storms, the NOAA SDM has a direct line to the on-call | ||
NHC/CPHC person, who can confirm the absence of a storm. It may then | ||
be possible to manually edit the message and nstorms files to add the | ||
storm in. Alternatively, you could rerun setup_hurricane, but that | ||
may change storm priorities. In that case, you must rerun the entire | ||
HAFS cycle (all storm slots). All of this is technical possibility; | ||
there may be procedural reasons why this cannot be done. | ||
|
||
For JTWC storms, the NOAA SDM has the direct line to the JTWC duty | ||
officer, but there isn't much that can be done. JTWC lacks any way to | ||
send vitals after the T+3 deadline. Hence, a JTWC storm that is | ||
missed, is missed. | ||
|
||
%end |
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
0
ecf/scripts/post/jhafs_unpost.ecf → ecf/post/jhafs_unpost.ecf
100644 → 100755
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.