165 |
multiple threads or MPI processes simultaneously writing to the same |
multiple threads or MPI processes simultaneously writing to the same |
166 |
file. |
file. |
167 |
|
|
168 |
\item[Meta-data] is written on a per-file basis using a second file |
\item[Meta-data] is written by MITgcm on a per-file basis using a |
169 |
with a \texttt{.meta} extension as described above. One should be |
second file with a \texttt{.meta} extension as described above. |
170 |
careful not to delete the metadata files when using convenient |
MITgcm itself does not read the \texttt{*.meta} files, they are |
171 |
MatLAB post-processing scripts such as \texttt{rdmds()}. |
there primarly for convenience during post-processing. One should |
172 |
|
be careful not to delete the meta-data files when using MatLAB |
173 |
|
post-processing scripts such as \texttt{rdmds()} since it relies |
174 |
|
upon them. |
175 |
|
|
176 |
\item[Numerous files] can be written by \texttt{mdsio} due to its |
\item[Numerous files] can be written by \texttt{mdsio} due to its |
177 |
typically per-time-step and per-variable orientation. The creation of |
typically per-time-step and per-variable orientation. The creation of |
178 |
both a binary (\texttt{*.data}) and ASCII text meta--data |
both a binary (\texttt{*.data}) and ASCII text meta-data |
179 |
(\texttt{*.meta}) file for each output type step tends to exacerbate |
(\texttt{*.meta}) file for each output type step tends to exacerbate |
180 |
the problem. Some (mostly, older) operating systems do not |
the problem. Some (mostly, older) operating systems do not |
181 |
gracefully handle large numbers (\textit{eg.} many thousands) of |
gracefully handle large numbers (\textit{eg.} many thousands) of |