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

Error Matching time in input file

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.

carinavb

New member
Hello, I have WRFV4, it works ok but sometimes I have the following error

d01 2019-08-02_00:00:00 alloc_space_field: domain 2 , 4477440 bytes allocated
d01 2019-08-02_00:00:00 alloc_space_field: domain 2 , 22999104 bytes allocated
d01 2019-08-02_00:00:00 *** Initializing nest domain # 2 from an input file. ***
d01 2019-08-02_00:00:00 med_initialdata_input: calling input_input
d01 2019-08-02_00:00:00 Input data is acceptable to use: wrfinput_d02
Time in file: 2019-08-01_00:00:00
Time on domain: 2019-08-02_00:00:00
**WARNING** Time in input file not equal to time on domain **WARNING**
**WARNING** Trying next time in file wrfinput_d02 ...
1 input_wrf: wrf_get_next_time current_date: 2019-08-01_00:00:00 Status = -4
d01 2019-08-02_00:00:00 ---- ERROR: Could not find matching time in input file wrfinput_d02
NOTE: 1 namelist vs input data inconsistencies found.
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 1248
NOTE: Please check and reset these options
-------------------------------------------
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0

My namelist.input:
&time_control
start_year = 2019, 2019,
start_month = 08, 08,
start_day = 02, 02,
start_hour = 0, 0,
end_year = 2019, 2019,
end_month = 08, 08,
end_day = 06, 06,
end_hour = 0, 0,
interval_seconds = 21600
input_from_file = .true.,.true.,
history_interval = 180, 60,
frames_per_outfile = 1000, 1000,
restart = .false.,
restart_interval = 7200,
io_form_history = 2
io_form_restart = 2
io_form_input = 2
io_form_boundary = 2
/

&domains
time_step = 60,
time_step_fract_num = 0,
time_step_fract_den = 1,
max_dom = 2,
s_we = 1, 1,
e_we = 33, 31,
s_sn = 1, 1,
e_sn = 41, 40,
s_vert = 1, 1,
e_vert = 35, 35,
p_top_requested = 5000,
num_metgrid_levels = 34,
num_metgrid_soil_levels = 4,
dx = 15000, 5000,
dy = 15000, 5000,
grid_id = 1, 2,
parent_id = 0, 1,
i_parent_start = 1, 17,
j_parent_start = 1, 6,
parent_grid_ratio = 1, 3,
parent_time_step_ratio = 1, 3,
feedback = 1,
smooth_option = 0
/

&physics
physics_suite = 'tropical'
mp_physics = -1, -1,
cu_physics = -1, -1,
ra_lw_physics = -1, -1,
ra_sw_physics = -1, -1,
bl_pbl_physics = -1, -1,
sf_sfclay_physics = -1, -1,
sf_surface_physics = -1, -1,
radt = 30, 30,
bldt = 0, 0,
cudt = 5, 5,
icloud = 1,
num_land_cat = 21,
sf_urban_physics = 0, 0,
/

&fdda
/

&dynamics
hybrid_opt = 2,
w_damping = 0,
diff_opt = 1, 1,
km_opt = 4, 4,
diff_6th_opt = 0, 0,
diff_6th_factor = 0.12, 0.12,
base_temp = 290.
damp_opt = 3,
zdamp = 5000., 5000.,
dampcoef = 0.2, 0.2,
khdif = 0, 0,
kvdif = 0, 0,
non_hydrostatic = .true., .true.,
moist_adv_opt = 1, 1,
scalar_adv_opt = 1, 1,
gwd_opt = 1,
/

&bdy_control
spec_bdy_width = 5,
specified = .true.
/

&grib2
/

&namelist_quilt
nio_tasks_per_group = 0,
nio_groups = 1,
/
What I should check?
I realize that wrfinput_d01 is created by the date, but wrfinput_d02 doesn't.

-rw-r--r-- 1 usuario usuario 3,6M ago 2 11:06 wrfinput_d01
-rw-r--r-- 1 usuario usuario 3,3M ago 1 20:12 wrfinput_d02
I think I have something wrong in my namelist.
Hope someone can help me with this.
Best regards
Carina
 
Carina,
Are you getting this error when running real.exe or wrf.exe? Can you attach the full error log?

If this error is with wrf.exe, can you issue the following:
ncdump -v Times wrfbdy_d01 >& log.wrfbdy
ncdump -v Times wrfinput_d01 >& log.wrfinput_d01
ncdump -v Times wrfinput_d02 >& log.wrfinput_d02

and also attach those 3 log.* files? When you're posting a response, look below the response box for the tab 'Options' and one with 3 horizontal lines. If you click on the one with the 3 lines, that will allow you to attach files. Thanks!
 
Hello, thanks for the answer. I get this erro from wrf.exe.

taskid: 0 hostname: WRF
module_io_quilt_old.F 2931 F
Quilting with 1 groups of 0 I/O tasks.
Ntasks in X 2 , ntasks in Y 4
*************************************
Configuring physics suite 'tropical'

mp_physics: 6 6
cu_physics: 16 16
ra_lw_physics: 4 4
ra_sw_physics: 4 4
bl_pbl_physics: 1 1
sf_sfclay_physics: 91 91
sf_surface_physics: 2 2
*************************************
WRF V4.0 MODEL
*************************************
Parent domain
ids,ide,jds,jde 1 33 1 41
ims,ime,jms,jme -4 23 -4 17
ips,ipe,jps,jpe 1 16 1 10
*************************************
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 17463664 bytes allocated
med_initialdata_input: calling input_input
Input data is acceptable to use: wrfinput_d01
Timing for processing wrfinput file (stream 0) for domain 1: 0.02355 elapsed seconds
Max map factor in domain 1 = 1.02. Scale the dt in the model accordingly.
INPUT LandUse = "MODIFIED_IGBP_MODIS_NOAH"
LANDUSE TYPE = "MODIFIED_IGBP_MODIS_NOAH" FOUND 33 CATEGORIES 2 SEASONS WATER CATEGORY = 17 SNOW CATEGORY = 15
INITIALIZE THREE Noah LSM RELATED TABLES
Skipping over LUTYPE = USGS
LANDUSE TYPE = MODIFIED_IGBP_MODIS_NOAH FOUND 20 CATEGORIES
INPUT SOIL TEXTURE CLASSIFICATION = STAS
SOIL TEXTURE CLASSIFICATION = STAS FOUND 19 CATEGORIES
*************************************
Nesting domain
ids,ide,jds,jde 1 31 1 40
ims,ime,jms,jme -4 27 -4 21
ips,ipe,jps,jpe 1 15 1 10
INTERMEDIATE domain
ids,ide,jds,jde 15 30 4 22
ims,ime,jms,jme 10 31 -1 18
ips,ipe,jps,jpe 13 21 2 8
*************************************
d01 2019-08-04_00:00:00 alloc_space_field: domain 2 , 4477440 bytes allocated
d01 2019-08-04_00:00:00 alloc_space_field: domain 2 , 22999104 bytes allocated
d01 2019-08-04_00:00:00 *** Initializing nest domain # 2 from an input file. ***
d01 2019-08-04_00:00:00 med_initialdata_input: calling input_input
d01 2019-08-04_00:00:00 Input data is acceptable to use: wrfinput_d02
Time in file: 2019-08-03_00:00:00
Time on domain: 2019-08-04_00:00:00
**WARNING** Time in input file not equal to time on domain **WARNING**
**WARNING** Trying next time in file wrfinput_d02 ...
1 input_wrf: wrf_get_next_time current_date: 2019-08-03_00:00:00 Status = -4
d01 2019-08-04_00:00:00 ---- ERROR: Could not find matching time in input file wrfinput_d02
NOTE: 1 namelist vs input data inconsistencies found.
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 1248
NOTE: Please check and reset these options
-------------------------------------------
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0

When I run with max_domain=1 wrf.exe works.
I attach namelist.input and the files you asked.

Best regards

Carina
 

Attachments

  • namelist.input
    3.7 KB · Views: 88
  • wrfbdy.log
    28.7 KB · Views: 79
  • wrfinput_d01.log
    42.9 KB · Views: 88
  • wrfinput_d02.log
    42.9 KB · Views: 70
Carina,
Thank you for sending those. Your namelist (for both domains) is set to begin 2019-08-04_00:00:00. Your wrfinput_d01 file has an initial time of the same thing; however, your wrfinput_d02 file has a start time of 2019-08-03_00:00:00, which is confusing the model. When you ran real.exe, did you have the dates for d02 set differently than for d01? Can you try running real.exe again (not changing the namelist.input file), and see what dates show up in the wrfinput_d01 and wrfinput_d02 files? You can see this information by using the 'ncdump -v Times wrfinput_d01' (for e.g.) commands I gave in the previous message.
 
When I run real without changing the namelist I get the same result. The dates in both domains are the same I check that several times.
If I change in namelist.input max_domain=1 it works with 1 domain. The strange thing is that sometimes works and sometimes I get the error.
 
There is absolutely no reason why the wrfinput_d02 file should be created with intitial conditions starting an hour before you are asking for. Has your code been modified in any way? Even if you don't think so, I would suggest trying with a fresh "out-of-the-box" version of WRF - build it in a new directory and try running again to see if you are still getting the same problem.
 
Top