iraf.net

Hi, we've just installed 4.1.1, and as a result I need to know where to
put saoimage etc. so it will run under openwindows. Thanks.eric howard
ehwd@uorpas.bitnet
vampyre@milton.u.washington.edu

Hi Eric, I have looked through the mail you and Chris Biemesderfer have
exchanged, and think you got SAOimage from us in the form of saoimage.sun4.Z,
saoimage.tar.Z and possibly readme.saoimage. The saoimage directory tree
should be installed outside the IRAF directory tree so it survives future
IRAF updates. Something like /usr/local/src/saoimage or maybe
/usr/X11/src/saoimage would be good choices. The saoimage executable itself
goes in your "localbin" directory, /usr/local/bin for example. This directory
must be in your default search path.Suzanne Jacoby

I currently have the X11 Beta 1.02 version of saoimage.
It is dated 12 Dec 89. Is that the latest version.We are having troubles printing images.An empty image appears to print OK.A real image seems to print in diagonal
segments. Like a patchwork quilt.cat
Cathy Accettura
Space Astronomy Lab
Universion of Wisconsin
608-263-4678
cathy@sal.wisc.edu
UWSAL1::CATHY

Cathy,
We are in the process of integrating some recent bugfixes into saoimage.
Make sure your saoimage geometry size (-gd on command line) is exactly the
same as your stdimage setting in iraf. E.g., if you opened saoimage with
"saoimage -gd 1144x764", you would have to use "set stdimage=imtfs35". To
examine the match between geometry and stdimage: % grep imt /usr/local/lib/imtoolrcThere are several versions of saoimage in our ftp archive that might be
slightly more recent than the one you have depending on what machine you
are running it on -- see the readme.sao* in ~ftp/iraf.old on iraf.noao.edu.
I hope to have an updated version tested and in the archive sometime in the
next couple of weeks.Steve Rooke (iraf@noao.edu)

Is there a later version of SAOimage for VMS than 1.02 beta?
Also, is there a newer version of xterm?ThanksWarren
============================================================
Warren R. Sturm (403) 240-6485
Senior Systems Programmer -----------------------------
Mount Royal College | WRSturm@Janus.MtRoyal.AB.CA |
4825 Richard Road S.W. | WRSturm@UCNET.UCalgary.CA |
Calgary, Alberta CANADA -----------------------------
T3E 6K6

Warren, At the moment, the SAOimage version that you have is as current as
it gets. However, we are working on some bug fixes, etc. to the program
this week, so there will probably be something newer rather soon. You may
want to check back with us in a week or two to see. A newer version of xterm than what? The version we have is from
Stephan Jansen at Wisconsin, although I think it has been modified a bit
here by Nigel Sharp. It was built here last in April 1990.Chris Biemesderfer
IRAF Group, NOAO
iraf@noao.edu

To: Chris Biemesderfer,Dear Chris,
Oh boy am I ever dumb. I forgot to run the setup.com. I put it in the
login.com, and then took it out for some reason. Anyway, I fixed that. Now
I get a large window, and I try to fill it with an image, I get a gray image
filled with rows of thin, short black lines. There are also some streaks of
white interspersed. The image stops about halfway up, then suddenly shrinks
(in y only) and a thick white line sits at the top. And that's it. I know
what my image looks like, and this ain't it!! What now? What other simple
stupid thing have I forgotten to do? I have reset [iraf.vms.hlib]zzsetenv.def
to stdimage=imt29. I also tried resetting it to imt512 (the original setting)
to see if it still works, and it does. Now, I notice that there is a line
in graphcap., to wit
imt1|imt512| etc
and stdimage is not set to imt1 in the original zzsetenv.def, but to imt512.
I wondered, therefore, whether I should have set stdimage to imt29, like you
said, or imt832, since I now have a line
imt29|imt832| etc
in graphcap.
Is this too confusing? It is for me!
As for Xterm, I have been working with Nigel Sharp on that problem, and he
has been a big, big help, but so far no luck fixing it. We've had memory
problems on the workstation, and Nigel now wonders if that's it. I received
email from him this morning about various factors to check out.
Let me know if you know what's going on with SAOimage. I apologize
profusely in advance if it's some simple dumb thing.
Angie Schultz
C1796A@SLVAXA.UMSL.EDU

Angie,

The several names separated by "|" characters on the first line fo
the graphcap entries are all aliases for that entry, so you can can use
whichever one is easier to remember. The streaked display sounds rather
like an IPC screwup (VMS uses mailboxes for interprocess communication,
and I don't know if SAOimage/IRAF use synchronous or async [async would
be my guess]). So I will have to look at some code, and talk to Nigel
myself, and perhaps try some experiments. I will get back to you later today after I learn more.Chris B.

Angie, The streaking you describe is probably due to a disagreement between
SAOimage and IRAF about the size of the frame buffer. In other words, there
is most likely something amiss in the way that you carried out the recipe I
sent the other day. Perhaps you should send me the relevant chunks of the
graphcap and imtoolrc files so we can be sure they are OK. I have tried this arrangement on a VAXstation we have here, and it
works as expected. (Except I don't have an image the size of the frame
buffer, but that's OK.)Chris B.

To: Chris BiemesderferDear Chris,
OK, here are the chunks of [iraf.dev]graphcap. and [iraf.vms.x11]imtoolrc.
I have included a few surrounding lines for comparison. I checked them for
anything wrong, but couldn't find it.
Thanks,
Angie
P.S.
In the graphcap. entries, what are the cn# for? I notice that all the
entries have cn# that match their imt numbers, but when you gave me the
line you said to use cn#11. Is this important?graphcap.
imt28|imt2df9x3|2D-Frutti detector format:cn#28r#976:yr#3040:\
:LC:BS@:z0#1:zr#200D=node!imtool,/dev/imt1,976,3040:tc=iism70:
imt29|imt832|:cn#11r#832:yr#800:\
:LC:BS@:z0#1:zr#200D=node!imtool,/dev/imt1,832,800:tc=iism70:
imtoolrc.
# Some site specific formats for NOAO.
20 2 388 576 # imt20|imtgec GEC CCD detector format
21 1 3040 976 # imt21|imtkpca KPCA detector format (also 2D-Frutti)
22 1 128 1520 # imt22|imt2df1 2D-Frutti
23 1 256 1520 # imt23|imt2df2 2D-Frutti
24 1 512 1520 # imt24|imt2df5 2D-Frutti
25 1 960 1520 # imt25|imt2df9 2D-Frutti
26 1 512 800 # imt26|imtcryo Cryogenic Camera
27 1 348 800 # imt27|imtgcam Gold Camera
28 1 976 3040 # imt28|imt2df9x3 2D-Frutti
29 1 832 800 # imt29|imt832

Where possible, people should not have to build saoimage from the sources
in the network archive. We should supply binaries instead (or more
precisely, in addition). The recent mail from Eric Smith is an example.
I also helped Pat Waddell in Seattle try to get saoimage going under
OW on a Sparc 2 and it would not build correctly. Let's avoid all these
problems and just give people working and tested executables for the more
popular systems. Buildable sources should also be provided but should
not be needed by most users.

Eric, rather than try to build saoimage, have you tried the prebuilt
executable from the iraf network archive? This is the file saoimage.sun4.Z
in the iraf.old directory. Doug

Steve, we need some more information before we can help you with this.
Is this a Sun-3 or a Sun-4? Did you build the saoimage executable yourself
from the sources on this system? What are you using for graphics - xterm?
Doug Tody

hiho - eric howard's been talking to you about saoimage and openwindow
matters, as i've been informed. i'll log off the issue and let him deal
with it. on the other hand, i've another question concerning the use
of tvmark. it apeears to do 2 funny things:
1. when i use it to save a frame consisting of two separate
images (created using the xycenter, xysize params of display)
the background and text are inverted (black on white -->
white on black) then when i pull up the saved image to try and
add some text to it, the text is a 'darker' black on black???? 2. in the same frame as above, the pixel values are higher by
roughly a factor of two in the frame saved by tvmark than the
original. the pixels are also short type when they started out
as real.is this clear?? i somehow doubt it. thanks muchly. slso@uordbv

Bill: I have had IRAF and SAOimage running uninterrupted for two weeks now.
This is on a VAXstation 3100 running IRAF V2.9.1 and VMS 5.3-1. I display the
dev$pix image to the SAOimage window at least twice a day and have yet to see
the error you report. Suzanne