Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

Obs Nudging output in rsl.error.0000

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.


New member
Could someone explain what each of the variables are displaying in the Obs nudging section of this rsl.error.0000 file?

Timing for main: time 2018-03-12_23:40:00 on domain 1: 3.00805 elapsed seconds
OBS NUDGING: Reading new obs for time window TBACK = 5.000 TFORWD = 6.333 for grid = 4
0-------------EOF REACHED FOR NVOL = 64 AND XTIME = 340.00-------------------
closed fdda file for inest= 4 0
****** CALL IN4DOB AT KTAU = 3672 AND XTIME = 340.00: NSTA = 0 ******
Timing for main: time 2018-03-12_23:40:05 on domain 4: 0.11221 elapsed seconds

I have a feeling that my observations are not being read in. Is NSTA the number of stations being read in?
Yes, that is what that number means. For additional information, take a look at the README.obs_fdda file in the WRF/test/em_real directory. It doesn't specifically say what NSTA means, but there may be some information in there that's useful to you. If you are still experiencing problems, can you attach the namelist.input file you're using, along with your rsl.out.0000 file, and let us know which version of WRF you are using? Thanks!
Just to close the loop on this...

Embarrassingly my domain just missed where the observations were located, so naturally they were not being read in.

Thanks for the advice though!
I'm so glad you were able to figure it out! Don't be embarrassed. These kinds of things happen to all of us. Thanks for updating the post.