Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

WRF-CTSM running got stuck at a certain time

Xiao.zh

Xiao Zhang
New Member
Hi all, I met a problem with WRF-CTSM simulation.
I have set a simulation of 112 days. The wrf.exe was running fine until 22:56:06 of the first day. Then there was no more output and the wrf.exe was still running.
I used grep cfl rsl* to check errors and found nothing. I have tried to use small time steps and have got the same condition.
Does anyone have met similar problem or have any ideas on how to fix this?
I attached my namelist.input and files for CTSM.
Thanks for your attention.

Xiao
 

Attachments

  • namelist.input.txt
    3.5 KB · Views: 0
  • lilac_in.txt
    1.7 KB · Views: 0
  • lnd_in.txt
    8.2 KB · Views: 0
  • lnd_modelio.nml.txt
    154 bytes · Views: 0
  • rsl.error.0000.txt
    974.6 KB · Views: 0
  • rsl.out.0000.zip
    289.4 KB · Views: 0

Xiao.zh

Xiao Zhang
New Member
the simulation got stucked again while writing restarting files. There are no more message after this in rsl.out file:
writing restart file ./ctsm_lilac.clm2.r.1998-06-02-00000.nc for model date =
1998-06-02-00000

restFile_open: writing restart dataset ./ctsm_lilac.clm2.r.1998-06-02-00000.nc at nstep = 3200

htape_create : Opening netcdf rhtape ./ctsm_lilac.clm2.rh0.1998-06-02-00000.nc
htape_create : Successfully defined netcdf restart history file 1
htape_create : Opening netcdf rhtape ./ctsm_lilac.clm2.rh1.1998-06-02-00000.nc
htape_create : Successfully defined netcdf restart history file 2
 

slevis

Moderator
Staff member
The fact that the model gets stuck when you increase output frequency and/or when writing restart files suggests that you have an i/o (input/output) problem, and you should probably ask the administrators of the machine that you're running on for help.
 
Top