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 f20001108_00042 until the end of the night's data (assuming the earlier oracdr_ufti 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 JITTER_SELF_FLAT

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

 % oracdr -list 5:7,23,33

would reduce the frames 5, 6, 7, 23, and 33. This is most likely to be applicable to a series of dark frames.

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 include accidently a dark frame not part of the group. Check the log in the raw data directory; it has file extension .nightlog. If you do not have a log, it is easy to create one.

 % oracdr -noeng -from 1 -skip -nodisplay NIGHT_LOG

This will create a log called $ORAC_DATA_IN/<date>.nightlog for the current UT date. For multi-mode instruments such as Michelle, UIST, IRIS2, NACO or ISAAC, the log will be called $ORAC_DATA_IN/<date>_im.nightlog.