PEAKPICK

Finds one or more peaks in data.

  
  NOTE: This command has deprecated since NeXtMidas 3.3.1. Use PEAKPICK;DSP.

<IN>        - Either type 1000 or type 2000 file.            [REQUIRED]
<OUT_ABS>   - ABSCISSA Locations of maxima.                  [OPTIONAL]
<OUT_VAL>   - Values of maxima.                              [OPTIONAL]
<MAX_PEAKS> - Maximum number of peaks per frame.             [DEF=1]
<PAD>       - Fill value if fewer than max # of peaks found. [DEF=0]

Keyword Only Parameters: 

[CXMODE]       - Complex mode. Can be MAG (default), REAL, IMAG, PHASE, 10LOG,
                 or 20LOG. (Since NeXtMidas 3.3.1)
[PAD_VALUE]    - Same as PAD=. If both are present, PAD_VALUE has precedence.

This primitive will find up to <MAX_PEAKS> peaks per "frame" of data. A "frame"
is either:
  * The whole file (type 1000, using defaults), output is type 1000
  * A standard frame of data (type 2000, using defaults) output is type 2000

If two peaks are separated by a "valley" whose difference from the smaller peak
is less than /HYSTER, ignore the smaller peak.

In the special case where the file is type 1000 and <MAX_PEAKS> equals 1,
results parameters are written rather than files, since there is only one
output value of each type.

Currently, the code reads in one entire "frame" of data at a time. This could
be changed to allow processing large files if necessary.

Complex Data in Input Files:
============================
Since NeXtMidas 3.3.1, PEAKPICK will automatically detect complex data in the
input file and process it accordingly. If the CXMODE= argument is not present, 
the data will be assumed to be MAGnitude.

Examples:

Switches:
  /HYSTER - If set, lump together peaks whose valleys are smaller than this, a
            value of 0.0 disables any hysteresis computations. [DEF=0.0]