iraf.net

Hi guys, It looks like OBSINIT was not run, or at least not successfully, from
the 4meter account on khaki at the start of the TI2 run on Oct. 8, since the
following files are there from the previous run. 4meter@khaki% ls -l `find . -mtime 3 -print`
-rw-r--r-- 1 4meter 939 Oct 5 14:05 ./.login
-rw-r--r-- 1 4meter 938 Oct 5 13:47 ./.login~
-rw-r--r-- 1 4meter 2007 Oct 5 20:21 ./reduce/login.cl
-rw-r--r-- 1 4meter 811 Oct 5 20:33 ./reduce/loginuser.cl~(I don't know where these file~ files come from; perhaps they are saved
by some window based editor?) In ~4meter/uparm/ccqdetpas.par (where the system saves the user's current
settings of DETPARS), detname currently = te2k. SOMEONE SHOULD EDIT THIS
BEFORE TONIGHT'S RUN (by running "detpars" or "epar detpars"). Since we
don't know what happened yet, it would be a good idea to examine obspars
and telpars as well. When really in doubt, you can always "unlearn detpars",
then "epar detpars" to reset everything from their initial defaults, the
same as would have been done at the start of the run, just after OBSINIT. Of the 23 image headers in ~4meter/night1, all but the last shows
detector=ti2; n10032.imh has detector=te2k. So clearly, even if obsinit
had not been run, DETPARS at least had to have been edited to set detname=ti2.
Is it possible someone inadvertently reset detpars.detname=te2k early this
morning (sometime between 3:33 and 5:15, according to the .imh file dates)? I would still like to know exactly what the observer did to run a second
observe before the previous one finished reading out. It is possible there
is some obscure bug, but I can't think of anything that could explain ICE
changing detname from ti2 to te2k other than the user doing so; there are
no other parameter files in uparm where detname could have been saved from
the previous run, whether or not obsinit had been executed.
Steve