--- MITgcm/doc/README	1998/07/08 15:24:05	1.9
+++ MITgcm/doc/README	1998/10/28 03:23:17	1.14
@@ -1,4 +1,4 @@
-$Header: /home/ubuntu/mnt/e9_copy/MITgcm/doc/README,v 1.9 1998/07/08 15:24:05 cnh Exp $
+$Header: /home/ubuntu/mnt/e9_copy/MITgcm/doc/README,v 1.14 1998/10/28 03:23:17 cnh Exp $
 
 
 MITgcmUV Getting Started
@@ -24,7 +24,7 @@
   the steps below:
 
   1. Extract MITgcmUV from the downloadable archive
-     tar -xvf checkpoint12.tar 
+     tar -xvf cNN.tar 
 
   2. Create platform specific make file
      For example on a Digital UNIX machine the script "genmake.dec" can
@@ -32,7 +32,7 @@
 
      cd bin
      ../tools/genmake 
-     cp Makefile.alpha Makefile
+     cp Makefile.alpha Makefile                  ( On Alpha machine)
 
   3. Now create header file dependency entries
      make depend
@@ -45,16 +45,24 @@
   
   6. Run baseline test case
      setenv PARALLEL 1
-     dmpirun -np 2 ../exe/mitgcmuv
+     dmpirun -np 2 ../exe/mitgcmuv        ( Under Digital UNIX   )
+     mpirun.p4shmem ../exe/mitgcmuv -np 2 ( Under Solaris + mpich)
+                                                      
 
      This runs a 4 degree global ocean climatological simulation.
-     By default this code is set to use two porcessors splitting
+     By default this code is set to use two processors splitting
      the model domain along the equator. Textual output is written
      to files STDOUT.* and STDERR.* with one file for each process.
      Model fileds are written to files suffixed .data and .meta
      These files are written on a per process basis. The .meta
      file indicates the location and shape of the subdomain in
      each .data file.
+    
+     This 4 degree global ocean climatological simulation is the baseline
+     configuration for the MITgcmUV code. The change files that 
+     convert the model to a different configuration in the 
+     verification directory all assume that the model is configured for
+     the baseline case and change the model code accordingly.
 
 o Running
 
@@ -82,6 +90,29 @@
 
   - Parallel execution. Hybrid
 
+o Cutomising the code
+
+  Model structure
+  ===============
+  The "numerical" model is contained within a execution 
+  environment support wrapper. This wrapper is designed 
+  to provide a general framework for grid-point models.
+  MITgcmUV is a specific numerical model that uses the
+  framework.
+   Under this structure the model is split into 
+  execution environment support code and conventional
+  numerical model code. The execution environment
+  support code is held under the "eesupp" directory.
+  The grid point model code is held under the 
+  "model" directory. 
+   Code execution actually starts in the eesupp 
+  routines and not in the model routines. For this
+  reason the top level main.F is in the eesupp/src
+  directory. End-users should not need to worry about
+  this level. The top-level routine for the numerical
+  part of the code is in model/src/the_model_main.F.
+
+
 o References
   Web sites - HP
   for doc     Digital