1 / 27

Running the GFS Parallel System Non-Hybrid EnKF on Zeus

Running the GFS Parallel System Non-Hybrid EnKF on Zeus. NOAA/NWS/NCEP/EMC. This presentation contains…. Overview of GFS Parallel System structure Running an experiment on Zeus (DEMO) Terms to know Directories Configuration file Rlist & appended rlist Model input Submitting job

augustin
Download Presentation

Running the GFS Parallel System Non-Hybrid EnKF on Zeus

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Running the GFS Parallel System Non-Hybrid EnKF on Zeus NOAA/NWS/NCEP/EMC

  2. This presentation contains… • Overview of GFS Parallel System structure • Running an experiment on Zeus (DEMO) • Terms to know • Directories • Configuration file • Rlist & appended rlist • Model input • Submitting job • Experiment/job progress • Model output • Troubleshooting

  3. Documentation & Help Website: http://www.emc.ncep.noaa.gov/GFS/exp.php Listserv (Glopara Support): NCEP.List.EMC.Glopara-Support@noaa.gov In Person: Stop by my cube next to the 2nd floor breakroom, I don’t bite 

  4. Global Forecast System Suite in Operations GFS Global Forecast System suite of jobs, which encompasses the gfs and gdas gfs gdas The "early run“.In real time, the early run, is initiated ~2 hrs and 45 min after the cycle time. The early gfs run gets the full forecasts delivered in a reasonable amount of time. GDAS Global Data Assimilation System The "final run", initiated ~6 hrs after the cycle time. Delayed gdas allows for the assimilation of later arriving data. Includes a short forecast (9 hrs) to provide the first guess to both the gfs and gdas for the following cycle. * Times are approximate

  5. Global Model Parallel Sequencing psub & reconcile.sh prep prep anal configuration file & rlist anal 2nd Segment? fcst1 angu gdas gfs post1 fcst2 fcst1 vrfy post2 post1 arch vrfy vrfy update cycle hour run GFS this cycle? arch arch

  6. GFS Experiment Setup (DEMO) • Terms to know • Directories • Configuration file setup • Model input • Submitting job • Experiment/job progress • Model output

  7. GFS Experiment Setup Terms to know:

  8. Demo time… Experiment prtest2: • CDATE = 2011070100 • CDUMP = gdas • CSTEP = fcst1 • gfs_cyc = 4 (all cycles run gfs) • DOENKF & DOHYBVAR = NO (3DVAR DA) • EDATE = 2011070112 • EDUMP = gdas • ESTEP = prep

  9. Global Model Parallel Sequencing psub & reconcile.sh ESTEP prep prep anal configuration file & rlist anal 2nd Segment? fcst1 angu CDUMP gdas gfs EDUMP post1 fcst2 fcst1 CSTEP vrfy post2 post1 arch vrfy vrfy update cycle hour run GFS this cycle? arch arch

  10. Global Model Parallel Sequencing psub & reconcile.sh prep prep anal configuration file & rlist anal 2nd Segment? fcst1 gfs_cyc=4 angu gdas gfs post1 fcst2 fcst1 CSTEP (cyc=00) vrfy post2 post1 arch now cyc=06 vrfy vrfy update cycle hour gfs_cyc=4 & cyc=06 So YES run GFS this cycle? arch arch

  11. Global Model Parallel Sequencing psub & reconcile.sh prep prep anal configuration file & rlist anal 2nd Segment? fcst1 gfs_cyc=1 angu gdas gfs post1 fcst2 fcst1 CSTEP (cyc=00) vrfy post2 post1 arch now cyc=06 vrfy vrfy update cycle hour gfs_cyc=1 & cyc=06 So NO run GFS this cycle? arch arch

  12. Sign onto Zeus… • ssh zeus.rdhpcs.noaa.gov(alternate: zeus.princeton.rdhpcs.noaa.gov) • Enter user name (First.Last / $LOGNAME) • Enter PIN+PASSCODE Example w/ PIN=123456 & PASSCODE from RSA token=778 899 …so PIN+PASSCODE  123456778899 Hit Enter and arrive at home location (/home/$LOGNAME) Example: /home/Kate.Howard

  13. Environmental Settings If not already configured…setup a .cshrc or .bashrc file See example under /home/Kate.Howard -rwxrwxrwx 1 Kate.Howard global 2339 Jun 1 12:50 .cshrc Find out which groups you are in: id First.Last (Example: id Kate.Howard) [Kate.Howard@fe4 ~]$ id Kate.Howard uid=30008(Kate.Howard) gid=11904(global) groups=11806(climate),11807(cmp),11904(global),11812(gm),11827(ptmp),511(rstprod),11830(stmp)

  14. Setup Experiment Directories Setup $EXPDIR & $COMROT for prtest2 $EXPDIR (save) Contains config file and other small text files Example: /$SCRATCH#/portfolios/NCEPDEV/$GROUP/save/$LOGNAME/…/pr$PSLOT /scratch2/portfolios/NCEPDEV/global/save/Kate.Howard/TUTORIAL/prtest2 $COMROT (noscrub, scrub, or ptmp) Contains large data files and model input/output Example: /scratch2/portfolios/NCEPDEV/global/noscrub/Kate.Howard/TUTORIAL/prtest2

  15. Configuration File • List of variables to be used in experiment and their configuration/value. The user can change these variables for their experiment. • Short list of important variables to check with each new run: • $PSLOT • The E’s ($EDATE, $EDUMP, $ESTEP) • $EXPDIR & $COMROT • Place a copy of a config file in $EXPDIR

  16. Setup Configuration File Check or alter the following variables: • $PSLOT • $EXPDIR • $COMROT • $ACCOUNT • $EDATE (and maybe $EDUMP & $ESTEP) • $gfs_cyc • ARCH variables, $ARCDIR & $ATARDIR • $DOENKF & $DOHYBVAR • VSDB variables

  17. Initial Conditions in $COMROT Acquire initial condition files and place in $COMROT: • biascr.$CDUMP.$CDATE • satang.$CDUMP.$CDATE • sfcanl.$CDUMP.$CDATE • siganl.$CDUMP.$CDATE Places to acquire ICs: • HPSS • Online archive • Someone else’s experiment/parallel

  18. Submitting the GFS While in $EXPDIR, using the psub script from config file, type the following on the command line: $PSUB $CONFIG $CDATE $CDUMP $CSTEP Where:$PSUB = psub script with full location path$CONFIG = name of configuration file (assumes the file is in your $EXPDIR)$CDATE = YYYYMMDDCC initial/starting year (YYYY), month (MM), day (DD), and cycle (CC) for model run$CDUMP = dump (gdas or gfs) to start run$CSTEP = initial model run step (see flow diagram above for options) …/bin/psub_zeuspara_config 2011070100 gdas fcst1

  19. Monitoring Experiment • Runlog in $EXPDIRtail –f pr$PSLOT.runlogEx: tail –f prtest1.runlog • myjobs (mj) [Kate.Howard@fe4 prtest1]$ mj 2268635 492 R Tue Jun 12 12:15:30 2012 TUTORIAL/prtest1/test12011070106gdasanal 2269631 244 R Tue Jun 12 13:02:04 2012 TUTORIAL/prtest1/test12011070106gfsfcst1_0 2269645 20 R Tue Jun 12 13:02:48 2012 TUTORIAL/prtest1/test12011070106gfspost1_0

  20. Rlist rlist & append.rlist • List of data to be used in experiment. • Created in reconcile.sh (when pmkr script runs) if it does not already exist at beginning of experiment. • If you do not want to use the rlist generated by reconcile.sh, you can start with an existing rlist and modify it by hand as needed. • Some samples exist in the exp subdirectory. • The pmkr script does not account for files to be archived (eg, ARCR, ARCO, ARCA entries). • The current standard practice is to put those entries in a separate file, append.rlist • Then define variable $append_rlist to point to this file. • If the variable $ARCHIVE is set to YES (default is NO), this file is then appended automatically to the rlist by reconcile.sh, but only when the rlist is generated on the fly by pmkr. • So, for example, if you submit the first job, which creates an rlist and then you realize that your ARCx entries are missing, creating the append_rlist after the fact won't help unless you remove the now existing rlist. If you delete the errant rlist (and set $ARCHIVE to YES, the next job you submit will see that the rlist does not exist, create it using pmkr, then append the $append_rlist file.

  21. Runlog pr$PSLOT.runlog • Text file with log of experiment information pertaining to each step of the parallel system (prep, anal, angu, fcst1, etc…) • Example of contents (first 6 lines): 2012/06/12 Tue 15:29:52 GMT OK: test12011070100gdasfcst1 submitted 2012/06/12 Tue 15:31:40 GMT OK: test12011070100gdasfcst1 begun 2012/06/12 Tue 15:31:42 GMT OK: test12011070100gdaspost1 submitted 2012/06/12 Tue 15:32:40 GMT OK: test12011070100gdaspost1 begun 2012/06/12 Tue 15:37:16 GMT OK: test12011070100gdasfcst1 ended  2012/06/12 Tue 16:04:25 GMT OK: test12011070100gdaspost1 ended  • Submitted, begun, ended….or failed 2012/06/12 Tue 15:37:16 GMT ERROR: test12011070100gdasfcst1 failed 

  22. GFS Output - Dayfiles Text output files containing details of run, as well as error messages for troubleshooting, found in $COMROT Naming convention: $PSLOT$CDATE$CDUMP$CSTEP.dayfile Example: test12011070100gdasfcst1.dayfile $PSLOT=test1 $CDATE=2011070100 (YYYYMMDDCC) $CDUMP=gdas $CSTEP=fcst1

  23. GFS Output - Data http://www.emc.ncep.noaa.gov/GFS/exp.php#All_files

  24. Plotting Output - GrADS grib2ctl grib2ctl –verf FILENAME > FILENAME.ctl gribmap gribmap –i FILENAME.ctl Open GrADS grads open FILENAME.ctl

  25. Verification (VSDB) For NOAA Zeus users: • copy the driver/scratch2/portfolios/NCEPDEV/global/save/Fanglin.Yang/VRFY/vsdb/vsdbjob_submit.sh • and parameter setting script/scratch2/portfolios/NCEPDEV/global/save/Fanglin.Yang/VRFY/vsdb/setup_envs.sh • make necessary changes following the instruction given in the script

  26. Documentation & Help Website: http://www.emc.ncep.noaa.gov/GFS/exp.php Listserv (Glopara Support): NCEP.List.EMC.Glopara-Support@noaa.gov In Person: Stop by my cube next to the 2nd floor breakroom 

  27. Questions?

More Related