WRF FDDA Best Practices?

Topics specifically related to any of the WRF runtime options, such as SST update, DFI, nudging, restarts, global runs, adaptive time step, ndown.exe, tc.exe, moving nest, etc.
Post Reply
Posts: 3
Joined: Fri Oct 23, 2020 12:19 am

WRF FDDA Best Practices?

Post by rconrick » Tue May 11, 2021 8:27 pm

Hi all,

I'm wondering if anyone can offer or point me to some best practices for using WRF's FDDA nudging options.
Our operational WRF runs use a 36-12-4-1.33 km configuration with nudging on the outer 36km domain.

For my research runs, I'm using a 12 km domain (nudged) with a 4 km domain nested within (not nudged). These are generally short (case study) simulations of 24-48 hours, but I'd like to match observations/analysis as closely as possible.

Is there any advice out there about whether this 12-4 km setup is okay? Or should I ditch the nudging entirely?


Ming Chen
Posts: 1596
Joined: Mon Apr 23, 2018 9:42 pm

Re: WRF FDDA Best Practices?

Post by Ming Chen » Wed May 12, 2021 11:16 pm

Please take a look at the website: https://www2.mmm.ucar.edu/wrf/users/doc ... chap7.html
where you can find detailed introduction how to do FDDA, whether ad when FDDA should be conducted for nested domain. etc.
In generally, if you have dense, high-quality observations over your model domain, then FDDA is a good option that may help to improve your simulation. The 12km-4km setting is commonly used in many case studies, and I believe it is appropriate.
WRF Help Desk

Post Reply

Return to “Special Running Options”