From: Kaike Pan
Subject: Re: 2.5m obslog 20051029 (MJD 53673)
Date: Sun, 30 Oct 2005 19:58:27 -0700
Hi, Steve,
     I looked at headers for other three frames. All of them have
wrong stripe
number 22 instead of 20. I do not know where frame headers get the
stripe
number information. Are they from observer's input
for command goDrift?  If this is the case, it could be due to my typo
(I am not
sure now what I have typed in, 20 or 22).  I am sorry if this is due
to my typo
and caused some extra work for others.
   If frame headers do use stripe number typed in by observers, I
just wonder
if it is possible for IOP to get stripe number information for
telescope's position
instead from observer's typing.  Of course, we will do our best to
type into correct
numbers. But understandably, observers might make typos, especially
in mornings
after hours working.  So, I feel that it would be nice if IOP can get
stripe number from
telescope position. Because we know where we want to telescope to be.
So,
we can always check it after we slew the telescope with "scanStripe"
command.
  Cheers,
    Kaike
On Oct 30, 2005, at 1:59 PM, Stephen Kent wrote:
>> LEGACY
>> 09:40Z run 5794, Legacy 20, N:
>>       Good since the beginning. The ramp starts at frame 11,
>> lambda -66,
>>       science from frame 24, lambda -64. Skippy is NOT running. It
>> runs
>>       occasionaly on some frames (from astrom), but only if we ask
>> it to run
>>       on a single frame. On other frames or if asked to run on
>> more than one
>>       frames it gives an error (see the problem section).
>>       Fits file headers looks ok to us both, those on which skippy
>> runs and
>>       those it does not. Maybe we are missing something?
>>       Also skippy finds anly a few catalog stars for that stripe
>> and then
>>       1 or 2 stars to compare with. So we don't beleve it's results.
>>       Since we did not have the pointing problems tonight, we
>> decided to
>>       continue "blindly". Please could someone look at the data
>> and tell us
>>       what is going on?
>>       End of the science on frame 124, lambda -49, ramp ends on
>> frame 137,
>>       lambda -47.
>>
>
> I looked at the r band frame 100, camcol 1.  The point looks OK
> when I came the field with SkyView.  However, the idReport file and
> the frame header both say that this is stripe 22, which is wrong -
> it is stripe 20. Why would this happen?
>
> Let's assume that the data are GOOD.  The idReport file and the
> frame headers will need fixing.
>
> Steve
>
> DSS DSS DSS DSS DSS  Digital Sky Survey DSS DSS DSS DSS DSS DSS
> DSS *** The information posted to SDSS mailing lists is proprietary
> ***
> DSS  This is message 2666 in the sdss-25mlog archive, URL
> DSS         http://www.astro.princeton.edu:81/sdss-25mlog/msg.
> 2666.html
> DSS  The index is at http://www.astro.princeton.edu:81/sdss-25mlog/
> INDEX.html
> DSS  To join/leave the list, go to
> DSS         http://www.astro.princeton.edu:81/cgi-bin/
> mailinglists.pl/show_subscription?list=sdss-25mlog
> DSS  To post a message, mail it to sdss-25mlog@astro.princeton.edu
> DSS
> DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS DSS
>