The most noticable difference in the way that PONGO behaves and “normal” IRAF tasks is that it uses its own display and graphic devices. To display on an X device the usual way of referring to a window is by the name xw. This is as used thoughout this document. If you need to change the size of this window then use the command (from the shell after closing the existing window):
You should not change the size of an X window after it is created. The X window is created using the
GWM services which you can read more about in SUN/130 (which, for instance, describes
other command-line options and how to set up your X resources to define the window
size). If you want to plot to a postscript file then there are a range of possible devices, the
most usual of which are pscol_p (colour postscript portrait mode) and epsfcol_p (colour
encapsulated postscript). All the devices available can be viewed using the INQUIRE DEVICES=YES
command.
The way that PONGO behaves when run from CL tends to be slightly different to that indicated in the full routine descriptions. The main changes are that some parameters will not behave as described and there are very few of what are described as “global parameters”. The on-line help available in CL should show what the actual parameters associated with a command are (you can, of course, also view these using the lparam command).
The commands described as “aliases” and “synonyms” previously are actually CL scripts most of
which will work pretty much as described. One problem to beware of is that several such commands
do not have any associated parameters (i.e. ADVANCE, CONNECT, ERASE, RESETPONGO, SHOWPONGO, VSTAND,
WNAD, XLINEAR, XLOGARITHM, YLINEAR and YLOGARITHM) so cannot be setup as part of a mkscript
session.
One unusual characteristic of PONGO commands is that some have what are described as “Write” or
“Unused” parameters. Both these types cannot be set using eparam (or more precisely any values you
assign to these will be ignored). The “Write” parameters will be modified when the command
completes and are a way of getting values back from the command for other uses (the NDATA
parameter of READF is one example, this is set to the actual number of points read from the
file).
If you want to know more about how Starlink packages operate from IRAF/CL then see the document SUN/217.