 
  
  
  
  
To run the model, go to the workspace directory work.  This
directory contains copies of scripts used to execute the model,
as well run parameter files used as input to the model.  These run
parameter files include:
mrestart execution shell script variable is
		set to ``1''.
            See the discussion of variable mrestart on
            page  for information on
            an important caveat to this file.
 for information on
            an important caveat to this file.
    mrestart on
            page  for information on
            an important caveat to this file.
 for information on
            an important caveat to this file.
    src.
		See Section 1.4.1 for more information
		on this file.  See Chapter 3 for a
		discussion of the physics behind the variables in
		this file.
scripts, while
``working'' copies are located in work.  These scripts include:
test.sh to
confirm that the model will compile and run correctly on your
machine.  Next, run the model a year or so with climatological
SST to create a qtcm.restart initial conditions file that will
serve to shorten the spin-up time of the model.  The 
Firsttime.sh script is set-up to do this.  Finally,
conduct an actual model run by executing qtcm_realtime.sh
or qtcm_seasonal.sh, as appropriate.
The model execution scripts govern the execution of the model by
first defining the major user-controlled
parameters under the script comment title ``Generate the user
control parameters   '' These parameters are then input as a
FORTRAN namelist so any parameter undefined in the script will
take-on the default value given in the subroutine
 '' These parameters are then input as a
FORTRAN namelist so any parameter undefined in the script will
take-on the default value given in the subroutine DriveInit
in driver.f.  Finally, the script compiles
and links the version of the code found
in sub-directory src using the file ``makefile'' in src
(see Section 1.4.3
for more information about the makefiles included
with this QTCM1 package),
moves the resulting executable from src to
work, and executes the program in work.
As it runs, the program writes out diagnostic messages (such as
the number of simulation days completed) to the screen and to a file
in directory work called log.
Below is an explanation of the user-controlled variables in the
execution scripts.  Default values for these user-controlled variables
are defined in the subroutine DriverInit in driver.f.:
landon=1 (the default)
		means land is interactive.
            Other values of landon mean the
		land is treated like ocean with a fake SST provided
            from the SST files.  Since an interactive land has more freedom,
            it's more prone to be unstable in the spin-up process, and it
		has spin-up time longer than the atmosphere by several months.
            Our recommendation is to run the model with land ``off'' for
		the first time (Firsttime.sh is set with such a setting).
	    However, QTCM1 seems to have little of this problem.
    solartop evolves.
               Variable is an alphanumeric string.  There 
               are three mode options:
        perpetual:  Perpetual SST from a
				given month is used (but 
				watch out for summer continents that
				may be too warm if the land is ``on'').
				Month used is specified in month0.seasonal:     Climatological monthly SST;
				solartop seasonal.real_time:   Real time interannual SST;
				solartop seasonal.
        year0 includes the 
                        millennium and century).  For perpetual and
				seasonal cases, year0 can be any value
				between 1001 and 9998.  However, note that
				year0 should be chosen such that during the
				entire length of the model run, the model
				year never exceeds 9998.  Type INTEGER.
				Note: 1 year   360 days in QTCM1.
  360 days in QTCM1.
    lastday.  Type INTEGER.
    noout days;
			useful for spin-up.  Type INTEGER.
    ntout days.  See
			Section 1.4.2 for more details.
			Minimum value is 1.  Type INTEGER.
    ntouti
			days.  See Section 1.4.2 for more
			details.  Minimum value is 1.  Type INTEGER.
    mrestart=1 (the default), model
			uses file qtcm.restart as 
                  initial condition (it is recommended to always use this 
                  option, except for the first time when you need to generate
                  your own qtcm.restart file, together with the land off).
                  Otherwise, the model will start from an initially
			unbalanced state; the spin-up time for the atmosphere is
			several days, and several months for land.  Type INTEGER.
NB: Currently, restart using qtcm.restart is not ``perfect.'' This is because in the standard version, qtcm.restart.out does not save diagnosis of physics variables that are based on previous timesteps of those prognostic variables that are saved in qtcm.restart.out.
 8.
 8.
 .  
		Default value is 5.  Type INTEGER.
 .  
		Default value is 5.  Type INTEGER.
test.sh):
&driverdata title='QTCM test run' !title bnddir='$QTCMROOT/bnddata' !bnd. data other than SST SSTdir='$QTCMROOT/bnddata/SST_Reynolds_oi' !where SST files are outdir='$QTCMROOT/proc' !where output go landon=0 !=0: land is like ocean with faked SST SSTmode='seasonal' !decide what kind of SST to use year0 = 1001 !starting year; must be between 1001 and 9998 month0 = 1 !starting month; 1 to 12 day0 = 1 !1 t0 30; each month has fixed length of 30 days lastday = 60 !model runs from day 1 to lastday (1yr=360day) interval = 1 !ocean-atmo. coupling interval; integer days noout=0 !no output for the first noout days ntout=30 !output mean every ntout days ntouti=30 !output instantaneous value every ntouti days mrestart=0 !=1: restart using qtcm.restart dt=1200. !atmospheric model time step, real seconds &end
This sample defines a run using monthly climatological SST as forcing, beginning on January 1, and ending 60 days later at the end of February (ostensibly February ``30''). Land acts like an ocean with interpolated SST, the atmosphere-ocean coupling interval is one day, each atmospheric time step is 20 minutes, no ``spin-up'' file is used for initial conditions, and both mean and instantaneous output is written every 30 days (i.e. one month).
 
  
  
 