Re: Disk 18e weirdness

[Tom Droege <tdroege@veriomail.com>]

Paul and all,

It looks like 18e got damaged somewhere in the copying process.  The files 
look OK on my hard disk.  So I can make more copies.

Can anyone read their copy of disk 18e?

If so, you can trade it around.  Otherwise I can send out a few more 
copies.  Sigh!  I am tired of copying disks.

OK, what I did was take the master sets of disks from the various runs and 
edit them onto my hard drive.  Usually there was 2 to 4 disks for the 
evening, I edited out 1 full disk from the set.  I then made a set of 
copies from the hard drive.  This set went into the next room where the 
fast machine was and were duplicated.  For the most part you can tell the 
earlier copies from the later copies since the earlier copies are plain 
disks while the later ones used disks that are labeled "Delta"

I did not always use the same disk for a master.  So it is possible that 
there are good sets and bad sets out there.  I used "xcdroast" on hte Linux 
machine in the "copy on the fly" mode.  Possibly some of you know of a 
problem with this.  I did have one problem where the machine died, and a 
bad disk was made.

I did spot check a few of the disks to the point of testing that I could 
read a few random images but I did not do a read after write verify.

Tom Droege

At 10:40 PM 6/5/01 +1200, you wrote:
Hi Tom,

I have managed to process 18b,g,h,i with the pipeline to
star lists.

But I've got a problem with 18e.

I'm checking this with you first, as it doesnt look like a cd problem as
all of the images are strange in the same way. More a software problem
with the fits headers.

I've attached the fits headers from two (of the many) images.
(the only editing I've done to the headers is a couple of line feeds in
the nasa comments as the editor ate the spaces to the end of the line
for some reason...)

The interesting stuff starts at the IMAGETYP line, as it
doesnt seem padded to 80 characters.

IMAGETYP= 'dark    '           / dark frame     RTMP= '8.921381'

The next bit of weirdness is in the CCDTEMP field which has spurious
data.

CCDTEMP = '-23.5^@^@^H^@^@^@^H^@4932'

There a lot of images like these and they all have the same problem!
Also (as far as I have looked) only one of the I & V image pairs seems
to be corrupt.

hira2017732.fits OK  hvra2017732.fits BAD
hira2017788.fits BAD hvra2017788.fits OK
hira2017730.fits OK  hvra2017730.fits BAD
hira2017721.fits OK  hvra2017721.fits BAD
hira2017717.fits BAD hvra2017717.fits OK etc... you get the idea ;-)

I havent checked disks d or f as of yet to see if its just disk 18e.

regards Paul