Running the pipeline

To run the pipeline, you use the oracdr command. This has a number of qualifiers described fully in SUN/230. There is online help too; enter

 % oracdr -h

for a list of the options.

Unlike using ORAC-DR at UKIRT, you are unlikely to need the looping (-loop option) for offline processing, as all the data exist. Thus the most important qualifiers are -list and -from, which specify the frames to process; and the recipe name.

 % oracdr -from 42

will process frames c20031022_00042 until the end of the night's data (assuming the earlier oracdr_cgs4 command), running the recipes given by each frame's header (RECIPE keyword). More likely is that you provide a list of selected observations. The following example

 % oracdr -list 41:49,51:59 POINT_SOURCE

processes frames from 41 to 49 inclusive and 51 to 59 inclusive, invoking the POINT_SOURCE recipe, and overriding the RECIPE header.

 % oracdr -list 5,6,11,12

would reduce the frame 5, 6, 11 and 12. This is most likely to be applicable to pairs of flats and arcs.

There is a hazard with the -list option. Take care to select a complete set of frames associated with an observation. A common error is to accidentally include an arc frame not part of the group. Check the log on the raw data directory; it has file extension .nightlog. If you do not have a log, it is easy to create one.

 % oracdr -from 1 -nodisplay NIGHT_LOG

This will create a log in $ORAC_DATA_IN for the current UT date. For CGS4, the log will be named <date>.nightlog. For multi-mode instruments such as Michelle, UIST, IRIS2, or ISAAC, there may be two log files created, one called <date>_im.nightlog and another called <date>_sp.nightlog, depending on the observing mode. In general mode-agnostic observations such as array tests are taken under imaging mode and will show up in the _im log, whereas science and calibration observations will show up in the _sp log.