Hi,
I am using WRF to downscale hourly ERA5 data in 2016. I read that it is best practice to do short model runs, e.g., 365 runs for 1 day, where each run is 36 hours long and the first 12 hours are spin-up time. I read that WRF needs this re-initialization in order not to diverge too much from the upper-level meteorological fields, which provide the boundary conditions.
From WPS, I get hourly met_em files, so I am wondering why I need this re-initialization of WRF, as wrf.exe gets input from the boundary conditions through the met_em files for every hour separately? How can it diverge from the boundary conditions if it gets input every hour? Or what am I missing?
Any help would be appreciated.
I am using WRF to downscale hourly ERA5 data in 2016. I read that it is best practice to do short model runs, e.g., 365 runs for 1 day, where each run is 36 hours long and the first 12 hours are spin-up time. I read that WRF needs this re-initialization in order not to diverge too much from the upper-level meteorological fields, which provide the boundary conditions.
From WPS, I get hourly met_em files, so I am wondering why I need this re-initialization of WRF, as wrf.exe gets input from the boundary conditions through the met_em files for every hour separately? How can it diverge from the boundary conditions if it gets input every hour? Or what am I missing?
Any help would be appreciated.