d02 2025-04-11_12:00:00 backfrom med_sidata_input

[2412545269]

Hello everyone, I am currently running the WRF model for the period from April 10, 2025 to April 14, 2025, using two nested domains. The ./real.exe step was completed successfully, and I obtained the following input files:wrfbdy_d01、wrfinput_d01、wrfinput_d02。
d02 2025-04-11_12:00:00 DEBUG wrf_timetoa(): returning with str = [2025-04-11_12:00:00]
d02 2025-04-11_12:00:00 DEBUG wrf_timetoa(): returning with str = [2025-04-10_12:00:00]
d02 2025-04-11_12:00:00 DEBUG wrf_timetoa(): returning with str = [2025-04-14_12:00:00]
d02 2025-04-11_12:00:00 DEBUG wrf_timeinttoa(): returning with str = [0000000001_000:000:000]
DEBUG med_sidata_input: clock after current_date set, clock start time = 2025-04-10_12:00:00
DEBUG med_sidata_input: clock after current_date set, clock current time = 2025-04-11_12:00:00
DEBUG med_sidata_input: clock after current_date set, clock stop time = 2025-04-14_12:00:00
DEBUG med_sidata_input: clock after current_date set, clock time step = 0000000001_000:000:000
d02 2025-04-11_12:00:00 backfrom med_sidata_input
d01 2025-04-14_12:00:00 real_em: SUCCESS COMPLETE REAL_EM INIT
I found that only d01 ran successfully, while d02 failed. How should we handle this situation?
I have attached my namelist.input and rsl.error.* files for reference.
Could you help me determine the cause of the nested domain problem?
Thank you for your support.
Best regards, 2412545269

 

[kwerner]

In the above message, that message does not mean that d02 failed. The very last time step was for d01, and then the "SUCCESS" message printed. This means real.exe was successful. If it's wrf.exe that is failing, please send the rsl file(s) for wrf.exe, instead of real.exe.

Before running wrf.exe, set debug_level back to 0. That variable is rarely useful and ends up just adding a bunch of junk to the rsl* files, making them very large and difficult to read.