iraf.net

Hi Paul LeVan. Your mail message arrived within 5 minutes of your sending
it! I've answered your questions below, and have repeated your original
message so others can follow our conversation. Please feel free to ask lots
of questions - we're glad to have you as an active IRAF site. Suzanne Jacoby
sjacoby@noao.arizona.edu
5356::sjacoby or draco::sjacoby
602-325-9364
------------------------------------------------------------------------------- > Hello Suzanne,
> Thanks so much for all your help as we were finally able to use our
> LN03 laser as the IRAF stdplot. Also, the Graphon 240 is fine as the
> stdgraph terminal. I am very much pleased by the IRAF and realize that
> I've seen only the basics!
> Now, several observations that I hope will be useful to you as
> difficulties encountered by this IRAF user:
>
> I) Images package -
> 1) Using imdel with wildcard filenames, I sometimes see
> WARNING: CANNOT ACCESS IMAGE *.PIX after which the
> *.imh and *.pix files are deleted, or
> WARNING: CONNOT OPEN IMAGE *.PIX, after which the
> files are not deleted. I am guessing that you have the image headers (*.imh) and pixel files (*.pix)
in the same directory. There is nothing wrong with this setup, but when you
use a wildcard, the header and pixel files are matched as two separate files
unless you specify the .imh extension (*.imh). The warning messages you
see result from the program trying to access a pixel file as an image header.
These are only warning messages, however, and the desired deletion should take
place. >
> 2) I cannot find imstack, and consequently do not know
> how to increase the dimensionality of images.Imstack is in the proto package, which is under noao. You can get this
information from the 'help' command. When you type 'help imstack', the
package path 'noao.proto' is printed at the top of the help page. Be aware
that a large number of image operations can be performed using the 'imcopy'
task and image section notation... see the manual page for imcopy. >
> II) In cl -
> 1) show term CR gives vt100, but
> show terminal CR gives vt640 ?By default, there is no CL environment variable named 'term'. I think you
may have defined this variable inadvertantly by abbreviating the word
'terminal' on a previous set command. So, you have two different CL environment
variables: 'term' and 'terminal'. It is the value of 'terminal' that is used
when retrieving information from the termcap file; the 'term' variable has no
built in meaning to the CL and does no harm. >
> 2) set CR gives the user environment listing, but
> with discrepant repeated values -
> e.g., stdgraph=4014 at top of list, but
> stdgraph=vt640 at bottom.
> also, printer=vvprint at top, but
> printer=imagen at bottom.
>
> Those at the top are preferred and are those shown with
> the SHOW command.The discrepant values reported by 'set' show that the value of an environment
variable has been set more than once. You can use 'reset' instead of 'set'
to avoid this duplication. You can also show only the present values of
variables with 'show'. For clarification of set, reset and show, read the
manual page on set ('help set'). >
> Once again, thanks to all at NOAO for a wonderful IRAF!
>
> Paul LeVan
>------