VERY Preliminary instructions for running CCSM on Ranger

cd $WORK

mkdir ccsmrun

setenv CCSMHOME /work/00964/cbitz/ccsm3_0_1_beta12

cd $CCSMHOME/scripts

./create_newcase -case $WORK/ccsmruns/firstrun -mach ranger -res T42_gx1v3

__

consider editing env_conf to change to branch (though try startup first)

./configure -mach ranger

./firstrun.ranger.build Now wait a 1.25 hr (really). The compiled code and run directory will be in $WORK/ccsmruns/firstruns

Edit env_run and select the run length. If at this time you decide that you wish you had set the RUN_TYPE to a branch, you must edit env_conf, configure, and build again by typing ./configure -cleanall and backing up two steps.

Correct your email address at the beginning of firstrun.ranger.run

qsub firstrun.ranger.run

After initial setup and hand-shaking which can take ~5 min, be sure cam or csim is spewing out its routine stdio to know the model is not stuck. Do this by going to the run directory $WORK/ccsmruns/firstrun and looking at the end atm/atm.log.IDnumber or ice/ice.log.IDnumber. They should be accumulating I/O in bunches.

When your job finishes, the output is moved to a "short-term" archive in $WORK/ccsmruns/archive/firstrun You have something like 4TB of space there. Each year CCSM3 produces about 5GB of data. So we aren't going to bother with long term archiving.

After one successful job run through the queue, edit env_run to change CONTINUE_RUN to true and resubmit.

-- CeciliaBitz - 28 Jul 2009