/[MITgcm]/MITgcm_contrib/osse/README
ViewVC logotype

Diff of /MITgcm_contrib/osse/README

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph | View Patch Patch

revision 1.3 by afe, Tue Jun 8 14:13:39 2004 UTC revision 1.6 by afe, Sun Aug 22 18:47:41 2004 UTC
# Line 32  where examples and test examples of MITg Line 32  where examples and test examples of MITg
32    
33  CONTENTS  CONTENTS
34    
35    EnKF: empty
36    
37    build: handy place to compile MITgcm
38    
39  code: modifications to MITgcm to run in cyclindrical coordinates.  At  code: modifications to MITgcm to run in cyclindrical coordinates.  At
40  the time of this writing, it requires checkpoint48 to compile and run.  the time of this writing, it requires checkpoint48 to compile and run.
41    
42    codemod: modification to MITgcm to run with checkpoint 54.  Not quite
43    ready for prime time.
44    
45    da: location for ensemble members and initialization and input files
46    
47    input: initialization and input files for running MITgcm
48    
49  filter: source and data files to run the data assimilation and Kalman  filter: source and data files to run the data assimilation and Kalman
50  filter.  filter.
51    
52    run: empty
53    
54    utils: assorted Matlab m-files
55    
56    
57    COMPILING AND TESTING THE MODEL
58    
59    The following series of commands creates the MITgcm executable.  
60    
61    From the MITgcm root:
62    
63    cd verification/osse/build  
64    ../../../tools/genmake -mods=../code  # creates makefile
65    make depend       # contructs Fortran code from model codebase
66    make              # makes executable mitgcmuv
67    
68    Try a test run, while redirecting the standard output to a file.  The
69    input directory contains files that should be present in the working
70    directory when you run mitgcmuv.  Assuming that you compiled the
71    MITgcm executable in the build/ directory, you would run
72    ``../build/mitgcmuv >& output.txt''  It is recommended that you copy the
73    contents of the directory input/ to a different directory for running
74    -- mitgcmuv does not change them, but they can be lost in the multitudes
75    of output files.
76    
77    The data assimilation code is made by typing ``make'' in the filter
78    directory, which creates an executable named ``osse''.  
79    
80    Before running osse, the initial ensemble needs to be set up by
81    running the mkens script in verification/osse/da.  mkens creates the
82    directories, symbolically links files necessary to run the model, and
83    copies in the initial ensemble files.  osse should be run from the
84    directory verification/osse/da/inits since it expects the ensemble
85    members to be one directory above.  It also expects to have in its
86    working directory the file iobsloc-003.txt, which contains the
87    locations of the observations.  This file is located in
88    verification/osse/da/inits.
89    
90    
91    
92    
93    
94    

Legend:
Removed from v.1.3  
changed lines
  Added in v.1.6

  ViewVC Help
Powered by ViewVC 1.1.22