--- mitgcm.org/front_content/using_cvs.xml 2005/09/29 12:17:13 1.9
+++ mitgcm.org/front_content/using_cvs.xml 2009/11/03 23:20:16 1.12
@@ -55,7 +55,7 @@
MITgcm_contrib directory that can be checked out using:
- $ cvs co MITgcm
+ $ cvs co MITgcm_contrib
In general, we do not recommend checking out all of MITgcm_contrib since
@@ -93,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