Welcome to iraf.net Monday, May 20 2024 @ 02:40 AM GMT


 Forum Index > Archives > Sitemail Archives
 Fwd from Dave Harris
   
Anonymous: Guest
 01/20/1994 10:03PM (Read 1034 times)  



>From harrisd@ll.mit.edu Thu Jan 20 12:26:57 1994
From: harrisd@ll.mit.edu ( David Harris)
To: fitz@noao.edu
Subject: A little help, please!Mike,I think I've gotten IRAF V2.10 and SAOimage more or less installed on our
Sun SPARC 10 under SunOS 4.1.3, but there are obviously are few more
minor adjustments I need to do that I haven't figured out from the documentation
in the network distribution. Could you please point out what I'm missing for
this problem in testing the connection of SAOimage to IRAF:I'm trying to do the simple test suggested in the TESTING SAOIMAGE section of
README.SAOIMAGE, which looks like this:% xterm -ls & works fine, sets up an xterm windowcl> stty xtermjh also works
cl> images shows the commands under images
cl> tv works, too
cl> reset stdimage = imtool
cl> reset stdimcur = stdimage(oops...cl> should have been im> after images and tv> after tv)tv> display dev$pix 1this last command yields this error message:ERROR: Cannot open device (node!imtool, /dev/imt1,512,512)As I understand this test, it should display the test IRAF image in the
directory .../iraf/dev, which I assume is pix.pix. I've tried to follow the
recommended directory structure for the IRAF and SAOimage files, and the
pix files are in the dev directory. There are also the imt entries in the
/dev directory.I suspect the problem is a fairly minor one, but as I'm neither a Unix nor
a C guru, I'm a bit in the dark about what file(s) to modify to get things
working.FYI, SAOimage seems to be working fine in its standalone mode, i.e., from
an IRAF user directory, the path is correct to start it and typing the
command saoimage moon.fits, for example, brought it up and displayed a
small FITS file with a moon image.Any suggestions you could offer would be very much appreciated!Dave Harris>From fitz Thu Jan 20 12:39:08 1994
To: harrisd@ll.mit.edu
Subject: Re: A little help, please!Hi Dave,
Be sure that you have SAOimage running before you attempt to display,
it can be iconified but it must be running. If that's not the problem then
be sure saoimage is working as an IRAF server: when it starts up it should
say "Open to accept IRAF input" before the banner. The newer versions of
SAOimage had the "-imtool" flag meaning changed to DISable iraf communications,
the correct syntax is "+imtool" but this is the default anyway so no flag
is needed at all.
Lastly, be sure that the fifo pipes needed for communication are in
place, they should have been created when the system was installed: pisces> ls -l /dev/imt*
1 lrwxrwxrwx 1 root 10 Jul 8 1992 /dev/imt1 -> /dev/imt1o*
0 prwxrwxrwx 1 root 0 Dec 8 17:11 /dev/imt1i*
0 prwxrwxrwx 1 root 0 Jan 13 16:31 /dev/imt1o*Also be sure that the '/usr/local/lib/imtoolrc' configuration file is there.
If this doesn't solve it write back, there are other reasons that could ex-
plain the error message you see.Cheers,
-Mike

 
Anonymous: Guest
 01/20/1994 10:03PM  



>From harrisd@ll.mit.edu Fri Jan 21 14:06:03 1994
To: fitz@noao.edu
Subject: Re: A little help, please! Mike, I checked the things you suggested and everything was OK
with the SAOimage startup, the /dev/im* files, and the
/usr/local/lib/imtoolrc file. So, apparently, there was no problem other than my not
understanding the SAOimage needed to be running first. I've
now got a nice display of the test image. Hopefully, if I can persuade my boss to spend a few bucks,
I'll be able to order a set of the IRAF manuals so that I
can learn how to use it without having to bother anyone with
easy to answer questions. Thanks again!
Dave Harris>From fitz Fri Jan 21 14:56:38 1994
To: harrisd@ll.mit.eduHi Dave,
Glad things seem to be working. If you need to order hardcopy docs
nab the file 'ORDERFORM' from our archive iraf.noao.edu in the iraf subdirec-
tory. For free you can look around in the iraf/docs subdorectory and pull over
compressed PostScript of what you would pay for (and much more!). The 'README'
file in there serves as a table of contents, there are also TOC files for the
hardcopy docs so you can bind them yourself if needed. Lastly, I's also
recommend the "Beginner's Guide" which is currently in the pub directory as
'beguide.ps.Z' but should move into general distribution soon. Let me know
if you need anything else.Cheers,
-Mike

 
Anonymous: Guest
 01/20/1994 10:03PM  



>From harrisd@ll.mit.edu Wed Jan 26 06:12:31 1994
From: David Harris <harrisd@ll.mit.edu>
To: fitz@noao.edu
Subject: Re: A little help, please! Mike, I've been tinkering with IRAF yesterday and today, and I'm
quite impressed with its capabilities. The Beginner's Guide
was helpful as an introduction. Now, if I can only get my
hands on some real data until our CCD camera arrives! Thanks again,
Dave Harris

 
Anonymous: Guest
 01/20/1994 10:03PM  



>From harrisd@ll.mit.edu Thu Jan 27 14:55:37 1994
From: harrisd@ll.mit.edu ( David Harris)
To: fitz@noao.edu
Subject: SAOimage display problems for certain imagesMike,Things are moving along pretty well for me with IRAF, except for the
problem I'm still having displaying some images. I've also tried imtool,
but it seems to have the same problem for the same images and also I
find using IRAF from an xterm with SAOimage more user-friendly than
IRAF from a gterm with imtool and SunView.Do you have Rick White's hcompress software? I assume its on some machines
at NOAO because of its use in the WIYN protocol, which I've been talking
to Jeff Percival about.White has a 256x256x16 test image, test1.fits, that he used for the figures
in his paper on his compression algorithm. That image is one of the ones
that won't display properly with SAOimage, though I can display it with
no problems on a PC using Michael Richmond's PCVISTA software. Also, I've
found that PCVISTA will display all the FITS images I have, including
others that SAOimage has problems with.Do you have any suggestions and/or do you know an email address for the
SAOimage programmers at SAO?Thanks in advance,Dave Harris>From fitz Thu Jan 27 15:18:42 1994
To: harrisd@ll.mit.edu
Subject: Re: SAOimage display problems for certain imagesHi Dave,
I looked around locally and couldn't find the test1.fits image you
mentioned, could you put it in our ftp pub directory so I can experiment
with it here? The original SAOimage author, Mike Van Hilst, left SAO a
while back, this is an all but frozen project although we do make occassional
bug fixes and support it here as best we can. If you could get me the image
I'll see if I can figure out what's happening and supply a patch for you
if it's something simple. Do you know whether or not these problem images
can be read/displayed from IRAF?Thanks,
-Mike

 
Anonymous: Guest
 01/20/1994 10:03PM  



>From harrisd@ll.mit.edu Fri Jan 28 12:00:30 1994
From: harrisd@ll.mit.edu ( David Harris)
To: fitz@noao.edu
Subject: test1.fitsMike,I've ftp'ed Rick White's test1.fits file to /pub on iraf.noao.edu.The file is a 256 x 256 x 16 image from one of the laser-scanned Palomar
plates they used at STSCI to produce the CDROM sets that the ASP is now
selling. I can display it with Michael Richmond's PCVISTA program on
a PC, which seems to work for all the FITS images I have.But, using either saoimage in its standalone mode or sending the image
to it via the IRAF display command doesn't yield anything close to the
correct image.The only clue I have is this warning information produced by Barry
Schlesinger's (I'm not sure I've remembered his name correctly) tool,
listfits, which says:"NOTE! Not an integral number of 2880-byte FITS records.
NOTE! File contains 283r374 512-byte records.
ERROR! Bytecount not a multiple of 2880 or 512 !!"So far, ever image for which I've had the display problems has had
a warning message like this from listfits and every one that displays
properly doesn't have a warning message. Perhaps, saoimage expects
FITS files to conform totally to the FITS specifications (or to some
earlier version of them than the PCVISTA program). I've also noticed
that the same problem occurs for IRAF image files of the same images
that I produced using the rfits task.I think it would be a good idea to get this problem fixed. The reason
is that a lot of people will probably start making use of Rick White's
compression software. So, if the uncompressed files it produces can't
be displayed by saoimage, that might turn out to be a problem for lots
of people.Dave HarrisP.S. Regarding IRAF and saoimage, it looks like the software has been
written to permit remote displays of images via the X-Windows software.
If that is correct, is that capability used much between Kitt Peak and
observers at remote sites? I've gotten the impression from Jeff
Percival and from some of the people working at Apache Point that
remote image viewing and remote operations using X-based software tends
to require significant bandwidth, e.g., that even a 56 kilobit/second
link is too slow. Is that the general consensus of opinion where you
are?>From fitz Fri Jan 28 12:15:22 1994
To: harrisd@ll.mit.edu
Subject: Re: test1.fitsDave,
Thanks for the file. The bad news I'm afraid is that I just displayed
this image with SAOimage V1.07 in standalone mode and it looks fine. If
I read it into IRAF and display it also looks fine. Even the FITS file in
out archive is 135360 bytes long (i.e. 47 2880 byte blocks).
I guess the first thing to check is what version of SAOimage are you
running? I check here using V1.06 and V1.07 (the version is printed in the
banner message when it first comes up). In an earlier message you said you
brought IRAF up on a Sparc-10 running SunOS 4.1.3, this this the same machine
with the problem display? I could get the FITS tools from Schlessinger's
machine but as far as I can tell this is a normal FITS file.> P.S. Regarding IRAF and saoimage, it looks like the software has been
> written to permit remote displays of images via the X-Windows software.
> If that is correct, is that capability used much between Kitt Peak and
> observers at remote sites?
I believe Bill Keel has done some "lurking" of KPNO observing runs
from Alabama with moderate success. Certainly using X networking allows for
displaying of images remotely (I've run saoimage on a machine in Australia
and displayed them in my office, it took a while....but). I'm not sure how
widely used this is, someone else in the group who knows more may comment
further.Cheers,
-Mike

 
Anonymous: Guest
 01/20/1994 10:03PM  



>From harrisd@ll.mit.edu Fri Jan 28 14:09:28 1994
To: fitz@noao.edu
Subject: Re: SAOimage display problems for certain images Mike, I've ftp'ed the test1.fits file and sent you a more detailed
message from another machine. Dave>From fitz Fri Jan 28 18:28:16 1994
To: harrisd@ll.mit.edu
Subject: Re: SAOimage display problems for certain imagesHi Dave,> I've ftp'ed the test1.fits file and sent you a more detailed message from
> another machine.
I never got an message other than the one saying you transferred the
file to our archive. Did you mean perhaps that you have the FITS file on two
different machines? This is what I get for the file you transferred: pisces> ls -l test1.fits
144 -rw-r--r-- 1 ftp 135360 Jan 28 11:39 test1.fits
pisces> sum test1.fits
56585 133Do you get something different? Maybe the file was just corrupted there
somehow?-Mike

 
Anonymous: Guest
 01/20/1994 10:03PM  



>From harrisd@ll.mit.edu Mon Jan 31 06:20:37 1994
From: David Harris <harrisd@ll.mit.edu>
To: fitz@noao.edu
Subject: Re: test1.fits Mike, Thanks very much! The information in your message was just
the clue I needed to figure out most of the problems. It
appears the display problems for some files were due to my
failure to use the ftp bin switch for each file I
transferred from my PC to the SPARC when it arrived earlier
this month. I transferred those files for which I had
display problems again with the bin switch and with saoimage
they now display properly. In other words, an operator
malfunction on my part! The problem I'm left with now is figuring out why White's
fcompress/fdecompress programs work for his test file
test1.fits, but not for the FITS files I've produced using
the IRAF irafil program from some square 420x420 binary CCD
image files. The files produced by irafil are displayed by
saoimage just fine, but the FITS file that results from
compression and decompression has some problem, since the
size of the FITS file is smaller and saoimage apparently
isn't happy about that. Anyway, sorry to trouble you for a stupid mistake on my
part, but you've got me back on track again. The version I've installed is V1.07. I would be interested to hear from anyone else in your group
about remote display of images, remote observing, etc. Have a good weekend...did you get some snow out of this
latest storm system that is now in New Mexico? Dave Harris>From fitz@pisces Mon Jan 31 08:19:58 1994
To: harrisd@ll.mit.edu
Subject: Re: test1.fitsHi Dave,
Glad that was solved, if you do find any FITS images with display
problems please let us know so we can figure out what might be wrong. The
IRAFIL task converts a binary file to an IRAF image. If this binary file is
really a FITS image you should be using the RFITS task in DATAIO. If this
is the output of the compression programs runon the PC the problem may just
be that on the PC the bytes are swapped (transferred in binary mode or not)
relative to the PC. You can use the REBLOCK task to swap the bytes or use
the unix command % dd if=binfile of=swapfile conv=swabNote that floating point pixels on the Sun are IEEE as well. Hope this gives
you another clue, let us know if we can be of any more help.
Unfortunately we didn't get any snow, "cold" temps in the 60's but
that's about all. It's been a rough winter here 8-)Cheers,
-Mike

 
Anonymous: Guest
 01/20/1994 10:03PM  



>From harrisd@ll.mit.edu Mon Jan 31 10:05:15 1994
From: David Harris <harrisd@ll.mit.edu>
To: fitz@noao.edu
Subject: Re: SAOimage display problems for certain images Mike, I'm replying from a PC, since the Lab has a "gateway"
computer that forwards all incoming mail to users via a
Novell network to which our remote field site in New Mexico
is connected. The other message was sent to you from my
account on that gateway machine, which is more convenient to
use for things like ftp. Anyway, I think the source of almost all my problems was
just due to not using the "bin" switch when I ftp'ed some of
the image files from this PC to the new Sun SPARC 10 that we
received on 3 January. So, that would be just a screwup on
my part. But, it could have been caused by some problem
with the "File Express" Windows tcp/ip software on the PC (I
think that stuff came with or was required for the
Hummingbird Exceed X-terminal emulation software that the
Lab has purchased for us). That software does have some
flaky behavior. The bottom line is that you provided the clue that enabled
me to get uncorrupted images on the SPARC that display OK. So, now my problem is figuring out whether the problem I'm
having with compressed (lossy) and decompressed FITS image
files produced by Rick White's fcompress/fdecompress
programs is due to my not fully understanding how to use it
yet, or to some bug, or to some other problem. Thanks again for you assistance. Dave Harris P.S. Is there any ftp'able document that provides an
overview of the contents and capabilities of the layered
packages STSDAS and XRAY mentioned in Appendix F of the IRAF
Beginner's Guide? What I've trying to put in place on our
SPARC is a complete system for these kinds of work: - display, manipulation, and analysis of CCD images
of sizes from about 420x420 to 2048x2048, with up
to 16 bits/pixel. It looks like IRAF + SAOimage can do most of that. - CCD photometry: both on individual frames for the
purpose of camera sensitivity testing and other
experiments and time-series type photometry of
rapidly-varying objects (say, at about a 100 Hz
maximum rate) It appears that IRAF has the individual frame
capability with digiphot, DAOPHOT, and other
packages. - CCD astrometry: astrometry of one or more target
objects with a CCD frame with respect to known
stars within that frame or other information It appears that IRAF might have or will soon
have this capability...is that correct? - Time series analysis, light curves, etc. This would software to do things like displaying
time series of CCD photometric data, integrating
the data (for equally-space samples), FFTs,
filtering, etc.
>From fitz Mon Jan 31 11:16:26 1994
To: harrisd@ll.mit.edu
Subject: Re: SAOimage display problems for certain imagesDave,> P.S. Is there any ftp'able document that provides an overview of the
> contents and capabilities of the layered packages STSDAS and XRAY mentioned
> in Appendix F of the IRAF Beginner's guide

User documentation for STSDAS and XRAY can be found in the archives
stsci.edu:software/stsdas/v1.3/doc/user and sao-ftp.harvard.edu:pub/pros/PUG
respectively. You can contact the people developing this software by writ-
ing to hotseat@stsci.edu (STSDAS) and rsdc@cfa.harvard.edu (XRAY).
I should also point out that an easy way to "browse" the system is
with the REFERENCES task, e.g. cl> refer photomgets you a list of all tasks with the phrase 'photom' in the description.> - display, manipulation, and analysis of CCD images of sizes from about
> 420x420 to 2048x2048, with up to 16 bits/pixel. It looks like IRAF + SAO-
> image can do most of that. I hope so!> - CCD astrometry: astrometry of one or more target objects with a CCD frame
> with respect to known stars within that frame or other information A full-blown astrometry package is yet to be written, but it is
possible to do some astrometry with the FINDER package which is based on
a non-IRAF task called ASTROM. Write back to iraf@noao.edu for more info on
this, I'm not fully aware of it's capabilities, limitations or availability.
A list of tasks include
astrom -- Host level `astrom.f' program
catpars -- Catalog column description pset
cdrfits -- Read FITS tables from the GSC CDroms
gscfind -- Search the GSC index for sources within a field
hydrahints -- Phil's hints for Hydra users
redo -- Reperform a fit after editing the ASTROM input
selectpars -- Source selection criteria pset
tastrom -- Script frontend for ASTROM foreign task
tfield -- Extract sources within a field from a list of tables
tfinder -- Search and read the catalog, predict and measure the coords
tpeak -- Interactively center objects from a tableI believe there are also various tools in STSDAS to help with this.> - Time series analysis, light curves, etc.
Again have a look in STSDAS. They have a TIMESERIES package as well
as a FOURIER package that may so what you need. The PDM task in the (iraf)
ASTUTIL package can be used to find a period from light curves. I doubt there
is anything currently that can do 100Hz if you mean this to be a real-time
rate.Cheers,
-Mike

 
Anonymous: Guest
 01/20/1994 10:03PM  



>From harrisd@ll.mit.edu Mon Jan 31 15:45:54 1994
To: fitz@noao.edu
Subject: Re: test1.fits Thanks again for responding. Today, I resolved the
remaining display problem and it had nothing to do a problem
in SAOimage or IRAF. It turns out the Rick White's image
compression software can only accept 16 bit pixels FITS
images. In my eagerness last week to try things out, I
assumed that irafil would convert an input binary image with
16 bits per pixel into a 16 bit IRAF file that I could then
could to a 16 bit FITS file with wfits. Well, I was wrong
because the IRAF file was 32 bits and I needed a switch on
wfits to get the 16 bit FITS output. Once I understood
that, it was a simple matter to convert a bunch of binary
files via IRAF to FITS files of the desired format, with
which I'm now experimenting. There must be some law of human nature that, if you give an
adult a fancy new tool to play with like a workstation
running a powerful tool like IRAF, that adult will
invariable be too eager to play with the tool to read the
instruction manuals for it! From your messages, it appears that you may not be familiar
with Rick White's image compression software? If you
aren't, please let me know and I'll email you some
information about it. Dave Harris>From fitz Mon Jan 31 15:54:28 1994
To: harrisd@ll.mit.edu
Subject: Re: test1.fitsHi Dave,
> There must be some law of human nature that, if you give an
> adult a fancy new tool to play with like a workstation
> running a powerful tool like IRAF, that adult will
> invariable be too eager to play with the tool to read the
> instruction manuals for it!
I hope not, but you're probably right. We're working on some GUI tasks
for IRAF now and I'm trying to get my code smart enough so any user just pushing
random buttons will get something to happen and not hang the system. Of
course there *is* a HELP button, but that's the last one ever hit....8-)> From your messages, it appears that you may not be familiar
> with Rick White's image compression software? If you
> aren't, please let me know and I'll email you some
> information about it. Yes, please. I've heard of this but I'm not sure we have it locally
anywhere. I just saw where a KPNO observer this week (last?) wanted to
compress the data and transfer it back to his own site ASAP. It would be
useful to have around, especially if people will start using it in connection
with IRAF processing. Thanks.Cheers,
-Mike>From harrisd@ll.mit.edu Mon Jan 31 16:10:22 1994
To: fitz@noao.edu
Subject: Re: test1.fits Mike, I've got to go now, since the site van will be leaving soon,
but I'll email you information about White's algorithm and
related work tomorrow. I'm sure you'll be very interested
in it. Dave

 
Anonymous: Guest
 01/20/1994 10:03PM  



NOTE: I found that we already have the HCOMPRESS stuff unpacked in /u3/extra
on tucana. The paper this is based on that Dave mentions is in the doc
subdirectory.
>From harrisd@ll.mit.edu Tue Feb 1 09:47:20 1994
To: fitz@noao.edu
Subject: Re: SAOimage display problems for certain images Mike, Thanks for the pointers to the STSDAS and XRAY
information...I'll check them out...and for the information
about the other packages. Here's some information about Rick White's software: The purpose for which he developed his image compression
software was for the "Compressed Digitized Sky Survey on
CD-ROMs", some of which is now available for purchase from
the Astronomical Society of the Pacific. This project at
STSCI used a laser scanner to scan and digitized about 1,500
photographic plates from the "southern SERC J band survey"
and the "northern Palomar E-band survey" to produce (I
think) 1,500 14,000 x 14,000 16-bit/pixel digital images. Obviously, that's quite a bit more data than most people's
systems can handle, so part of the project involved
developing an image compression algorithm to convert
smaller-sized raw images into compressed versions that would
still retain reasonable astrometric and photometric quality.
Sets of those images at two different levels of compression
would be reproduced on CDROMs and sold (the sets aren't
cheap: the price is $2,900 for orders before 15 February,
but $3,500 after that...so be sure to get your check in the
mail soon, Mike Smile The problem was compressing typical astronomical images from
photographic plates, CCDs, etc., is that they contain lots
of localized, point sources, which implies high spatial
frequency content. There are lots of popular data and image
compression methods, but none of them are very well suited
for such imaged. For example, the JPEG compression scheme,
which is very popular now, uses the Discrete Cosine
Transform on small blocks of the image and it achieves
compression large by throwing away the coefficients of the
high frequency terms. Thus, using JPEG for astronomical
images would introduce undesirable artifacts when images
with point sources undergo lossy compression and then
decompression to a viewable or processable image. So, White developed an algorithm based on a two-dimensional
Haar transform (a sort of wavelet transform). I don't think
the idea is his, since his paper cites work 10 to 15 years
ago along the same lines. But, you can get a copy of his
software that runs on Unix or VMS systems and try it! Here's where to get his software and its documentation: ftp to stsci.edu and usual anonymous ftp login
procedure change to the directory /software/hcompress In it you'll find these files: OWNER (text)
aareadme (text)
backup.com (text, for VAX)
hcompress.bck (binary, VAX Backup file)
hcompress.tar.Z (binary, Unix tar.Z file)
modify.exe (binary, VAX program) The backup.com program unpacks the files in hcompress.bck
on a VAX. The modify.exe program (if my memory is correct)
is needed to adjust the record lengths of some files on
VAX/VMS systems. I installed his software last summer on
a VAX here, but could do much with it since I had no display
capability and no CCD images to work with. But, the
installation was easy and the code worked. The Unix stuff is in the .tar.Z file. It, too, is easy to
install and I did it on several Unix systems that could run
the code, but with no display capabilities, until we got
our SPARC. In fact, I think my boss back at the main Lab
was impressed enough with White's algorithm and his test
cases that he was able to get the money for the SPARC for
me to develop code starting with White's code. The documentation is in OWNER, aareadme, and in files
inside the VAX and Unix archive files. It consists of
instructions on how to install the software on either
kind of system, Unix "man" pages for the executable
commands (hcompress, hdecompress, fcompress, and
fdecompress), and a PostScript file containing his
paper: "High-Performance Compression of Astronomical Images" I don't remember if the paper was published in a journal
or not. The paper contains the older references that
I mentioned above, and I've managed to accumulate most
of them. If you want the exact titles, etc., for any
of them, just let me know. There is also a related paper: "Efficient Transfer of Images over Networks"
J. W. Percival and R. L. White

that was published in "Astronomical Data Analsis
Software and Systems II", which is Volume 52 in the
ASP's Conference Series. Percival is the fellow at the Univ. of Wisconsin's Space
Astronomy Laboratory who has been integrating White's
software into a TCP/IP-based communications protocol
that will be used for the WIYN telescope and, it appears,
for others as well. I've talked to Jeff Percival about his
work and he has been very helpful, even providing to me a
copy of his code that I have installed on the Sun SPARC. Finally, here are their email addresses, in case you need
them: White: rlw@stsci.edu Percival: jwp@bernie.sal.wisc.edu I found both of them to be very helpful, though you may
not get an quick response from Rick White, since he's
been very busy for the past few months, probably, because
he has been involved with the pre-fix HST image restoration
work and with the preparations for and testing of the
HST hardware changes. Dave Harris
>From fitz Tue Feb 1 10:45:04 1994
To: harrisd@ll.mit.edu
Subject: Re: SAOimage display problems for certain imagesHi Dave,
Thanks for the information, I'm sure it will come in handy. Turns
out that on an obscure part of our disk we already have the software, I
just didn't know about it. Your notes also help explain things more clearly.
I only hear things occassionally about remote observing at KPNO, the
person to contact would be Rob Seaman (seaman@noao.edu) who is the IRAF pro-
grammer responsible for the ICE (IRAF Control Environment, an IRAF based
data aquisition system) on the mountain. He's worked with observers who
have tried remotely working on the mountain and would know how well that
has worked in the past.Cheers,
-Mike

 
Anonymous: Guest
 01/20/1994 10:03PM  



From: David Harris <harrisd@ll.mit.edu>
Message-Id: <9402011308.AA07130@LL.MIT.EDU>
To: fitz@noao.edu
Subject: Re: SAOimage display problems for certain images Thanks for the point of contact. I'll send some questions
by email for Seaman. I'm particularly interested in getting
people's impressions of how well existing remote observing
systems work, what problems they have, what people are
planning for the future in the way of enhancements or new
systems, etc. Just as with packages like IRAF, it doesn't
make sense to waste the taxpayer's money developing software
if someone else already has done all or most of the work you
would be duplicating. Dave

 
   

Normal Topic Normal Topic
Sticky Topic Sticky Topic
Locked Topic Locked Topic
New Post New Post
Sticky Topic W/ New Post Sticky Topic W/ New Post
Locked Topic W/ New Post Locked Topic W/ New Post
View Anonymous Posts 
Anonymous users can post 
Filtered HTML Allowed 
Censored Content 
dog allergies remedies cialis 20 mg chilblain remedies


Privacy Policy
Terms of Use

User Functions

Login