--- MITgcm_contrib/LCML/cpl_aim+ocn/README	2007/10/17 21:46:26	1.1
+++ MITgcm_contrib/LCML/cpl_aim+ocn/README	2007/10/21 18:19:34	1.2
@@ -1,3 +1,15 @@
+*****VERY IMPORTANT*****
+The setbuildenv and setrunenv files need to be in the users' home
+directory. They need to be modified for other compilers/libraries.
+Eventually LEGEND will prepare them as well.
+
+Load up Legend
+
+Go to File->Open, put in 
+/net/lagoon/scratch2/ce107/MITgcm_contrib/LCML/cpl_aim+ocn
+or whereever you have untared/cvs co-ed the root directory
+and choose cpl_aim+ocn.xml
+
 To build the code:
 
 A) Go to the top level menu and 
@@ -8,7 +20,8 @@
 1) set the choices for package, options etc in every case.
 2) save the file in every case
 
-C) Configure the Atmosphere genmake2 menu and run genmake2
+C) Configure the Atmosphere genmake2 menu and run genmake2. This takes
+a while.
 
 D) Go up to the Atmosphere build menu, decide on the variables and 
 run the script
@@ -20,7 +33,7 @@
 F) Configure the Ocean genmake2 menu and run genmake2
 
 G) Go up to the Ocean build menu, decide on the variables and 
-run the script
+run the script. This takes a while.
 
 B) Go deep into the Coupler build menu and 
 1) set the choices for Parameters in every case.
@@ -28,16 +41,46 @@
 
 C) Configure the Coupler genmake2 menu and run genmake2
 
-D) Go up to the Atmosphere Coupler menu, decide on the variables and 
-run the script
+D) Go up to the Coupler build menu, decide on the variables and 
+run the script. This doesn't take too long.
 
 To run the code:
 
-A) Go deep into each menu and edit the data parameter files. Save them.
+A) Go deep into each menu and edit the data and execution parameter
+files. Save them in the respective directories (savedirs) that you
+sent in the top menu. 
+
+*****VERY IMPORTANT*****
+To retrieve values that work for this setup you can either import each
+file's exported values (the names are self explanatory) or import a
+top to bottom export for the runtime called
+exportFromCpl_aim+ocn_runtime.xml
 
-B) To to the top runtime menu, edit the options and run the script.
+B) Go to the runtime menu for each component and run the script to
+prepare the run directories 
+
+C) To to the top runtime menu, edit the options if necessary and run
+the script. 
 
 LEGEND current faux-pass:
-a) Do not forget to remove the default PBS monitor from the options under Tools.
+a) LEGEND is temperamental as of late. It seems to be far less so with
+IBM java than with Sun Java so on batsi.mit.edu for example use module
+add jdk/ibm/1.5.0 
+java -jar Legend.jar
+etc.
+Available modules on batsi are seen as always by 
+module avail
+b) If you do not want to see PBS output that makes no sense do not
+forget to remove the default PBS monitor from the options under
+Tools. On the other hand this way you get a nice popup when an action
+finishes unlike the standard case when you have to look for any
+output.  
+c) You can always edit a script before execution in the window it
+appears in; Sun Java sometimes gets horribly worked up over it and
+LEGEND needs to be killed.  
+d) After an import the visual on the use box for a structure becomes
+unticked even though it is actually true. The file output is correct
+but the table display is misleading.
+