SIMULATION START TIME mismatch

[Gulnaaz]

I am using WRF to simulate a real case.I have given the start time as 2024/12/01_00:00:00.The simulation is for 23 hours.While running ./wrf.exe, my simulation terminates with the error as shown
Input data is acceptable to use: wrfinput_d01
CURRENT DATE = 2024-12-01_00:00:00
SIMULATION START DATE = 2016-10-06_00:00:00
Time in file: 2016-10-06_00:00:00
Time on domain: 2024-12-01_00:00:00
**WARNING** Time in input file not equal to time on domain **WARNING**
**WARNING** Trying next time in file wrfinput_d01 ...
1 input_wrf: wrf_get_next_time current_date: 2016-10-06_00:00:00 Status = -4
---- ERROR: Could not find matching time in input file wrfinput_d01
NOTE: 1 namelist vs input data inconsistencies found.
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 1307
NOTE: Please check and reset these options
I have checked the namelist.input file and everything seems fine.Kindly help.
I have attached the required files.

 

[kwerner]

Hi,
Did real.exe run successfully? If so, can you issue the following and then attach the ncdump.txt file? Thanks!

ncdump -v Times wrfinput_d01 >& ncdump.txt

Can you think of any reason why wrf would be looking for a 2016 file, when you're running a 2024 case? Are there any files in your running directory that are specific to a 2016 date?

 

[Gulnaaz]

Thanks for your reply.I have attached the ncdump.txt file.The date is 2016-10-06.
Before running 2024 case, I had run the case for 2016.Although I have changed the date in namelist.wps and namelist.input but the issue persists.

 

[kwerner]

Thanks for sending that. At the end of the ncdump.txt file, it shows that the wrfinput_d01 file was initiated for 2016.

 Times =       
  "2016-10-06_00:00:00" ;
}

This must be the older wrfinput file from the previous case. Remove that file (and the wrfbdy_d01 file) from the wrf running directory and re-run real.exe to produce the input and boundary condition files for the new case.