|
QuickLook/Postprocessing: 'manual invocation'
Sometimes it is handy/necessary to start up the postprocessing tasks
by hand, such that you can see what messages are output to the
terminal. When using the tasks through UIF control this information
is lost once the popped-up IRAF terminal disappears.
Logon to the postprocess account on florence (make sure to
memorize user/passwd as i'm not writing that down here).
If needed set the DISPLAY variable (using setenv).
Start an xgterm (xgterm -sl 1000 -sb -bg lightblue -name IRAF -geo 120x40 &)
and issue the commands as discussed below in that xgterm.
ALFOSC QuickLook/Postprocessing tasks
cd ~/alfosc
setenv EXECSTATUS ~/alfosc/execstatus
-   ./quickexam.ihs   /data/alfosc/   ol110065   1   dummy   dummy   dummy   dummy   dummy   200.0   1000.0
The first two parameters are normally set by BIAS. The 'dummy' parameters are not used but should be given (and can be anything). The other
parameter values correspond to the ones set on the postprocessing UIF.
-   ./quickspec.ihs   /data/alfosc/   ol110065   0   0   0   0   0   0
The first two parameters are normally set by BIAS. The 6 boolean
parameters correspond to the ones set on the postprocessing UIF.
-   ./quickechelle.ihs   /data/alfosc/   ol110065   0   0   0   0   0   dummy   3
The first two parameters are normally set by BIAS. The 'dummy' parameter is not used but should be
given (and can be anything).The other parameter values correspond to
the ones set on the postprocessing UIF.
NOTCAM QuickLook/Postprocessing tasks
cd ~/notcam
setenv EXECSTATUS ~/notcam/execstatus
-   ./quickexam.ihs   /data/notcam   NCpb120270.fits   1   NCpb120001.fits   1
-   ./focuspyramid.ihs   /data/notcam   NCpb120260.fits   1   NCpb120001.fits   1
-   ./slitoff.ihs   /data/notcam   NCpb120250.fits   123456789   512   512   1   NCpb1200049.fits
The first two parameters are normally set by BIAS. The other parameter values correspond to
the ones set on the postprocessing UIF.
Note that there are subtle syntax differences for the
ALFOSC and NOTCAM tasks. Also note that the exact syntax of the
file-name parameter values will likely change when we move to a data
aquisition system that produces MEF-fed images.
| |