Preliminary instructions for using CAM on Ranger

cd $WORK ($HOME and $WORK should be set automatically for you on Ranger.)

mkdir camruns (if necessary)

mkdir camruns/caseid (fill in caseid with your name of choice)

cd camruns/caseid

cp ~cbitz/camruns/genericcam/{bld,run}-* .

Edit $CASE (make it the same as your caseid!) in the build script and run it. Go to the run directory and edit the namelist as needed.

Back up one directory and edit the run script and make sure the caseid is correct so your run will start in the correct directory. Try out your run by first setting the time limit to 30 min and set nelapse = -31 in the namelist.

Set the time limit roughly (adding a bit to my estimates) according to the number of years you wish to run. Typically shorter times have higher priority in the queue. I think we can run upto 24 hrs at a time.

Please do not use automatic restarts on Ranger with CAM! If you need to continue you run be sure to set nsrest to 1 by hand in the namelist and resubmit your job.

Submit the run with qsub. Delete with qdel and check with qstat (not with the -n flag as on olympus).

If running at resolution other than T42, change the number of cores in the run script
For T31 use: #$ -pe 16way 16
For T42 use: #$ -pe 16way 32
For T85 use: #$ -pe 16way 64

Number of Cores and Timing on Ranger
T42 with 32 cores takes about 1 hr 40 min to run one model year (~15 yrs/day)
T32 with 16 cores takes about 1 hr 40 min to run one model year (~15 yrs/day)
Not sure about T85

At this time there is no way to look at your data on Ranger. I'm working on fixing this, but it may take another week. In the meantime, move your data back to olympus with secure copy (scp).

r4 - 2008-04-16 - 19:03:32 - CeciliaBitz