|
|||
| Joint Astronomy Centre |
|
|
|
| Show document only |
IntroductionThe summit data reduction uses the orac-dr pipeline, calling the Starlink algorithm set. The pipeline is invoked by first setting up environment variables:oracdr_uist
and then running the actual pipeline: oracdr
-loop flag
(for WFCAM there are four pipelines, and you should see the specific instructions on the runup page). Note that oracdr_<instrument> needs to be entered only once - it does nothing but set up the environment. As a corollary, it can be entered at any time in an xterm to find out what data directories are being used. ArgumentsORAC-DR takes only one command-line argument - the data reduction recipe to be applied. If you give no arguments, the pipeline will get the recipe specification from the FITS headers (and this is the normal mode of operation). If a recipe name (e.g. QUICK_LOOK) is given on the command line, then all frames processed by the pipeline will be processed using that recipe, whether or not it makes sense.OptionsAll ORAC-DR behaviour is controlled by the option switches. 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). there is a long list of options which can be listed by typingoracdr
-h
Here we list only the most common ones. Windows and logging control-nodisplayDo not launch the display system. No data will be displayed and GWM, GAIA etc. windows will not be launched. -log s Log to terminal screen (standard out) -log f Log to a file. The logfile is called ".oracdr_NNNN.log" where NNNNis 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-fromNumber 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. Calibration options-calibUsed 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. Looping optionsThe "-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 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. This is how the normal summit pipeline should be run. If you wish to start a pipeline from a given point and carry on as new data arrive, then use something like this: oracdr -from 750 -loop flag Examples
|
