WRF-Chem Restart Error When Starting from 06 UTC and 18 UTC

Naser

Naser

Member
Hello,

I am encountering an issue when restarting a WRF-Chem simulation.

The model runs successfully when started or restarted at 00 UTC and 12 UTC. However, when I attempt to restart from 06 UTC or 18 UTC, the model stops with the following error:


0 input_wrf: wrf_get_next_time current_date: 2024-02-22_06:00:00 Status = -102
d01 2024-02-22_06:00:00 ---- ERROR: Could not find matching time in input file
NOTE: 1 namelist vs input data inconsistencies found.
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 1313
NOTE: Please check and reset these options
-------------------------------------------
Abort(1) on node 0 (rank 0 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0



Therefore, the requested times (06 UTC and 18 UTC) are present within the corresponding emission files.

What is confusing is that the restart works correctly at 00 UTC and 12 UTC but fails at 06 UTC and 18 UTC, even though those times are available in the emission files.

Has anyone experienced a similar issue or identified possible causes for this behavior? Any suggestions would be greatly appreciated.

Best regards,
Naser
 

Attachments

Hi Nasar,
Can you issue the following command and then attach the wrfbdy.txt file? Please also do the same with any other auxinput files that may be used by WRF and name the output from those commands similarly.

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

Then issue:

Code: 
ls -ls wrfrst* >& wrfrst.txt

and attach the wrfrst.txt file, as well.
 
Dear Kwerner,
Hello

Thank you for your reply.

You can find the requested files in the attachment.

Thank you
Naser
 

Attachments

Hi Nasar, Many apologies for the delay. Between support staff travel and our users workshop, we've not had much time to dedicate to forum inquiries.

Per your namelist, you're attempting to restart from 2024-02-22_06; however, the times listed in all of the files you attached do not include that time stamp. For e.g., if you look at the end of the wrfbdy.txt file, you see these dates/times:

Code: 
Times =
  "2024-02-10_00:00:00",
  "2024-02-10_06:00:00",
  "2024-02-10_12:00:00",
  "2024-02-10_18:00:00" ;

To do a restart, the files need to include data for the dates/times of the simulation you're attempting.
 
Dear Kwerner,

I sincerely apologize for my late reply.

Thank you very much for your response.

As you mentioned, the time in my wrfbd file did not match the restart time specified in the namelist. I corrected the wrfbdy time so that it matches the restart time, but I am still encountering the same error.

I would appreciate any further suggestions you may have.

Thank you again for your help.

Best regards,

Naser
 

Attachments

kwerner said:
Hi Nasar, Many apologies for the delay. Between support staff travel and our users workshop, we've not had much time to dedicate to forum inquiries.

Per your namelist, you're attempting to restart from 2024-02-22_06; however, the times listed in all of the files you attached do not include that time stamp. For e.g., if you look at the end of the wrfbdy.txt file, you see these dates/times:

Code: 
Times =
  "2024-02-10_00:00:00",
  "2024-02-10_06:00:00",
  "2024-02-10_12:00:00",
  "2024-02-10_18:00:00" ;

To do a restart, the files need to include data for the dates/times of the simulation you're attempting.
Click to expand...
Dear Kwerner,
Please find all logs in the attached tar file.
Thank you
 

Attachments

Thank you for sending those. The wrfbiochem* files you sent are applicable for 2024-02-10_12:00:00, while the restart begins at 2024-02-10_06:00:00. Do you have wrfbiochem* files valid for the restart time?

If so, and if you just attached the wrong ones, then this could potentially be related to a code issue that was fixed in the latest release. Can you try to run this with wrfv4.8.0 and see if you still get the error?
 
kwerner said:
Thank you for sending those. The wrfbiochem* files you sent are applicable for 2024-02-10_12:00:00, while the restart begins at 2024-02-10_06:00:00. Do you have wrfbiochem* files valid for the restart time?

If so, and if you just attached the wrong ones, then this could potentially be related to a code issue that was fixed in the latest release. Can you try to run this with wrfv4.8.0 and see if you still get the error?
Click to expand...
Dear Kwerner,

Thank you for your reply.

I will follow your suggestion and let you know the result. Before doing so, I would like to clarify my situation and provide some additional background.

My work involves applying data assimilation to WRF-Chem. Therefore, I need to restart the model at 00, 06, 12, and 18 UTC. Previously, I used WRF-Chem version 3.9.1. Since I was quite new to the field at that time, I used executables compiled by my colleagues.

With those executables, I was able to restart the model easily at 06 and 12 UTC, even though the times in my anthropogenic and biogenic emission files did not correspond exactly to the restart times. I did not encounter any errors, so I assumed that this behavior was normal.

Later, after gaining more experience, I compiled WRF-Chem myself. However, I found that I could not restart the model using the newly compiled executables. For some time, I continued using my colleagues’ executables, but unfortunately, they have since left our laboratory. I have not been able to resolve the problem since then.

I thought that upgrading to a newer version of WRF-Chem might solve the issue, but the problem still remains. It occurs only when I use the 12-hour, diurnally varying anthropogenic emission files. When I use serial emission files, I do not encounter this problem.

In both cases—diurnal and serial anthropogenic emissions—I use the same biogenic emission file. Since the biogenic emission file contains only one time record, corresponding to the initial time, I do not think the problem is related to the biogenic emissions.

At this point, I suspect that the problem is related to one of the following:

  1. The diurnally varying anthropogenic emission files; or
  2. The way WRF-Chem was compiled.
I wanted to explain this background so that my problem would be clearer.

Regarding your request, I will try your suggestion and report the results to you.

Thank you again for your help.

Best regards,
Naser
 
You must log in or register to reply here.
Back
Top