The program stopped running.

[Park.pong]

Hi; right now I try to operate WRF. Starting at 00:00 on 2022-12-20, I stayed till 00:60 that same day.
Following that, when I wish to run WRF once more from 2022-12-20 at 00:60 to 2022-12-20 at 00:12. in the namelist.input file. The input upon startup should be .true., , right (image 1)? The issue arises, though, when I set it to true: the program runs at restart….. (did not continue) (image 2), thus I will try running it without spin-up time. The outcome was therefore successful.

How, then, can I find a solution for the issue? Furthermore, I would want to know whether executing the program without spin-up time will cause issues or not.

Pic 1


pic 2


This is link to reach namelist.wps and nameless.input : WRF - Google Drive

#WRF

 

[kwerner]

Hi,
I'd like to apologize for the very long delay in response while we've had to tend to other obligations. Thank you for your patience. Since it's been so long, I first want to ask if you're still experiencing this issue. If so, can you attach the full output file (or if you have multiple .rsl files, package those together in a single .tar file and attach that) for the run where the issue occurs? I'm not quite clear on what happens. Thanks!

 

[Park.pong]

Dear @kwerner,

I still facing with this problem. Now. I started to run from 06-03-2023 to 11-03-2023 and set

restart = .false.,

After that I want to continue from 11-03-2023 to 16-03-2023 and I set
restart = .true.,

The result show the same (facing problem again).

Thus, I attached the request file for you to see what is the issue? please you answer me as fast as possible because I found this issues every when I want to set restart = .true.,

 

[Park.pong]

I face the same problem with this post Can't run WRF from wrfrst files

I do not understand how to solve the problem well.

 

[kwerner]

Hi,
1) When you ran the initial case from March 6 through March 11, was the run successful? Did you see the success message in the end of the rsl files?
2) To prepare to run the restart, did you change anything in the namelist.input file, other than setting restart to "true' and changing the date/time start and end?
3) Can you issue the following command and then attach the wrfbdy.txt file?

ncdump -v Times wrfbdy_d01 >& wrfbdy.txt

 

[Park.pong]

Dear @kwerner,

Thank you for your response. I have addressed your questions as follows:

1. When running WRF, I always monitor the process using tail -f rsl.out.0000. This allows me to verify that the model has successfully completed its execution once the process concludes.
2. I have updated the start and end dates in accordance with the settings specified in namelist.wps.
3. I attempted to run the simulation again for the period from April 1 to April 6, covering five days. Consequently, the dates in wrfbdy.txt have been adjusted accordingly.

I have attached all relevant files that I believe are important for diagnosing the issue. Please let me know if you require any additional information.

 

[kwerner]

Hi,
Many apologies for the delay. My notification email got buried amongst some others. Thank you so much for your patience.

I looked at the times in your wrfbdy_d01 file, and they start from 2023-04-01_00, which is the time your restart initiates. I also notice namelist.wps starts at the same time. However, they should start from the original time (in the initial non-restart simulation). Did you re-run WPS and real.exe between running wrf.exe for the original simulation, and the restart simulation? If so, that is no longer a restart simulation, and is just a basic simulation.

For restarts, the dates/times should look something like this example:
WPS: run from 1 April, 2024, through 30 April, 2024
real: run from 1 April, 2024, through 30 April, 2024
wrf (non-restart): run from 1 April, 2024, through 15 April, 2024
wrf (restart): run from 16 April, 2024, through 30 April, 2024