Next: 8.3.5 The individual calendars
Up: 8.3 The calendar package
Previous: 8.3.3 Calendar dates and
Contents
Each routine has as an argument the thread number that it is
belonging to, even if this number is not used in the routine
itself.
In order to include the calendar tool into the MITgcm
setup the MITgcm subroutine "initialise.F" or the routine
"initilise_fixed.F", depending on the MITgcm release, has
to be modified in the following way:
c #ifdef ALLOW_CALENDAR
c C-- Initialise the calendar package.
c #ifdef USE_CAL_NENDITER
c CALL cal_Init(
c I startTime,
c I endTime,
c I deltaTclock,
c I nIter0,
c I nEndIter,
c I nTimeSteps,
c I myThid
c & )
c #else
c CALL cal_Init(
c I startTime,
c I endTime,
c I deltaTclock,
c I nIter0,
c I nTimeSteps,
c I myThid
c & )
c #endif
c _BARRIER
c #endif
It is useful to have the CPP flag ALLOW_CALENDAR in
order to switch from the usual MITgcm setup to the
one that includes the calendar tool. The CPP flag
USE_CAL_NENDITER has been introduced in order to enable
the use of the calendar for MITgcm releases earlier
than checkpoint 25 which do not have the global variable
*nEndIter*.
mitgcm-support@dev.mitgcm.org
Copyright © 2002
Massachusetts Institute of Technology |
|
|