/[MITgcm]/manual/s_outp_pkgs/text/mnc.tex

Diff of /manual/s_outp_pkgs/text/mnc.tex

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

-revision 1.3 by edhill,
Sat Aug  6 16:28:14 2005 UTC
+revision 1.4 by edhill,
Tue Dec 20 21:25:16 2005 UTC
 Line 147 
 are contained within a Fortran namelist
        write \texttt{autodiff} output w/MNC  \\
        \texttt{mnc\_max\_fsize}  &  R  & 2.1e+09  &
        max allowable file size  \\
+       \texttt{mnc\_filefreq}  &  R  &  -1  &
+       frequency of new file creation (seconds)  \\
        \texttt{readgrid\_mnc}  &  L  &  \texttt{.FALSE.}  &
        read grid quantities using MNC  \\
        \texttt{mnc\_echo\_gvtypes}  &  L  & \texttt{.FALSE.}  &
-Line 202 
 http://nco.sourceforge.net/
+Line 204 
 http://nco.sourceforge.net/
  \end{verbatim}
  \begin{rawhtml} </A> \end{rawhtml}
+ Another way users can force the splitting of MNC files along the time
+ dimension is the \texttt{mnc\_filefreq} option.  With it, files that
+ contain variables with a temporal dimension can be split at regular
+ intervals based solely upon the model time (specified in seconds).
+ For some problems, this can be much more convenient than splitting
+ based upon file size.
  Additional MNC--related parameters may be contained within each
  package.  Please see the individual packages for descriptions of their
  use of MNC.
-Line 215 
 files are either mostly or entirely comp
+Line 224 
 files are either mostly or entirely comp
  convention (v1.0) and any conformance issues will be fixed over time.
  The patterns used for file names are:
  \begin{center}
- \texttt{BASENAME.nIter0.tileNum.seqNum.nc}
+   {\footnotesize
+     \begin{tabular}[htb]{l}
+       \texttt{BASENAME.tileNum.nc}  \\
+       \texttt{BASENAME.nIter.faceNum.nc}  \\
+       \texttt{BASENAME.nIter.tileNum.nc}
+     \end{tabular}
+   }
  \end{center}
- and an example is:
+ and examples are:
  \begin{center}
- \texttt{grid.0000000000.000001.0000.nc}
+   {\footnotesize
+     \begin{tabular}[htb]{l}
+       \texttt{grid.t001.nc}, \texttt{grid.t002.nc}  \\
+       \texttt{state.0000000000.t001.nc},
+       \texttt{surfDiag.0000036000.t001.nc}  \\
+       \texttt{input.0000072000.f001.nc}
+     \end{tabular}
+   }
  \end{center}
  where \texttt{BASENAME} is the name selected to represent a set of
- variables written together, \texttt{nIter0} is the starting iteration
+ variables written together, \texttt{nIter} is the current iteration
  number as specified in the main \texttt{data} namelist input file and
- written in a zero-filled 10-digit format, \texttt{tileNum} is the
+ written in a zero-filled 10-digit format, \texttt{tileNum} is a
- six-digit zero-filled tile number, \texttt{seqnum} is a four-digit
+ three-or-more-digit zero-filled and ``\texttt{t}''--prefixed tile
- zero-filled sequence number used when maximum allowable files sizes
+ number, \texttt{faceNum} is a three-or-more-digit zero-filled and
- are too small to contain all of the output for a particular type
+ ``\texttt{f}''--prefixed face number, and \texttt{.nc} is the file
- within one run (new files are created with sequential numbers as files
- reach the maximum file size limit), and \texttt{.nc} is the file
  suffix specified by the current netCDF ``CF'' conventions.
  Some example \texttt{BASENAME} values are:

 Legend:



Removed from v.1.3
 


changed lines


 
Added in v.1.4
 Legend:



Removed from v.1.3
 


changed lines


 
Added in v.1.4
-Removed from v.1.3
+Added in v.1.4

	ViewVC Help
Powered by ViewVC 1.1.22