iraf.net

From: "Chuck F. Claver" <claver@noao.edu>
Date: June 16, 2005 12:42:14 PM MST
To: Frank Valdes <valdes@noao.edu>
Subject: Questio on RTEXTIMAGE
Frank,Sorry to bother you again.I am trying to read in some calculated diffraction images from some
LSST modeling using the IRAF task RTEXTIMAGE. The input data are
text files having a format of 512x512. I have put these up on my ftp
area on taurus.tuc.noao.edu. Their names are:test.dat
test.dat.TXT
shortsys_cfg0_angpos0_scaled.datThe last file is the original file that has 4 lines of additional
information. The first file is this original file with the first
four lines stripped out. The second file is the same data as the
first but reformatted and tab deliminated.When I try to read these with RTEXTIMAGE I always get an image that
is garbage and on the reformatted file I also get the following
messages:Premature EOF seein rt_rfpixels
Premature EOF seein rt_rfpixels
Premature EOF seein rt_rfpixels
ERROR: floating point overflowOddly when I use the original file format I do not get this message
even though the line lengths are longer. I have tried increasing the
value of SZ_LINE to 32767 in iraf.h, but this doesn't seem to affect
the behavior any.Is there something else I can do? or am I doing something stupid here.Chuck
From: Frank Valdes <valdes@noao.edu>
Date: June 17, 2005 9:59:55 AM MST
To: Chuck F. Claver <claver@noao.edu>
Subject: Re: Questio on RTEXTIMAGE
Hi Chuck,The premature EOF may be a misunderstanding of the format for the
"dim" parameter. I often use a whitespace separated list when it has
to be comma separated. It gives me the premature EOF error. As to
the long lines and the ^M's in the input, the way I would deal with
it is:cl> words test.dat | rtext STDIN image head- dim=512,512I believe this produces the image you want since I don't know what it
should look like. I note that you have some numbers with e-002 in
them. I don't know if that is a problem or not with the way the
image looks.The WORDS command turns your list into one pixel per line to avoid
any long line problems. Of course if there is a header this would
cause problems. I tried with and without removing the ^M's but the
image was the same so it looks like RTEXTIMAGE ignores those. Let me
know if I should play around more with your other files and methods.Yours,
Frank