From: stephanie snedden Subject: Re: 2.5m obslog 20090129 (MJD 54861) Date: Fri, 30 Jan 2009 12:05:41 -0700 Actually, I think we did have this problem in the fall as well, now that my memory has awakened. The workaround is pretty easy, so I'm not too concerned about the problem. However, there is a new TCC coming soon, according to Russell. I don't believe the new TCC will have any changes that affect this "feature", but Russell can correct me if I'm wrong. Steph On Jan 30, 2009, at 11:53 AM, David Schlegel wrote: > Connie et al, > > Note that we did non-survey scans in the Fall (cross-scans, flat-field > scans) without trouble. So this must have been a recent change. > I would suggest rolling it back. If indeed we continue imaging this > coming Fall, it is likely we would want another flat-field scan. > > -David > > > On Jan 30, 2009, at 10:40 AM, Constance Rockosi wrote: > >> >> The error message that Howard and Kaike got was not very informative, >> something about the variable "stripe" not being set. >> >> The real problem is that goDrift (for a non-bias scan) now checks >> with >> the TCC that the stripe name given to goDrift is the same as the one >> that the TCC thinks it is scanning (as issued by scanStripe, the >> normal way for the observers to send the telescope scanning). This >> is >> a well-intentioned attempt to keep all the information about an >> imaging >> scan in sync so that astrom can reduce it, etc., skippy can give >> pointing checks, etc. Remember the terrible trouble we've had when >> the boresight offset was not what we thought it was. >> >> However, that check makes it impossible to do a scan that is not >> along >> a "known" stripe, to which you send the telescope scanning with >> "scanStripe". It might be enough to specify the stripe name in the >> track command, but I haven't checked. >> >> The kludge of issuing the goDrift from an iop without a TCC window >> was >> just lucky -- I was going to ask Howard to issue the goDrift yet once >> more and then read to me the stack trace from the errorInfo variable, >> but I realized I could just issue the command myself and save the >> telephone recitation. And lo and behold, it worked after I told my >> iop to go ahead and finish the goDrift even though it didn't have a >> TCC connection to confirm the stripe name. >> >> Someone should check whether the TCCgoDrift check can be satisfied >> by giving the stripe name in the track command. Then we can decide >> how to modify non-standard-scanning procedures in the future. We >> don't >> think we'll want any more, but it would be good to know how to do >> this with less drama. >> >> --Connie >> >> >> On Fri, Jan 30, 2009 at 10:13:50AM -0700, stephanie snedden wrote: >>>> >>> What was the error that you got when the goDrift failed, and what >>> did >>> Connie do differently? We need to correct the procedure. >>> >>> Steph >>> >>>> Segue cluster Stripe run 7942 >>>> 05:49Z drift started frame 13 >>>> We tried to start goDrift, with no success. We called >>>> Connie, and >>>> she started goDrift remotely from an iop sessio nwithout a tcc >>>> connection. We didn't stop the drift, instead just slewed >>>> back to the >>>> beginning of the field. >>>> 05:52Z focus loop running and going back to track frame 18 >>>> 05:53Z frame 21 is good seeing is 1.1" >>>> 06:01Z cluster seen frame 32, dewar 3 >>>> 06:32Z watcher complained about vs voltage of ccd 55 >>>> 06:35Z cluster 2 found at frame 90, dewar 3 >>>> 06:59Z stopping drift frame 130 >>>> 07:01Z on-telescope bias T bars unlatched run 7943 >>> >>> 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 4450 in the sdss-25mlog archive, URL >>> DSS http://www.astro.princeton.edu:81/sdss-25mlog/msg.4450.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 >>> >>> !DSPAM:10028,4983357719393072027612! >>> >> >> 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 4451 in the sdss-25mlog archive, URL >> DSS http://www.astro.princeton.edu:81/sdss-25mlog/msg.4451.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 >