Checking Your Run

Checking Your Run#

Batch Job Scheduler Monitoring#

Once CESM has been submitted, the status of the run on Derecho can be checked using the qstat command. Qstat accesses the information in the Batch Job Scheduler to see the status of all jobs running on Derecho. The -u option can be specified to simplify the list to jobs for a particular user.

Result of running qstat with an active job running: 

qstat -u $USER

Output: 

                                                            Req'd  Req'd   Elap 
Job ID          Username Queue    Jobname    SessID NDS TSK Memory Time  S Time 
--------------- -------- -------- ---------- ------ --- --- ------ ----- - -----
6606898.desche* katec    cpu      run.my.B1*    --   12 15* 2820gb 12:00 Q   -- 
6606899.desche* katec    cpudev   st_archiv*    --    1   1   10gb 00:20 H   --

Note, there may be a slight delay from submitting CESM until the jobs appear in the queue. Once the jobs have completed they will disappear from the qstat command.

Monitoring Files in the Run and Archive Directories#

As the CESM job runs it will update files in Build / Run Directory. Once the job has completed successfully, the archiver will transfer history files to the Archive Directory. One way to keep track of the progress of the run is to monitor the files in these directories.

  • Check the files in the $RUNDIR as the model is running and once it is finished.

  • Check the files in the $DOUT_S_ROOT after case.st_archive runs.

CaseStatus file#

All activities for the case are recorded in the CaseStatus file in the $CASEROOT directory. By looking through the file, the successful or otherwise outcome of each step of the run can be tracked.

Status of the case recorded in the $CASEROOT CaseStatus file: 

cd /glade/u/home/$USER/cases/CASE
more CaseStatus
Click here for example output 
2026-06-30 21:07:13: case.setup starting 
 ---------------------------------------------------
2026-06-30 21:07:15: case.setup success 
 ---------------------------------------------------
2026-06-30 21:07:15:   local git repository created
 ---------------------------------------------------
2026-06-30 21:11:17: case.build starting 
 ---------------------------------------------------
2026-06-30 21:27:59: case.build success 
 ---------------------------------------------------
2026-06-30 21:33:07: case.submit starting case.run:6606898.desched1, case.st_archive:6606899.desched1
 ---------------------------------------------------
2026-06-30 21:33:08: case.submit success case.run:6606898.desched1, case.st_archive:6606899.desched1
 ---------------------------------------------------
2026-06-30 21:57:19: case.run starting 6606898.desched1
 ---------------------------------------------------
2026-06-30 21:57:28: model execution starting 6606898.desched1
 ---------------------------------------------------
2026-06-30 22:01:21: model execution success 6606898.desched1
 ---------------------------------------------------
2026-06-30 22:01:21: case.run success 6606898.desched1
 ---------------------------------------------------
2026-06-30 22:01:22:   Timing files created for run 6606898.desched1.260630-215719
 ---------------------------------------------------
2026-06-30 22:01:52: st_archive starting 6606899.desched1
 ---------------------------------------------------
2026-06-30 22:02:01: st_archive success 6606899.desched1
 ---------------------------------------------------
Contents