setenv <synchfile> <path name> or "NONE" setenv <infile> <path name> setenv <outfile> <path name> setenv GRIDDESC <path name> m3cple <and respond to the prompts>where infile, outfile, and the optional synchfile are the logical names of the input and output files. GRIDDESC is needed only if
M3CPLE
is doing a grid-to-grid
interpolation rather than a copy operation.
M3CPLE
program extracts all
variables for a specified time step sequence
from one I/O API file, infile, optionally interpolates them
to a new grid, and writes them to a different I/O API file,
outfile, under the optional control of a synchfile.
Any combination of physical or virtual files
is supported.
The normal use of M3CPLE
with a synchfile is
to fit into a system of coupled models exchanging data via the I/O API coupling mode, and
extract/interpolate data either from a virtual file to a physical
file, or vice versa. Grid-to-grid interpolation is only available for
files of type GRDDED3; the copy
operation is available for files of type GRDDED3, CUSTOM3, BNDARY3; in any case, all the
variables must be of basic data type
M3REAL. For interpolation to be meaningful, the output
resolution should be finer than the input resolution, else you
should not be using any interpolation, but rather should be using some
sort of aggregation algorithm.
The list of currently supported coordinate system conversions for interpolation is the following:
<input coordinate system type> =
<output coordinate system type>
Before you run the program, you need to assign logical names to the physical file names of both files and to the GRIDDESC file, according to Models-3 conventions, using the operation
"setenv <lname> <pname>"The program will prompt you for the logical names you have chosen for the input files, for the output grid, and for the time step sequence to process. To do a copy operation instead of a grid-to-grid interpolation, respond
SAME
to the
prompt for output grid (the default response). The prompts have
default responses indicated in square brackets [LIKE
THIS]
, which can be accepted by hitting <RETURN>.
The specification of starting date and time, target date and time,
and number of time step records for the run follow Models-3
date and time conventions.
If you want to run this program in batch mode (from a script), the recommended way to develop the script is to run the program once interactively noting the pattern of responses to prompts which generate the particular analysis you want. The pattern of responses then becomes either a command-input file which you may redirect into the program in the script, or may become a "here-document" fed into the execution by the script.
Versions of the program are available for each supported architecture (workstation versions are currently in the directories /env/proj/ppar/(SunOS5f90 | IRIX6n32f90 | IRIX64f90)/bin.
Requires Fortran-90 for compilation. Source code for program
m3cple
is available under the
GNU GPL License, Version 2, and can be downloaded
here (Note: NetScape advised;
there seems to be a bug in Micrrosoft Internet Explorer.).
See Also:
To: Models-3/EDSS I/O API: The Help Pages