Hi, everyone!
I conducted a one-month simulation from 2020052000-2020070100 using WRF-V4.2. The first 10 days were regarded as spin up time. The WPS and real procedure were done before running the WRF.
I set the resart interval of 4 days. The nearest restart time was 2020-06-01_00:00:00.The wrf procedure was running normally without errors and the wrfout and wrfrst files seemed to be normal. Due to the insufficient storage, I deleted all the files of wrfout_d01_2020-05-20_00:00:00 - wrfoutd01_2020-05-30_00:00:00.
But when I checked the rsl.out file, there existed errors and warnings as follows:
Finally I killed the job, and checked the time series of the wrfbdy and wrflowinp. The time coverage was not the same for the wrfbdy and wrflowinp.
I wonder why did the above issues happen and how can I solve it? Did it related to the inconsistent time series of the wrfbdy and wrflowinp?
Attched are the namelist.input, namelist.wps, rsl.out.0000, rsl.out.0001 and rsl.error.0001
Thank you for any generous help!
I conducted a one-month simulation from 2020052000-2020070100 using WRF-V4.2. The first 10 days were regarded as spin up time. The WPS and real procedure were done before running the WRF.
I set the resart interval of 4 days. The nearest restart time was 2020-06-01_00:00:00.The wrf procedure was running normally without errors and the wrfout and wrfrst files seemed to be normal. Due to the insufficient storage, I deleted all the files of wrfout_d01_2020-05-20_00:00:00 - wrfoutd01_2020-05-30_00:00:00.
But when I checked the rsl.out file, there existed errors and warnings as follows:
Finally I killed the job, and checked the time series of the wrfbdy and wrflowinp. The time coverage was not the same for the wrfbdy and wrflowinp.
I wonder why did the above issues happen and how can I solve it? Did it related to the inconsistent time series of the wrfbdy and wrflowinp?
Attched are the namelist.input, namelist.wps, rsl.out.0000, rsl.out.0001 and rsl.error.0001
Thank you for any generous help!
Attachments
Last edited: