Hello WRF Community,
I have been using WRF for the last couple of years, but this is my first attempt at using ndown.exe. I'm following steps mentioned in the WRF Tutorial for running ndown.exe from a 777m domain to 259m domain (https://www2.mmm.ucar.edu/wrf/users/docs/user_guide_v4/v4.0/users_guide_chap5.html#_e._One-way_Nested)
I was able to run wrf.exe for the nested domain (259m) successfully, following every step mentioned in the tutorial. However, while I checked the wrfout variables using ncview, I have found something strange. Most of the variables for the 259m domain have a blank screen except for the initial values. Then I checked wrfinfut, and wrfbdy files and found both of them were looked good. For example, I have attached ncview screen of U for wrfinput, and wrfout for two different times.
To cross-check the ndown process, I have done another one-way nesting simulation from the 2.3km domain to the 777m domain. For this case, I have found everything looks perfect. This makes me confused then what’s wrong with 777m to 259m.
At this point, I am not sure what’s causing the problem. I would be very grateful if someone helps me with this concern.
** I have used Cheyenne computer for these simulations**
P.s.’ I am attaching the namelist.input that I use for ndown and real wrf.
Thanks in advance for your help.
With Kind Regards
Shak
I have been using WRF for the last couple of years, but this is my first attempt at using ndown.exe. I'm following steps mentioned in the WRF Tutorial for running ndown.exe from a 777m domain to 259m domain (https://www2.mmm.ucar.edu/wrf/users/docs/user_guide_v4/v4.0/users_guide_chap5.html#_e._One-way_Nested)
I was able to run wrf.exe for the nested domain (259m) successfully, following every step mentioned in the tutorial. However, while I checked the wrfout variables using ncview, I have found something strange. Most of the variables for the 259m domain have a blank screen except for the initial values. Then I checked wrfinfut, and wrfbdy files and found both of them were looked good. For example, I have attached ncview screen of U for wrfinput, and wrfout for two different times.
To cross-check the ndown process, I have done another one-way nesting simulation from the 2.3km domain to the 777m domain. For this case, I have found everything looks perfect. This makes me confused then what’s wrong with 777m to 259m.
At this point, I am not sure what’s causing the problem. I would be very grateful if someone helps me with this concern.
** I have used Cheyenne computer for these simulations**
P.s.’ I am attaching the namelist.input that I use for ndown and real wrf.
Thanks in advance for your help.
With Kind Regards
Shak
