WRF-SUEWS coupling project
Make sure you use the following commands after cloning the repo:
git submodule init
git submodule update
These commands update SUEWS repo associated with WRF-SUEWS. Currently, it is an older version of SUEWS than the most up-to-date one.
To compile and Run on JASMIN (as of 12 Oct 2021)
please follow the official guide here
-
Go to
coupling-automator
, and typemake
-
It creates the WRF-SUEWS folder to compile (name of the folder depends on what you specify here)
-
load JASMIN compilers:
module load intel/20.0.0
-
In the created folder, type
./configure
. This is for configuration of WRF-SUEWS. Choose number15
for the compiler (as of WRFv4 this refers to standard intel compiler) andbasic
option for the nesting. -
Then you need compile the code:
./compile em_real >& compile.log&
. For this, you can submit the job file bysbatch sb-compile.sh
in the compilation folder (specified bypath_working
in automate_main.py). -
After compilation of the code, you need to transfer all the
wrf_input
files to the location of main run (usually./test/em_real
). It should include the boundary condition file. -
You also need to copy
namelist.suews
to the same location. -
Use
LANDUSE.TBL
in./test/em_real
to change the albedo associated with Urban areas (number13
forMODIFIED_IGBP_MODIS_NOAH
for both winter and summer. By default it is 15% (0.15). In London case, it is changed to 11% (0.11) based on Ward et al. 2016) -
namelist.input
should also be modified to be consistent for WRF-SUEWS. See examples here (specially thesf_surface_physics = 9
which specifies to use SUEWS as the LSM). -
The rest of steps, are similar to usual WRF runs (running WRF-SUEWS)
To generate the original wrfinput
files (before processing them for WRF-SUEWS), you should follow here. After generating wrfinput
and wrfbdy
, you need to follow pre-processing instructions to modify the input file suitbale for WRF-SUEWS runs
Please refer to this instruction for WRF-SUEWS preprocessing system (WSPS).