--- MITgcm_contrib/osse/README 2004/06/08 19:52:21 1.5 +++ MITgcm_contrib/osse/README 2004/08/22 18:47:41 1.6 @@ -32,22 +32,29 @@ CONTENTS +EnKF: empty + +build: handy place to compile MITgcm + code: modifications to MITgcm to run in cyclindrical coordinates. At the time of this writing, it requires checkpoint48 to compile and run. -input: initialization and input files for MITgcm +codemod: modification to MITgcm to run with checkpoint 54. Not quite +ready for prime time. -filter: source and data files to run the data assimilation and Kalman -filter. +da: location for ensemble members and initialization and input files -utils: assorted Matlab m-files +input: initialization and input files for running MITgcm -EnKF: empty +filter: source and data files to run the data assimilation and Kalman +filter. run: empty +utils: assorted Matlab m-files + -COMPILING AND RUNNING THE MODEL +COMPILING AND TESTING THE MODEL The following series of commands creates the MITgcm executable. @@ -60,13 +67,15 @@ Try a test run, while redirecting the standard output to a file. The input directory contains files that should be present in the working -directory when you run mitgcmuv. It is recommended that you copy the -input contents to a different directory for running -- mitgcmuv does -not change them, but they can be lost in the multitudes of output -files. +directory when you run mitgcmuv. Assuming that you compiled the +MITgcm executable in the build/ directory, you would run +``../build/mitgcmuv >& output.txt'' It is recommended that you copy the +contents of the directory input/ to a different directory for running +-- mitgcmuv does not change them, but they can be lost in the multitudes +of output files. The data assimilation code is made by typing ``make'' in the filter -directory, which creates an executable named osse. +directory, which creates an executable named ``osse''. Before running osse, the initial ensemble needs to be set up by running the mkens script in verification/osse/da. mkens creates the