PIPELINE INFRASTRUCTURE

DO : automatic environment

* Random collected files (Several fits files will be sent to do via pilDeliFrame; The testfiles are badpixel files from Europeantest stored in fors_badpixel.tar; ...)

* Commandline options and environments setting (wrong parameters, DFS_ROOT points to unexistent directory; invalid env DFS_DO_RAW; ...)

* SUSI rules (tool FitsFactory is used to generate susi2-fits files for each classification rule)

* EMMI rules

* SOFI rules (tool FitsFactory is used to generate sofi-fits files for each classification rule)

*ISAAC rules (interface DO <--> keyword INSTRUME; tool FitsFactory is used to generate a set of 4 fors-fits files for each classification rule of raw-data; Checking testdata for img_jitter_jitter rule; ...)

* FORS rules (interface DO <--> keyword INSTRUME; tool FitsFactory is used to generate a set of 4 fors-fits files for each classification rule of raw-data; ...)

* Classification rules using FORS data (raw file arrived before DO is started, no rule for single frame, 1^st / last frame missing, ...)

* UVES ( interface DO <--> keyword INSTRUME; ...)

* Error Handling (interface DO <--> path length of data fits file;

* Miscellaneous (Starting DO twice ; order of file processing;

RBS

Syntax of interface files

(*.rb, *.rri, *.rrd, *.prg)"

Environment setting

RB related commands

RBS control commands

DRS (Midas) commands

Command file

Testing scripts

FORS specific tests

ISAAC specific tests

Error Handling

Stress Test

FORS2 specific tests

UVES specific tests

Miscellaneous