NAME
dds2cmcube - Create Connection Machine cube data
SYNOPSIS
dds2cmcube [help] [in= in_dict] [format= in_fmt] [data=
in_data] [out= out_dict] [out_data= out_data] [hdr=
out_dict] [hdr_data= out_data] [par= par_dict] [dump= {fmt}
{buf n | diff n | diff2 n | name "n1 n2 ..." | usp | segy |
disco}]
DESCRIPTION
Dds2cmcube reads binary data and builds a data cube for the
Connection Machine.
CONTROL
The usage of in, format, data, out, out_data, hdr, hdr_data,
par, and dump is common to most DDS programs. See
dds_user(1) for details.
DEFINITIONS
akjsdlfj
type:cube_slab= {n1 n2 n3 ...}
Field names for header slab.
nproc= n
Number of CM processors.
cm_arch= cm5
CM architecture.
hippi= {yes | no}
Hippi channel transfer.
fms= {yes | no}
Fixed machine size.
data_type= {real | complex}
Cube data type.
round= {yes | no}
Round cube dimension.
prepad= n1 n2 n3
Prepad dimension.
postpad= n1 n2 n3
Postpad dimension.
cm_layout= l1 l2 l3 ...
CM array layout.
tab(|); l lB lB l. layout|description. news|CM key-
word serial|CM keyword send|CM keyword disk|Disk
resident axis.
pad_mode= l1 l2 l3 ...
CM array layout.
EXAMPLES
This copies a data dictionary from foo into bar. The input
binary data is described by the foo dictionary. The data
itself normally resides in another file defined by foo
(data= filename). The bar output dictionary describes out-
put data. The filename for output data is
DATA_PATH/barDATA_SUFFIX.
dds2cmcube in= foo out= bar
Data dictionaries can be piped through the dds2cmcube pro-
gram. The binary data is appended to the parameter diction-
ary and both are sent through the pipes. This works for all
formats (usp, segy, disco, etc.). Command line arguments
are not required for dds2cmcube when in= stdin: and out=
stdout:.
dds_pgm | dds2cmcube | dds_pgm
Bridge will automatically create a dictionary for input
data, if it doesn't already exist. The user must define
format to provide the required hint. The binary data
filename may also be defined, if the default (data= stdin:)
is not appropriate.
dds2cmcube format= usp ... < line3.usp
usp_pgm | dds2cmcube format= usp ...
dds2cmcube data= line3.usp format= usp ...
Bridge always creates an output dictionary that describes
the output binary data. The default name for output data is
dependent upon the dictionary name and media (file, pipe,
tape, etc.). These names may be explicitly defined using
out and out_data.
dds2cmcube out= line3 ...
dds2cmcube out= line3 out_data= stdout: ... | usp_pgm
dds2cmcube out= line3 out_data= /export/xxx.usp ...
The format of output data is the same as the input, unless
explicitly changed. The conversion is controlled by map
definitions. The output trace fields are computed using an
algebraic expression referencing input fields. The user may
override the default map definitions. See dds_map(1).
dds2cmcube format= usp out_format= segy ...
Data can be read from or written to tape. If multiple input
reels are required, labels must be defined for the input
device.
dds2cmcube data= /dev/rst1 ...
dds2cmcube out_data= /dev/rst1 ...
dds2cmcube data= /dev/rst1 /dev/rst1= label "a b c" ...
SEE ALSO
tab(|); lB l. dds(1)|overview dds_user(1)|user guide
dds_map(1)|map expressions dds_names(1)|glossary
dds_format(1)|generic format dds_disco(1)|Disco format
dds_usp(1)|Disco format dds_segy(1)|Disco format
AUTHOR
R. L. Selzler, TRC (May, 1994).
COPYRIGHT
copyright 2001, Amoco Production Company
All Rights Reserved
an affiliate of BP America Inc.
Man(1) output converted with
man2html