rpointer.drv does not exist

[rddixon@wisc_edu]

Hello!

I am running CESM1.0 on bluefire and set up a much longer run than I had done previously, however, I forgot to increase the wall clock time so that my job quit prematurely. I thought, "no problem, I'll just resubmit it as a continue run", but for some reason it keeps crashing.

I used:

xmlchange -file env_run.xml -id CONTINUE_RUN -val TRUE
xmlchange -file env_run.xml -id STOP_OPTION -val nmonths
xmlchange -file env_run.xml -id STOP_N -val 7 (to finish the year I started)

and made sure to increase the wall clock time to 6:00, however, it doesn't seem to be able to find my rpointer files. My cpl.log file gets to the line

(seq_infodata_Restart) read rpointer file rpointer.drv

but doesn't continue. Also other log files say something to the effect of file pointer rpointer.drv does not exist.

Is this because they were never written when my job was dropped due to exceeding the wall clock time? Is there anyway I can continue this run? Your help is greatly appreciated!

 

[hannay]

You can only restart this run if the rpointer files has been written:
• rpointer.atm
• rpointer.drv
• rpointer.ice
• rpointer.lnd
• rpointer.ocn.ovf
• rpointer.ocn.restart

By default, the rpointer files are written at the end of the run. So, if you run crashed stopped before completion, it is unlikely that you have the files necessary to restart the run. Except if before starting your run, you had changed the frequency of the restart files (by editing the variables: REST_OPTION and REST_N in env_run.xml)

 

[rddixon@wisc_edu]

I thought it might be something like this. Good to know about REST_OPTION and REST_N. Thanks!