--- mitgcm.org/front_content/using_cvs.xml 2004/02/16 02:27:33 1.6 +++ mitgcm.org/front_content/using_cvs.xml 2009/11/03 23:20:16 1.12 @@ -39,7 +39,7 @@ $ export CVSROOT=':pserver:cvsanon@mitgcm.org:/u/gcmpack' $ cvs login ( enter the CVS password: "cvsanon" ) - $ cvs co MITgcm MITgcm_contrib + $ cvs co MITgcm

Using a "C", "csh", or "tcsh" shell the commands are:

@@ -48,8 +48,21 @@ $ setenv CVSROOT ':pserver:cvsanon@mitgcm.org:/u/gcmpack' $ cvs login ( enter the CVS password: "cvsanon" ) - $ cvs co MITgcm MITgcm_contrib - + $ cvs co MITgcm + + +

A large amount of additional (optional!) content can be obtained from the + MITgcm_contrib directory that can be checked out using: + +

+  $ cvs co MITgcm_contrib
+
+ + In general, we do not recommend checking out all of MITgcm_contrib since + it takes a long time to download (particularly from remote locations) and + much of it is specific to certain setups (eg. high-res setups, + in-development material that is not yet part of the "main" code, + etc.).

Note that you will only need to perform the "cvs login" once. And for convenience, you may want to add the CVSROOT variable to your shell's @@ -60,9 +73,9 @@

Getting Parts of the Source "Tree"

The above commands demonstrate how to check out all of the MITgcm code - and the "contributed" (that is, unsupported by often useful) information - within the "MITgcm_contrib" directory. In many cases, this is overkill - and can result in long download times. To reduce the volume of + and the "contributed" (that is, unsupported by occasionally useful) + information within the "MITgcm_contrib" directory. In many cases, this is + overkill and can result in long download times. To reduce the volume of information downloaded and thereby speedup the download times, one can select one of the following pre-defined "aliases" that will provide a sub-set of the entire MITgcm source "tree":

@@ -80,9 +93,19 @@ MITgcm_verif_basic Source code plus a small set of the verification examples - ("global_ocean.90x40x15", "aim.5l_cs", "hs94.128x64x5", - "front_relax", and "plume_on_slope"). - + ("aim.5l_cs", "hs94.128x64x5", "ideal_2D_oce", "lab_sea", + "tutorial_baroclinic_gyre", "tutorial_global_oce_latlon" + and "tutorial_plume_on_slope"). + + + MITgcm_tutorials + Source code plus all of the tutorials examples. + + + MITgcm_verif_all + Source code plus all of the verification examples. + + + CVS Code Browser + , the MITgcm code is continuously undergoing updates. At points during the development (typically, after work has been done and the - source code has passed the verification + source code has passed the verification tests), a release or checkpoint "tag" is created. These tags are a convenient mechanism for referring to different times or points within the development. One can check out these versions using the "-r TAG_NAME" CVS