Commit fe8c75a8 authored by Uwe Schulzweida's avatar Uwe Schulzweida
Browse files

Docu update

parent a0a710e0
......@@ -131,7 +131,7 @@
\setlength{\unitlength}{1cm}
\begin{picture}(16,0.4)
\linethickness{1.5mm}
\put(0,0.1){\line(1,0){15.85}}
\put(0,0.1){\line(1,0){16.3}}
\end{picture}
\begin{flushright}
......@@ -146,7 +146,7 @@
\begin{picture}(16,1)
\linethickness{1.0mm}
\put(0,0.7){\line(1,0){15.85}}
\put(0,0.7){\line(1,0){16.3}}
\end{picture}
\end{titlepage}
......
......@@ -128,7 +128,7 @@
\setlength{\unitlength}{1cm}
\begin{picture}(16,0.4)
\linethickness{1.5mm}
\put(0,0.1){\line(1,0){15.85}}
\put(0,0.1){\line(1,0){16.3}}
\end{picture}
\begin{flushright}
......@@ -143,7 +143,7 @@
\begin{picture}(16,1)
\linethickness{1.0mm}
\put(0,0.7){\line(1,0){15.85}}
\put(0,0.7){\line(1,0){16.3}}
\end{picture}
\end{titlepage}
......
......@@ -96,15 +96,12 @@ of the {\CDI} library (see \htmlref{Build}{build}).
\section{SERVICE}
SERVICE is the binary exchange format of the atmospheric general
circulation model ECHAM \cite{ECHAM}.
SERVICE is the binary exchange format of the atmospheric general circulation model ECHAM \cite{ECHAM}.
It has a header section with 8 integer values followed by the data section.
The header and the data section have the standard Fortran blocking
for binary data records.
A SERVICE record can have an accuracy of 4 or 8 bytes and
the byteorder can be little or big endian.
The following Fortran code example can be used to read a
SERVICE record with an accuracy of 4 bytes:
The header and the data section have the standard Fortran blocking for binary data records.
A SERVICE record can have an accuracy of 4 or 8 bytes and the byteorder can be little or big endian.
In {\CDI} the accuracy of the header and data section must be the same.
The following Fortran code example can be used to read a SERVICE record with an accuracy of 4 bytes:
\begin{lstlisting}[language=Fortran, backgroundcolor=\color{pyellow}, basicstyle=\small, columns=flexible]
INTEGER*4 icode,ilevel,idate,itime,nlon,nlat,idispo1,idispo2
......@@ -134,13 +131,12 @@ The meaning of the variables are:
\section{EXTRA}
EXTRA is the standard binary output format of the ocean model MPIOM
\cite{MPIOM}. It has a header section with 4 integer values followed by the
data section. The header and the data section have the standard Fortran
blocking for binary data records. An EXTRA record can have an accuracy of 4 or
8 bytes and the byteorder can be little or big endian.
The following Fortran code example can be used to read an
EXTRA record with an accuracy of 4 bytes:
EXTRA is the standard binary output format of the ocean model MPIOM \cite{MPIOM}.
It has a header section with 4 integer values followed by the data section.
The header and the data section have the standard Fortran blocking for binary data records.
An EXTRA record can have an accuracy of 4 or 8 bytes and the byteorder can be little or big endian.
In {\CDI} the accuracy of the header and data section must be the same.
The following Fortran code example can be used to read an EXTRA record with an accuracy of 4 bytes:
\begin{lstlisting}[language=Fortran, backgroundcolor=\color{pyellow}, basicstyle=\small, columns=flexible]
INTEGER*4 idate,icode,ilevel,nsize
......
......@@ -8,14 +8,17 @@ First go to the \href{http://code.zmaw.de/projects/cdi/files}{\tt download} page
({\tt http://code.zmaw.de/projects/cdi/files}) to get the latest distribution,
if you do not already have it.
To take full advantage of {\CDI}'s features the following additional
library should be installed:
To take full advantage of {\CDI}'s features the following additional libraries should be installed:
\begin{itemize}
\item Unidata \href{http://www.unidata.ucar.edu/packages/netcdf/index.html}{netCDF} library
({\tt http://www.unidata.ucar.edu/packages/netcdf/index.html})
version 3 or higher.
This is needed to read/write netCDF files with {\CDI}.
\item ECMWF \href{http://www.ecmwf.int/products/data/software/grib_api.html}{GRIB\_API}
({\tt http://www.ecmwf.int/products/data/software/grib\_api.html})
version 1.9.5 or higher.
This library is needed to encode/decode GRIB2 records with {\CDI}.
\end{itemize}
......@@ -38,10 +41,11 @@ Compilation is now done by performing the following steps:
./configure
\end{verbatim}
Or with netCDF support:
Or optionally with netCDF and GRIB2 support:
\begin{verbatim}
./configure --with-netcdf=<netCDF root directory>
./configure --with-netcdf=<netCDF root directory> \
--with-gribapi=<GRIB_API root directory>
\end{verbatim}
For an overview of other configuration options use
......@@ -58,7 +62,7 @@ For an overview of other configuration options use
\end{enumerate}
The software should compile without problems and the library ({\tt libcdi.a})
The software should compile without problems and the {\CDI} library ({\tt libcdi.a})
should be available in the {\tt src} directory of the distribution.
......
{\CDI} is an Interface to access Climate model Data.
The interface is independent from a specific data format
and has a C and Fortran API.
{\CDI} was developed for a fast and machine independent access
to GRIB and netCDF datasets with the same interface.
The local data formats SERVICE, EXTRA and IEG are also supported.
{\CDI} is an Interface to access Climate and NWP model Data.
The interface is independent from a specific data format and has a C and Fortran API.
{\CDI} was developed for a fast and machine independent access to GRIB
and netCDF datasets with the same interface.
The local MPI-MET data formats SERVICE, EXTRA and IEG are also supported.
% limitations:
%
%
\input{install}
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment