Date: Sun, 05 Jun 2005 14:48:03 -0500 (CDT)
From: Brian_Yanny
Subject: Re: 2.5m obslog 20050604 (MJD 53526)
 	Thanks for trying to get this strip 290 N.
 	As Steve mentioned, it is unusual in its node and inclination,
 	being neither a SEGUE nor a regular Survey stripe,
 	and may give funny results in TCCMON and/or skippy.
 	In any case, however, should you get another opportunity to
 	scan this strip, please go ahead and do so, and 'trust'
 	the position information, and go ahead and continue the scan
 	(blindly if need be) so long as conditions are and photometric.
 	The purpose of this strip (and strips 205 and 291)
 	is to serve as a 'SEGUE cross scan', which crosses
 	the other SEGUE stripes and some regular SDSS stripes
 	in order to tie them together.
 	The exact position of the stripe is not hugely important
 	so long as it crosses the other scans.  Also, we
 	can recover the exact astrometry in full processing later.
thanks,
-brian
(for the SEGUE team)
On Sun, 5 Jun 2005, Stephen Kent wrote:
>> Stripe 290 N - something is going wrong with this stripe (or or perhaps
>> with
>> us ?). The telescope was commanded to go to mu=306, but instead it went to
>> mu=288. We ruled out bad pointing. Maybe some parameters for that stripe
>> are
>> wrong - could someone look at the problem please? (see the log for
>> details).
>
> Argh, stripe 290 is one of the Segue "special stripes" which will not
> show up properly in tccmon.  The reason is that it has a special node and
> inclination.  All normal Segue stripes are scans of constant galactic
> longitude, and tccmon assumes that that is the case.  I should have marked
> the observing plan.  The special stripes are 205, 290, and 291.
> It is also possible that skippy will not work with them either.
>
> I also erred in my last email asking for repeat data on stripe 17.
> I would like to repeat 17 N from -2 to 18, if photometric and seeing is
> definitively good.  (No need to do it if seeing is marginal).
>
> Nice to fill some holes!  I seem to recall that there are times when slewing
> the telescope cause NaN's to be put out by the TCC for
> some fields that goDrift will be trying to read.
>
> R.E. pushing twilight, it seems we can tolerate about 5 minutes outside
> the tilight limits before the sky level (u band) rises noticeably.
> I would not worry too much about this effect when filling the holes, because
> data processing should still be able to handle it, and only the u
> band is affected.
>
> 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 2475 in the sdss-25mlog archive, URL
> DSS         http://www.astro.princeton.edu:81/sdss-25mlog/msg.2475.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
>