Arguments:
    The following argument is supported:

    * RECIPE
        By default, ORAC-DR looks in the file header for the name of the
        recipe to be used on the data. If you specify the name of a recipe
        on the command line, it will override the one specified in the
        header. This override recipe is used for all data files regardless
        of header contents or observation mode, so make sure you only only
        apply it to appropriate data frames.

Options:
    All ORAC-DR behaviour is controlled by the option switches. These
    options may be abbreviated to a unique substring. It is via command line
    switches that you (for example) control the range of file numbers to be
    reduced, force the system to use a particular calibration file when
    reducing (e.g. to try a different flat exposure). This list needs to be
    read thoroughly by anyone wanting to use the system.

  General Options:
    -help
        List help text. This prints a summary of this document.

    -version
        Print the version number.

    -verbose
        Print messages from the Starlink engines (rather than just ORAC-DR
        messages).

    -man
        Print the full documentation.

    -debug
        Log debug messages to file "ORACDR.DEBUG" in $ORAC_DATA_OUT.

    -warn
        Turn on perl level warning messages ("perl -w"). This should be used
        for debugging only. If "-verbose" is also true then full perl
        diagnostics are turned on (see diagnostics for more information on
        this perl pragma).

    -beep
        Make as much noise as possible over errors and pipeline exit.
        Default is not to beep.

  Windows and output:
    -nodisplay
        Do not launch the display system. No data will be displayed and GWM,
        GAIA etc. windows will not be launched.

    -showcurrent
        Launch a recipe viewer window along with the log Xwindow

    -log s
        Log to terminal screen (standard out)

    -log f
        Log to a file. The logfile is called ".oracdr_NNNN.log" where NNNN
        is the current process ID. It is written to $ORAC_DATA_OUT and is a
        hidden file.

    -log x
        Log to an Xwindow. Has the advantage that warnings and errors are
        written to different, independently scrollable windows.

    The three log options can be combined. The default is "-log sx"

    To run ORAC-DR using output only within the xterm that you used to
    invoke it in, use "-nodisplay -log s". This is the fastest way to run
    the pipeline if you are not interested in visually inspecting the data
    as it is being reduced.

  Observations:
    -from
        Number of first observation.

    -to Number of last observation.

    -list
        Comma separated list of observation numbers. Colons indicate a
        range. For example, `1,2,4:6,10' means 1,2,4,5,6,10.

    -file
        File name (relative to current directory) of a flat ASCII text file
        containing a list of observation files to be reduced, one file per
        line.

  ut date:
    -ut UT date of observations (defaults to current yyyymmdd). When the
        instrument specific setup scripts are run, oracdr is automatically
        aliased to use the correct "-ut" option. The UT is required for
        UKIRT and JCMT instruments as it forms part of the file naming
        convention for data files.

  Recipe Selection:
    -recsuffix
        Modify the recipe search algorithm such that a recipe variant can be
        selected if available. For example with `"-recsuffix QL"' a recipe
        named MYRECIPE_QL would be picked up in preference to MYRECIPE.

        Multiple suffices can be supplied using a comma separator.

         -recsuffix QL1,QL2

  Calibration options.:
    -calib
        Used to specify calibration overrides. Accepts comma separated
        key=value pairs. (e.g. `"-cal dark=file1"' or `"-cal
        dark=file1,bias=file2"'). The allowed options depends on the
        instrument that is in use.

    See Calibrating for more information on how the pipeline deals with
    calibrations.

  Looping options:
    The "-loop" option specifies the type of data detection loop. Allowed
    values are `list', `inf', `wait', `flag' or 'file'. In almost all cases
    of offline use, `inf' is most appropriate.

    -loop list
        Default when using the "-list" option. The pipeline will stop once
        the observations in the list have been reduced.

    -loop wait
        Waits for data to appear before timing out. Data is reduced and the
        pipeline waits for the next file.

    -loop inf
        Do not wait for data. Simply reduce data starting with observation
        specified by "-from" and continuing until no more files are present.
        Implicitly used when "-from" is specified. This is the fastest way
        of reducing data offline.

    -loop flag
        Waits for completion files to appear (flags) before processing the
        data. Data is reduced and the pipeline waits for more data by
        checking the presence of a flag.

    -loop file
        Works much like "-loop list" except that looping is carried out over
        a list of arbitarly named files input from the "-files" command line
        option.

    -loop task
        Obtain data from a remote (DRAMA) task.

    See DataLoops for more information on looping schemes.

  Group processing options:
    -batch
        Run in batch mode. Precalculate groups before processing data.
        `wait' loop mode should not be used with this option. NOTE only
        SCUBA recipes support this option.

    -skip
        Allow the data detection loop to skip missing observations. Default
        is to stop the loop when an expected file can not be found.

    -resume
        Allow the pipeline to resume midway through the processing of a
        group. (so long as the recipe/instrument supports this behaviour).
        Default is for the group file to be deleted when a new group is
        created. When "-resume" is set, the group file is retained. NOTE
        this option is not currently supported by IRCAM, UFTI and SCUBA
        recipes.

    -grptrans
        Groups are presumed to be transient and no longer needed when a new
        group is created. This is useful when you know that groups can not
        be broken up. Has no effect in batch mode. Memory usage will be
        significantly lower if many hundreds of frames and groups are to be
        processed.

        This option is not the same as setting the ORAC_NOGROUPS environment
        variable. That environment variable disables all group processing
        whereas this command line option ensures that only a single group is
        being processed.

  Engine Options:
    -noeng
        Do not start algorithm engines. NOTE this will cause the vast
        majority of recipes to fail.

    -nomsgtmp
        Do not create an invocation specific temporary directory for the
        messaging systems but use whatever directory is the usual default.
        For ADAM tasks this would mean that ~/adam or $ADAM_USER will be
        used rather than a private ORAC-DR directory. This should only be
        used when it is required for ORAC-DR to talk to tasks that were not
        started by the pipeline and could lead to possible confusion if
        multiple pipelines are running using this flag.

(version 20080213)