Setting up ORAC-DR

Before you can run the pipeline you have to tell ORAC-DR for which instrument you wish to reduce data, the observation date, and the directory containing the raw data, and wher you want the processed data to be written. There are two options.

• The first needs your data to conform to the directory-naming convention of the instrument at UKIRT. This will be the case if you simply unpack the archive written by the uktape utility. In this case enter

        % setenv ORAC_DATA_ROOT <root_data_directory>
        % oracdr_<instrument> <date>
  

  where $<$root_data_directory$>$ is the directory in which you unpacked the data from the tape, $<$instrument$>$ is either ufti or ircam, and $<$date$>$ is the UT date in the format YYYYMMDD. Note that each % represents the UNIX shell's prompt, which you do not type. The commands must be entered in the above order.

  For example, the standard location for raw UFTI data is raw/ufti/YYYYMMDD/, and reduced/ufti/YYYYMMDD/ for the corresponding reduced data. So if your data are stored in /home/users/abc/data/UKIRT/raw/ufti/20001108/ you should enter the following.

        % setenv ORAC_DATA_ROOT  /home/users/abc/data/UKIRT/
        % oracdr_ufti 20001108
  

  to enable the pipeline for UFTI data taken on 2000 November 8.

  Data taken from the AAT is handled differently, as there is no unified directory structure for both raw and reduced data directories. For IRIS2, INGRID, ISAAC, NACO, NIRI, or Classic Cam data the best option is specifying where the raw and reduced data directories are, as shown below. Those with ISAAC and NACO data should see ISAAC and NACO preliminary conversion for a necessary preliminary naming conversion step for each instrument. Classic Cam users need to read Classic Cam preliminary conversion concerning renaming raw data files for the respective instruments.

• The second option is where your raw and reduced data are to be in arbitrary directories. Type the following

        % oracdr_<instrument> <date>
        % setenv ORAC_DATA_IN <raw_data_directory>
        % setenv ORAC_DATA_OUT <reduced_data_directory>
  

  The directories can either be given as full paths, or as relative paths to the current working directory. Here is an example for IRCAM data using full paths.

        % oracdr_ircam 19990328
        % setenv ORAC_DATA_IN /export/data/mjc/asteroid/night1
        % setenv ORAC_DATA_OUT /home/scratch/mjc/reduced
  

In the first case $ORAC_DATA_IN and $ORAC_DATA_OUT are still defined, but in terms of the root directory. For instance, re-using the earlier example with UFTI for UT date 2000 November 8, $ORAC_DATA_IN points to $ORAC_DATA_ROOT/raw/ufti/20001108/.

ORAC-DR operates in $ORAC_DATA_OUT, irrespective of what your current directory is when you invoke it. Your current directory remains unchanged.

It is highly recommended to work in directories on discs local to the computer running the pipeline. Processing over NFS-served drives can many times slower and degrades the performance seen by other users. Running ORAC-DR on a Linux computer over NFS-served drives can also lead to erroneous results, crashing of the pipeline, or computer lockups.