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

WRF MP28 + SST/QNA update: “Could not find matching time in input file” with 3 domains (FNL input)

K

KL.ARUN

New member
I am running WRF with mp_physics = 28 using GFS FNL data as meteorological input. The simulation works in 2 domains, but fails when all three domains are active together with SST and QNA updates. It is running fine when either QNA or SST update is off. But when both options are turned on in 3 3-domain simulation, it is giving an error after 6 hours, which is the input interval for the Aux input files. I would appreciate help identifying what is wrong.
  • WRF version: 4.7.1
&time_control
interval_seconds = 21600,
input_from_file = .true., .true., .true.,
history_interval = 360, 180, 60,
frames_per_outfile = 1, 1, 1,
restart = .false.,
io_form_history = 2,
io_form_restart = 2,
io_form_input = 2,
io_form_boundary = 2,
auxinput4_inname = "wrflowinp_d<domain>",
auxinput4_interval = 360, 360, 360,
io_form_auxinput4 = 2,
auxinput17_inname = "wrfqnainp_d<domain>",
auxinput17_interval = 360, 360, 360,
io_form_auxinput17 = 2,
force_use_old_data = .true.,

&domains
p_top_requested = 3000,
num_metgrid_levels = 32,
num_metgrid_soil_levels = 4,
wif_input_opt = 1,
num_wif_levels = 30,
dx = 9000, 3000, 1000,
dy = 9000, 3000, 1000,
grid_id = 1, 2, 3,
parent_id = 1, 1, 2,

&physics
mp_physics = 28, 28, 28,
ra_lw_physics = 4, 4, 4,
ra_sw_physics = 4, 4, 4,
sf_sfclay_physics = 1, 1, 1,
sf_surface_physics = 2, 2, 2,
bl_pbl_physics = 1, 1, 1,
cu_physics = 1, 1, 0,
isfflx = 1,
ifsnow = 1,
icloud = 1,
surface_input_source = 1,
num_soil_layers = 4,
num_land_cat = 20,
qna_update = 1,
sst_update = 1,
tmn_update = 1,
sst_skin = 1,
/

ERROR,,
1765957977836.png

Any suggestions or examples of a working three‑domain MP28 + QNA + SST‑update configuration would be very helpful.

Thank you in advance for your help.
 
can you upload all y our rsl.error and rsl.out files in a zip folder from the WRF/run folder:? That will help diagnose the issue
 
Thank you William for taking you time to see into my problem. I have attached below the zip of .out and .error files as you have asked.
 

Attachments

  • rslFiles.tar.gz
    511.3 KB · Views: 2
@KL.ARUN
Thanks for attaching the rsl files and the namelist. The error message you're getting is:

Code: 
d03 2018-08-13_06:00:00  Error trying to read metadata
d03 2018-08-13_06:00:00  Input data is acceptable to use:
           4  input_wrf: wrf_get_next_time current_date: 2018-08-13_06:00:00 Status =         -102
d03 2018-08-13_06:00:00  ---- ERROR: Could not find matching time in input file

This typically means you're missing some data in one of your input files for WRF. Can you issue the following commands and then attach all the *.txt files created?

Code: 
ncdump -v Times wrfbdy_d01 >& wrfbdy.txt

ncdump -v Times wrflowinp_d03 >& wrflowinpd03.txt

ncdump -v Times wrfqnainp_d03 >& wrfqnainpd03.txt
 
kwerner said:
@KL.ARUN
Thanks for attaching the rsl files and the namelist. The error message you're getting is:

Code: 
d03 2018-08-13_06:00:00  Error trying to read metadata
d03 2018-08-13_06:00:00  Input data is acceptable to use:
           4  input_wrf: wrf_get_next_time current_date: 2018-08-13_06:00:00 Status =         -102
d03 2018-08-13_06:00:00  ---- ERROR: Could not find matching time in input file

This typically means you're missing some data in one of your input files for WRF. Can you issue the following commands and then attach all the *.txt files created?

Code: 
ncdump -v Times wrfbdy_d01 >& wrfbdy.txt

ncdump -v Times wrflowinp_d03 >& wrflowinpd03.txt

ncdump -v Times wrfqnainp_d03 >& wrfqnainpd03.txt
Click to expand...
Thank you for your suggestion. I have already checked this and could not identify any missing time in the input files. Another notable observation is that the error does not occur when either the SST update or the QNA update is disabled; it appears only when both options are enabled simultaneously. The .txt files you mentioned are included as attachments for your reference.
 

Attachments

  • TimesFiles.tar.gz
    18.9 KB · Views: 1
Last edited:
Hi,
I just want to let you know that I've been able to repeat your issue with a basic case I ran, turning on both sst_update and qna_update together, and only when running 3 domains (versus 2). It may take a while to get to the bottom of this, but I'm looking into it. Thank you for your patience while we determine a solution.
 
Hi again, I've found that this issue is resolved when I remove "force_use_old_data = .true." from the namelist prior to running real.exe. I was able to do this because my input data are later than V4 data. Are you having to use older input for you simulation?
 
Hello Kwerner,
Thank you for taking the time to look into my error. I'm using only WRF V4 inputs (no older versions), so I'll rerun the simulation without the force_use_old_data option and update you on the results.
 
Hello again,
After setting force_use_old_data=.f, the error has changed to an input error at the same 6th hour(given below). But I'm only using the same version of WRF.

Timing for Writing wrfout_d03_2024-07-27_06:00:00 for domain 3: 54.10665 elapsed seconds
d03 2024-07-27_06:00:00 Error trying to read metadata
d03 2024-07-27_06:00:00 File name that is causing troubles =
d03 2024-07-27_06:00:00 You can try 1) ensure that the input file was created with WRF v4 pre-processors, or
d03 2024-07-27_06:00:00 2) use force_use_old_data=T in the time_control record of the namelist.input file
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 342
---- ERROR: The input file appears to be from a pre-v4 version of WRF initialization routines
-------------------------------------------
 
You must log in or register to reply here.
Top