mbm_makedatalist(1)

NAME
mbm_makedatalist - Macro to generate a datalist of the swath files in a specified directory.

VERSION
Version 5.0

SYNOPSIS
mbm_makedatalist [-Idirectory -Odatalist -H -V]

DESCRIPTION
Mbm_makedatalist is a macro to generate an MB-System datalist file referencing all identifiable swath files in the specified target directory. The output datalist will be placed in the current working directory. The output datalist is named datalist.mb-1 by default, but can be specified with the -O option. If no target directory is specified with the -I option, then the current working directory is used. In order for swath files to be recognized and included in the datalist, they must conform to the MB-System swath file naming convention (see the mbsystem manual page for details).

AUTHORSHIP
David W. Caress (caress@mbari.org)
  Monterey Bay Aquarium Research Institute
Dale N. Chayes (dale@ldeo.columbia.edu)
  Lamont-Doherty Earth Observatory

OPTIONS

-H  This "help" flag cause the program to print out a description of its operation and then exit immediately.

-I  directory
    Sets the path of the target directory.

-O  datalist
    Sets the name of the output datalist file. Default: datalist.mb-1

-V  The -V option causes mbm_makedatalist to print out status messages.

EXAMPLES
Suppose we have a set of swath files in a directory and we want to construct a datalist referring to those files. A simple directory listing shows four files:
     20051019_154030.mb88
     20051019_162540.mb88
     20051019_171756.mb88
     junk.txt
of which three are identifiable as swath files because of the ".mb88" file suffix. Running mbm_makedatalist in this directory with no arguments other than verbosity:
     mbm_makedatalist -V
produces a datalist file named datalist.mb-1. The contents of this file are:
     ./20051019_154030.mb88 88
     ./20051019_162540.mb88 88
     ./20051019_171756.mb88 88
where the file junk.txt has been ignored.

SEE ALSO
mbsystem(l), mbdatalist(l), mbinfo(l)

BUGS
This macro doesn't yet recognize when one swath file derives from another (e.g. line1p.mb57 can be inferred to be a processed version of line1.mb57).