|
|
|
|
Next: 3.3 Model and directory
Up: 3.2 Obtaining the code
Previous: 3.2.1 Method 1 -
Contents
Subsections
3.2.2 Method 2 - Tar file download
If you do not have CVS on your system, you can download the model as a
tar file from the web site at:
http://mitgcm.org/download/
The tar file still contains CVS information which we urge you not to
delete; even if you do not use CVS yourself the information can help
us if you should need to send us your copy of the code. If a recent
tar file does not exist, then please contact the developers through
the
mitgcm-support@dev.mitgcm.org
MITgcm-support@mitgcm.org
mailing list.
If you already have an earlier version of the code you can ``upgrade''
your copy instead of downloading the entire repository again. First,
``cd'' (change directory) to the top of your working copy:
% cd MITgcm
and then issue the cvs update command such as:
% cvs -q update -r checkpoint52i_post -d -P
This will update the ``tag'' to ``checkpoint52i_post'', add any new
directories (-d) and remove any empty directories (-P). The -q option
means be quiet which will reduce the number of messages you'll see in
the terminal. If you have modified the code prior to upgrading, CVS
will try to merge your changes with the upgrades. If there is a
conflict between your modifications and the upgrade, it will report
that file with a ``C'' in front, e.g.:
C model/src/ini_parms.F
If the list of conflicts scrolled off the screen, you can re-issue the
cvs update command and it will report the conflicts. Conflicts are
indicated in the code by the delimites `` '', ``======='' and
`` ''. For example,
<<<<<<< ini_parms.F
& bottomDragLinear,myOwnBottomDragCoefficient,
=======
& bottomDragLinear,bottomDragQuadratic,
>>>>>>> 1.18
means that you added ``myOwnBottomDragCoefficient'' to a namelist at
the same time and place that we added ``bottomDragQuadratic''. You
need to resolve this conflict and in this case the line should be
changed to:
& bottomDragLinear,bottomDragQuadratic,myOwnBottomDragCoefficient,
and the lines with the delimiters ( ,======, ) be deleted.
Unless you are making modifications which exactly parallel
developments we make, these types of conflicts should be rare.
We don't make a ``release'' for every little patch and bug fix in
order to keep the frequency of upgrades to a minimum. However, if you
have run into a problem for which ``we have already fixed in the
latest code'' and we haven't made a ``tag'' or ``release'' since that
patch then you'll need to get the latest code:
% cvs -q update -A -d -P
Unlike, the ``check-out'' and ``update'' procedures above, there is no
``tag'' or release name. The -A tells CVS to upgrade to the
very latest version. As a rule, we don't recommend this since you
might upgrade while we are in the processes of checking in the code so
that you may only have part of a patch. Using this method of updating
also means we can't tell what version of the code you are working
with. So please be sure you understand what you're doing.
Next: 3.3 Model and directory
Up: 3.2 Obtaining the code
Previous: 3.2.1 Method 1 -
Contents
mitgcm-support@dev.mitgcm.org
| Copyright © 2002
Massachusetts Institute of Technology |
 |
|
