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

Analysis Nudging

Chihiro

New member
Dear all,

In my simulation, I need to use analysis nudging to improve wind and temperature

I set it according to the examples.namelist,but there was such an error,in the course of my operation.This was my firt time to use grid nudging.Would you please kindy advise me?

Please kindly advise me on this issue.
Thanks a lot in advance.
 

Attachments

  • namelist.input
    6.3 KB · Views: 2
  • rsl.error.0000
    470.4 KB · Views: 3
@Chihiro
The error message is:

Code:
**WARNING** Time in input file not equal to time on domain **WARNING**
 **WARNING** Trying next time in file wrffdda_d01 ...
           2  input_wrf: wrf_get_next_time current_date: 2020-07-10_18:00:00 Status =           -4
d01 2020-06-30_06:01:48  ---- ERROR: Could not find matching time in input file wrffdda_d01
NOTE:       1 namelist vs input data inconsistencies found.
-------------- FATAL CALLED ---------------

Do you have a "wrffdda_d01" file in your running directory? If so, issue the following and then attach the times.txt file so I can take a look:

Code:
ncdump -v Times wrffdda_d01 >& times.txt
 
@Chihiro
The error message is:

Code:
**WARNING** Time in input file not equal to time on domain **WARNING**
 **WARNING** Trying next time in file wrffdda_d01 ...
           2  input_wrf: wrf_get_next_time current_date: 2020-07-10_18:00:00 Status =           -4
d01 2020-06-30_06:01:48  ---- ERROR: Could not find matching time in input file wrffdda_d01
NOTE:       1 namelist vs input data inconsistencies found.
-------------- FATAL CALLED ---------------

Do you have a "wrffdda_d01" file in your running directory? If so, issue the following and then attach the times.txt file so I can take a look:

Code:
ncdump -v Times wrffdda_d01 >& times.txt
Hi, I think I made a low-level mistake, I found a post, someone and I made the same mistake, this is the time step and history output time is not caused by the integer relationship, the time step is changed to 150 s after the problem is ruled out.
 
Top