Previous: Setting up and acquiring data
Up: Data acquisition with the CCD
Next: Windowing and binning CCD data
Previous Page: Setting up and acquiring data
Next Page: Windowing and binning CCD data
If you want to take a quick look at data, displaying it on the DMS or SPARCstation, but not collecting header information or copying the data to disk on the system computer, do a glance exposure:
ICL> GLANCE UES 5In this example, a 5-second exposure is made and the data appears in the DMS. The data can then be inspected before proceeding further.
If you decide you want to keep this data on the system computer after all, type
ICL> KEEP UES [TITLE="This command will assign a run number, collect headers and write the data to a disk file in RUN_FILES a for a normal run. Note that if you have changed the instrumental setup between taking the glance exposure and saving it the headers will be incorrect.
To make an observation that you do not intend to retain, but which you want to save to disk on the system computer, use the WINK command.
ICL> WINK UES 1 <observation type> <exposure time> [TITLE="causes the data (image plus headers) to be written to a `scratch file' S1.SDF in the directory SCRATCH_FILES. Scratch files have headers but aren't allocated run numbers; they are temporary files that should not be exported from LPO.
Any number of such scratch files may be created (subject to disk-space constraints) by substituting another file number for the 1 in the command. If you make a scratch exposure into an existing scratch file, the new data over-writes the old.
SCRATCH_FILES is initially the same directory as RUN_FILES but this can be changed by redefining the logical name at job level.
An example definition would be:
$ DEFINE/JOB SCRATCH_FILES <directory path>
If you later find that you want to keep a scratch file, you can convert it to a proper run using the PROMOTE command.
ICL> PROMOTE 1causes scratch file 1 to be allocated a run number and moved to RUN_FILES.