iraf.net

Hello Dario Trevese, > thank you for your e-mail of feb-9. I included the 'reset' and 'task'
> instructions in the login.cl file and I was able to run
> the display program. However the program gave a system error:
> mismatch in shearable image name.
> I have not found Robert Thompson yet . I could perhaps send you all
> the Thompson's files (135 blocks) , but you don't have the SIGMA
> ARGS . Can you suggest me something ?
> We will ask for the IRAF version 2.8 , but I don't think that the
> above problem is related to the IRAF version.VMS/IRAF does make use of a shared library which is certainly different
in V2.5 and V2.8 and which is installed in VMS as part of the IRAF
installation procedure. I don't know how the executable in Thompson's code
was linked, whether or not it links with the shared library. If it
does, that is the problem which will be resolved when you upgrade to
V2.8. In the meantime, you might try relinking without the shared
library. This is done by adding the flag "-z" to the linker command.
(Make a backup copy of the current executable before proceeding.)
I can't tell you exactly what command to use since I don't really know
how this package is structured. But, go to the package root and type
'mkpkg update -n". This is a no-op pass of the mkpkg procedure;
commands will be printed but not executed. (You can read through
the mkpkg file and read the on-line help for mkpkg.) Assuming no errors
are reported, reenter the command this time adding the -z linker flag:
cl> mkpkg update LFLAGS="-z"Try running the new executable. If this doesn't work, you'll have
to contact Thompson to get correct instructions for relinking without
the shared library or wait for V2.8 to arrive.Suzanne

Dear Jeannette,
Thank you very much for your prompt delivery of my Sun/IRAF software
and documentation. My Sparcstation arrived a week ago last Friday and I
am happy to say I am up and running with SunOS and IRAF. Even as a
novice UNIX user, your installation instructions for IRAF were excellent
and I had no problems. I do have a few questions about configuration.1. I wish to have the pixel directory in a subdirectory below the
current subdirectory I am in. This maintains the file and directory
structure I prefer to use for my data reduction and analysis. How do I
change mkiraf so that it creates the pixel directory with name say
"images" in the subdirectory I currently am in?2. I have arranged the various windows and their sizes on the screen the
way I want them. I then use "save page layout" to save the settings
back to my .sunview file. However, the next time I come into sunview
and IRAF the windows and their sizes are still the old defaults. Do you
know what the problem might be?3. Does the dataio command t2d read tape FITS images to disk in the same
format that would be produced if I wrote an IRAF disk image file to a FITS
disk file?4. Would it be possible to receive copies of the following documents? "IIDS/IRS Data Reductions on IRAF with ONEDSPEC Package"
"Reduction of Longslit Spectroscopic Data Using IRAF"
"Reduction of Echelle/CCD Data Using IRAF" I need the first two more than the last one at the moment.Thanks again, Mark

Dear Jeannette,
Thank you very much for your prompt delivery of my Sun/IRAF software
and documentation. My Sparcstation arrived a week ago last Friday and I
am happy to say I am up and running with SunOS and IRAF. Even as a
novice UNIX user, your installation instructions for IRAF were excellent
and I had no problems. I do have a few questions about configuration.1. I wish to have the pixel directory in a subdirectory below the
current subdirectory I am in. This maintains the file and directory
structure I prefer to use for my data reduction and analysis. How do I
change mkiraf so that it creates the pixel directory with name say
"images" in the subdirectory I currently am in?2. I have arranged the various windows and their sizes on the screen the
way I want them. I then use "save page layout" to save the settings
back to my .sunview file. However, the next time I come into sunview
and IRAF the windows and their sizes are still the old defaults. Do you
know what the problem might be?3. Does the dataio command t2d read tape FITS images to disk in the same
format that would be produced if I wrote an IRAF disk image file to a FITS
disk file?4. Would it be possible to receive copies of the following documents? "IIDS/IRS Data Reductions on IRAF with ONEDSPEC Package"
"Reduction of Longslit Spectroscopic Data Using IRAF"
"Reduction of Echelle/CCD Data Using IRAF" I need the first two more than the last one at the moment.Thanks again, Mark

Hello Mark, I'll try and answer the IRAF configuration questions you
recently asked. You might want to talk on the phone about some of
these ideas. > 1. I wish to have the pixel directory in a subdirectory below the
> current subdirectory I am in. This maintains the file and directory
> structure I prefer to use for my data reduction and analysis. How do I
> change mkiraf so that it creates the pixel directory with name say
> "images" in the subdirectory I currently am in?A couple of points... If you change mkiraf ($hlib/mkiraf.csh), every user
who runs IRAF and presumably executes mkiraf will be affected in the same
way. Secondly, mkiraf creates the default imdir directory and sets the
CL environment variable 'imdir' in the login.cl file. You could probably
fix up mkiraf.csh and the template login.cl file ($hlib/login.cl) so it
sets imdir to HDR$images/ and perhaps even creates this directory. But
mkiraf would only create the initial images subdirectory, the one below
your login directory. If you intend to have a separate pixel subdirectory
for each directory that contains image data, that is a more difficult
problem that I don't think can be easily solved. The simplest thing
would be to run the existing mkiraf, then edit by hand your login.cl file
to include
set imdir = HDR$images/
and make the directories yourself as needed. This is an interesting idea. > 2. I have arranged the various windows and their sizes on the screen the
> way I want them. I then use "save page layout" to save the settings
> back to my .sunview file. However, the next time I come into sunview
> and IRAF the windows and their sizes are still the old defaults. Do you
> know what the problem might be?I'd have to experiment on a Sun workstation before I can say much about
this. First, check the obvious. Check the file date on the .sunview file
to verify it is really getting updated. The .sunview file in your UNIX
login directory is read (by default) by sunview. Your UNIX login directory
can be different from your IRAF login directory. If you're doing this from
the IRAF account, note that the IRAF login directory should be
$iraf/local. So, assume the right file in the right directory is
getting updated. I recall from the last time I used toolplaces on
a Sun, you still had to edit the new .sunview file to take care of
the gterm and imtool commands because they extend beyond one line. Check
the $iraf/local/.sunview file for an example of what it's supposed to
look like and see what's different in the file created by
"save page layout". I can't come up with any other suggestions right now. > 3. Does the dataio command t2d read tape FITS images to disk in the same
> format that would be produced if I wrote an IRAF disk image file to a FITS
> disk file?Yes. That is, I think so. Both files should be readable with the IRAF
RFITS program. You can t2d a FITS tape to disk and read it with RFITS.Call me if you want to discuss any of this further, especially #1.Suzanne

Mark, I said something wrong in my previous mail. If your imdir has
been set to HDR$images/ and this directory doesn't exist, the directory
IS created for you as it is needed. So, there is no problem with
having several pixel directories, one for each directory that contains
image headers. These pixel directories will be created for you as needed.
This is true only if the HDR$ designation is used in defining imdir. If
you specify an absolute pathname for imdir that does not exist, you'll
get an error when the directory access is attempted. So, to have mkiraf put HDR$pixels/ (or whatever you prefer) in
your login.cl file, edit the template login.cl in the hlib directory.
Replace the reference to U_IMDIR with HDR$pixels/:
set imdir = "HDR$pixels/"Also edit out the mkdir command in $hlib/mkiraf.csh so it doesn't attempt
to create the pixel file. This is done near the end of the script;
comment this line out with a # sign: #whoami | sed -e "s;.*;mkdir $imdir/& 2> /dev/null;" | shI'll point out again that anything you modify in mkiraf.csh or the
template login.cl will affect all users. You still might prefer to
simply edit your login.cl file and replace the imdir definition with
HDR$pixels/. Sorry for the earlier confusion.Suzanne

Hi Mark,

I forwarded your questions to Jeannette Barnes. Frank Valdes
suggests you use BLKREP after stacking images with IMSTACK to get the
"duplicity factor" you want. This will work well, assuming the factor
is the same for each image being stacked. On the subject of pixel directories, there are several reasons
users prefer to have the pixel directory under their image header directory,
including "organization" and ease of tar backup as you mentioned. But,
you should not have a problem though with "pixel collisions". If you have
identically named images in different directories, their pixel files
can reside in the same imdir. A unique name is generated for each pixel
file.Suzanne

Mike, I reinstalled IRAF and built the testphot package on bullwinkle.
Notes on what I did are in $iraf/local/sj.notes. Remember if
users want pixel directories under their current working directory, they
can "reset imdir = HDR$pixels/" in their login.cl files. I think everything is all straightened out now!Suzanne

WARNING: I heard on the news this weekend that ther was a virus in
Internet!!!!My real question is this: What wil be the charge for a copy of IRAF
to run on a SPARC1 (Unix), that includes SAOImage. I will want it on
an Exabyte tape.Best Wishes to ALL of YouMike

Hi!
A couple of questions:
1) I have installed IRAF on a Sun4/370 to run both on the console and
on several Sparcstation1 machines which it serves. I have everything
working except the image display stuff. I am able to display images on
the console display, but not on any of the Sparcs. Everything else seems
to be working fine. I fire up imtool and gterm, get into the cl, and
when I try to use the display program, I get the following message:
cannot open device (node!imtool,/dev/imt1,512,512)
This looks like IRAF cant figure out the nodename of the Sparcstation I am
using -- but I can't figure out where I should be telling it that info!The documentation doesn't say anything about this, however. Can you PLEASE
help me?2) This is an administrative question: What are the hours of the IRAF
hotline telephone number? I tried calling yesterday evening around 5:00PM
PST, and for two hours this morning, and no one has answered...The number
I have called is (602)323-4160.....Is that correct?Looking forward to hearing from someone there real soon.Thanks!
Gaylin Laughline-mail:
INTERNET: gaylin@ipac.caltech.edu
BITNET: gaylin%ipac@hamlet
SPAN: ROMEO::"gaylin%ipac"telephone:
(818)584-2942

Hello Gaylin,Installing IRAF in networked environments was not fully described in
the Sun/IRAF installation guide. There is a brief additional note
about it in IRAF Newsletter #7, June 1989, "Things to Watch out for
in IRAF V2.8". If the /local/bin directory for the clients resides
on the server, the install script will have to be run on the server for
each client. Additionally, the install script makes entries in /dev
for imtool, so the script needs to be run on each client as well. It
sounds like you're just missing the /dev/imt* entries on each client,
so run install on each SPARCstation client.There is a recording machine on the HOTLINE number 24 hours a day; the
recorder picks up after 3 rings. I am here to answer the phone mornings
only, approximately 8-12 MST. You have the number right (602-323-4160).
You should have gotten through this morning, as I've been either on the
phone or sitting next to it all morning (except for working at another
terminal from approximately 9:45 - 10:15)! Give me a "test call" if
you like after receiving this message.Suzanne Jacoby
sjacoby@noao.edu
5355::sjacoby or noao::sjacoby
(602-325-9364)
(602-323-4160 IRAF HOTLINE with an answering machine)

Tony, the ..*.imh files are a feature, used to protect the image headers.
They are hard links to the image header and prevent a user from deleting
the header with the DELETE command. If the headers weren't protected,
users could delete only the header, leaving behind an orphaned pixel
file. This was described in detail in IRAF Newsletter #6 (Feb 1989).
The scheme works well unless someone uses the UNIX rm command to delete
a header file. In that case, the ..imh link remains, consuming disk space.
The bottom line is to always use IMDELETE to delete an IRAF image. It
unprotects the header (that is, deletes the ..imh file) and then deletes the
header and pixel file.Suzanne