You probably have forgotten to initialize Surf or Kappa.
Let’s assume that you have followed the manual, and you type
surf to initialize the
Surf software package, but nothing happens. You get a reply saying command not
found, instead of the listing you saw in the manual. In this case you probably lack the
Starlink initialization in your
.login files. Type
and you should be able to initialize Surf and Kappa. The Starlink initialization scripts should be
placed in your
.login files if you intend to use Surf and Kappa regularly:
i.e. in your
.login file put the line:
and in your
.cshrc file put the line:
See, for example, SUN/212  for more information on using and installing Starlink software.
This seems to occasionally happen when we switch between program packages. The cure is to
delete the AGI  resource file, called
computer is the name of your
computer, and the file resides in your home directory. In my case the file is called
This means that your AGI database has become corrupt (e.g. by using control-C to exit early from a task that displays graphics (scuover for example) – this prevents the task from performing normal cleanup duties). This problem can be fixed by issuing the Kappa command gdclear or by removing the AGI database file from your home directory (see earlier fault).
Any color printer will need the color table supplied with the plot. In addition to setting the
device to a color printer (e.g. epsfcol_p), you will also have to specify the color table with the
lut. In the example below we plot the final NGC 7129 image using the bgyrw color
table, which resides in $KAPPA_DIR as bgyrw_lut
This produces a color postscript file gks74.ps.n. A list of valid devices can be obtained with the Kappa command gdnames.
Error messages of this type typically indicate that you are out of disk space – a quite common occurrence for anybody reducing SCUBA maps – or that you do not have write permission in your current directory.