Skip to content

WRF suite

mikebedington edited this page Jun 14, 2022 · 3 revisions

The operational WRF suite has an operations graph of

                run_wrf[-P1D] =>  start_cycle => softlink_run => get_gfs_data 
                get_gfs_data:finish => transfer_gfs_data => write_wps_namelist => run_ungrib
                run_ungrib => run_metgrid => write_run_namelist => adjust_soil_levels => run_real
                run_real => run_wrf => run_netcdf_convert => transfer_for_fvcom => archive_output => housekeeping

There is also a startup app softlink_commmon that , and a monthly task

The transfer_for_fvcom app triggers the FVCOM suite on completion

start_cycle

This is a clock trigger. It completes once the time is past a certain allowing the suite to start running at a particular time point.

softlink_run

This gets the model setup files from the general share directory (ROSEDATA) and softlinks them in to this cycles share directory (ROSEDATAC).

transfer_gfs_data

This first runs the rolling archive tidy up script (proc_gfs_file.sh). This script goest to the gfs data directory on the remote (as passed by the first argument) then deletes directories older than the number of days given by the second argument. It in the 'forecast' directory it soft links to the latest version of the forecast for each hour.

I've had a silent fail when the remote user didn't have the correct permissions to write in the forecast_data directory, this caused an error downstream in adjust_soil_levels but not at this point.

write_wps_namelist

Updates a template of the namelist.wps file (in ./file) with the correct start and end dates, the interval, and the path to the opt_metgrid_tbl file then copies the namelist to the cycle share directory (ROSE_DATAC).

run_ungrib

Runs the linkgrib.sh script (in ./file) passing the location of the GFS rolling archive. This creates a bunch of GRIBFILE.??? files. The wps namelist and Vtable are collected, a bunch of module loaded and ungrib.exe run. This

Once this is complete the FLX files are copied to the cycle share directory (ROSE_DATAC).

run_metgrid

Does some sort of pre processing. Not quite sure what but ungrib, metgrid, and real are provided with WRF. Some more notes are here https://wiki.uio.no/mn/geo/geoit/index.php/Running_WRF

write_run_namelist

Updates a template of the namelist.input file (in ./file) with the correct start and end dates, and number of days to run.

adjust_soil_levels

This does some fiddling in the files to get the number of soil levels correct

Requires ncdump (on ceto load module netcdf, should probably include this in the app relies on it already being loaded at the moment).

This is also sometimes the first place that errors in gfs dates/run_ungrib/run_metgrid appear as it requires the met_d03* files which can fail to be created earlier but somehow don't throw errors.

run_real

More preprocessing

run_wrf

Runs WRF

run_netcdf_convert

Converts output files from netcdf3 to netcdf4

transfer_for_fvcom

Creates the fvcom useable version of the output (using wrf_to_fvcom_ceto which needs to be in the global bin folder) and then puts them in a common directory to be available for when fvcom runs

archive_output

Moves output from ceto to the sthenno directories

housekeeping

Removes the larger files from within the ~/cylc-run/wrf/share/cycle/[date] directories on ceto