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.

please follow the official guide here

1. Go to coupling-automator, and type make

2. It creates the WRF-SUEWS folder to compile (name of the folder depends on what you specify here)

3. load JASMIN compilers: module load intel/20.0.0

4. In the created folder, type ./configure. This is for configuration of WRF-SUEWS. Choose number 15 for the compiler (as of WRFv4 this refers to standard intel compiler) and basic option for the nesting.

5. Then you need compile the code: ./compile em_real >& compile.log&. For this, you can submit the job file by sbatch sb-compile.sh in the compilation folder (specified by path_working in automate_main.py).

6. 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.

7. You also need to copy namelist.suews to the same location.

8. Use LANDUSE.TBL in ./test/em_real to change the albedo associated with Urban areas (number 13 for MODIFIED_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)

9. namelist.input should also be modified to be consistent for WRF-SUEWS. See examples here (specially the sf_surface_physics = 9 which specifies to use SUEWS as the LSM).

10. 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).