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
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