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

" Could not find matching time in input file"

BartSmulders

New member
Hi,

I have been trying to run some WRF runs but keep getting the attached rsl.error (same for every processor).
I have already done WRF runs with input file created in WPS from the same original input data (HadGEM2-ES) for the dates 27-3-20* till 31-5-20* which ran without an issue.
But for some reason WRF now stops within 3 seconds only creatins rsl files saying the " time in file" is 27-3-2008.

How can i fix this?

Cheers,
Bart
 

Attachments

  • rsl.error.0001.txt
    2.5 KB · Views: 11
Hi,

I have been trying to run some WRF runs but keep getting the attached rsl.error (same for every processor).
I have already done WRF runs with input file created in WPS from the same original input data (HadGEM2-ES) for the dates 27-3-20* till 31-5-20* which ran without an issue.
But for some reason WRF now stops within 3 seconds only creatins rsl files saying the " time in file" is 27-3-2008.

How can i fix this?

Cheers,
Bart
Can you attach all your rsl.error files and name list files as a tar file please?
 
@BartSmulders
The error message is

Code:
 Time in file: 2008-03-27_12:00:00
 Time on domain: 2008-08-25_12: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: 2008-03-27_12:00:00 Status =           -4
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE:  <stdin>  LINE:     941
 ... Could not find matching time in input file wrfinput_d01
-------------------------------------------

So it looks like the wrfinput* file you have in your WRF running directory has an initial time of 2008-03-27_12:00:00, while your namelist.input file is asking it to process for initial time 2008-08-25_12:00:00

Did you re-run real.exe prior to running wrf for this new date? If you're unsure about your wrfinput file, you can issue the command

Code:
ncdump -v Times wrfinput_d01

to see the time available for the file.
 
@BartSmulders
The error message is

Code:
 Time in file: 2008-03-27_12:00:00
 Time on domain: 2008-08-25_12: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: 2008-03-27_12:00:00 Status =           -4
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE:  <stdin>  LINE:     941
 ... Could not find matching time in input file wrfinput_d01
-------------------------------------------

So it looks like the wrfinput* file you have in your WRF running directory has an initial time of 2008-03-27_12:00:00, while your namelist.input file is asking it to process for initial time 2008-08-25_12:00:00

Did you re-run real.exe prior to running wrf for this new date? If you're unsure about your wrfinput file, you can issue the command

Code:
ncdump -v Times wrfinput_d01

to see the time available for the file.

I am using a single command to run both real.exe and wrf.exe

Code:
mpirun -np 16 ./real.exe
mpirun -np 16 ./wrf.exe

But the date 2008-03-27_12:00:00 is the start data of a run I have done prior (without an issue), but as far as i can see there are no longer any files from that run in the directory I run WRF from anymore.

under "global attributes" when using
Code:
ncdump -v Times wrfinput_d01
It says
:START_DATE = "2008-03-27_12:00:00" ;
:SIMULATION_START_DATE = "2008-03-27_12:00:00" ;

and under "data" it gives "Times = "2008-03-27_12:00:00" ;"

But why does it use this initial time? 😅
 
Last edited:
It is working now (but I have no idea why)
I tried running real.exe separately by commenting out the wrf command, this gave different rsl.error files than the ones I attached above.
These noted that the input files for d03 were missing for the start date.
After edditing the WPS namelist to make sure it was correct I re-ran WPS and real.exe after, which gave no errors.
Then I ran both real.exe and wrf.exe with the code posted above and now it is working fine again.

So if someone knows what the problem could have been I would still be interested in knowing but at least it is working again.

Thank you both for helping trying to find the fix.
 
It is working now (but I have no idea why)
I tried running real.exe separately by commenting out the wrf command, this gave different rsl.error files than the ones I attached above.
These noted that the input files for d03 were missing for the start date.
After edditing the WPS namelist to make sure it was correct I re-ran WPS and real.exe after, which gave no errors.
Then I ran both real.exe and wrf.exe with the code posted above and now it is working fine again.

So if someone knows what the problem could have been I would still be interested in knowing but at least it is working again.

Thank you both for helping trying to find the fix.
Hello,BartSmulders
I encountered a similar problem when I was running WRF-Chem. Do you know how to solve it now?
the message of all rsl.error.00* are include in the 123.txt.
Thank you
 

Attachments

  • 123.txt
    48.1 KB · Views: 6
Top