From: "Frinchaboy, Peter"
Date: Fri, 16 Dec 2011 16:47:16 -0600
Subject: Re: abbendum to: Re: [sdss3-25mlog 406] Re: [sdss3-plug 816] Re:
Viktor et al., the 10 min sky is now explicitly included in the time block
for the first plate of the night (though there is no explicit display for
in on the schedule page).
-- Peter
On 12/16/11 3:21 PM, "Viktor Malanushenko"  wrote:
>On Dec 16, 2011, at 2:17 PM, Viktor Malanushenko wrote:
>
>> About autoschedule:
>> Now the distance between the plates is exactly 85 minutes.
>> t's almost enough 65 min exposure + 20 min to adjust new plate.
>> But that is NOT enough to obtain sky dark...
>>=20
>> Could you please turn the sky dark time (4*150 sec + time to adjusting)
>>for the program autoschedule.
>
>It mean Sky Flat of course, sorry for mistake.
>
>
>Viktor Malanushenko
>viktorm@apo.nmsu.edu
>
>
>> Thanks in advance
>>=20
>> Viktor Malanushenko
>> viktorm@apo.nmsu.edu
>>=20
>>=20
>>=20
>> On Dec 16, 2011, at 2:12 PM, Fred Hearty wrote:
>>=20
>>> Thanks for looking into this, Mark. We'll be ready to discuss on
>>>Tuesday.
>>> Fred
>>>=20
>>> Mark Klaene wrote:
>>>>=20
>>>> Fred
>>>>=20
>>>> Dan, Kaike and I talked about this and after a lot of research by Dan
>>>> --We need a fair amount of discussion on this at the next tuesdays
>>>>ops telecon
>>=20
>>>>=20
>>>> APOGEE has some fundamental differences form the past 10 years of
>>>>SDSS that is causing this and not all of us were aware of the fallout
>>>>of these differences.
>>>>=20
>>>> here are some of the issues that need clarification and discussion
>>>>=20
>>>> 1. drill run nomenclature .  how does drill run number relate to
>>>>observing run ?
>>>>=20
>>>> 2. autoscheduler plan observing does not match the long used platedb
>>>>plan observing page
>>>> 3. platedb  is updated during the daytime (after plugging) but
>>>>Autoscheduler does not know this for that nights observing
>>>>=20
>>>> 4. pluggings do not match plugging request.  (this was never a
>>>>problem before but is now) because of item 3
>>>>=20
>>>> 5. Observers must go by actual pluggings not plugging request or
>>>>autoscheduler plan because they may differ. Thus there must be a step
>>>>to check platedb vs autoscheduler plan every afternoon.
>>>>=20
>>>>=20
>>>> Note the problem that occurred last night occurred twice this month
>>>>already but was caught. Last night it was not. So this is a serious
>>>>issue we must work through to everyones satisfaction. Right now there
>>>>is just too much manual and human interaction that is needed and
>>>>apparently no computer checks
>>>>=20
>>>>=20
>>>>=20
>>>> Mark
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> On Dec 16, 2011, at 8:23 AM, Fred Hearty wrote:
>>>>=20
>>>>> Hi Dan and Mark,
>>>>> The plates 5575/76 were part of the NOVEMBER drill run.
>>>>> Request that someone physically check that all co-observed plates
>>>>>from that run were properly marked.
>>>>> Also, the statement 'cart 1 plate 5568 (APOGEE+MARVELS) - we observe
>>>>>only APOGEE, 4*500 sec' from the night log also indicates that there
>>>>>was a SECOND missed co-observed plate, since this plate was supposed
>>>>>to be plugged for co-observing (and likely was), but the MARVELS
>>>>>integration was apparently not taken.
>>>>>=20
>>>>> Fred
>>>>>=20
>>>>>=20
>>>>> Dan Long wrote:
>>>>>> Hi Peter and Nathan,
>>>>>>=20
>>>>>>  There is a difference between what the autoscheduler is asking for
>>>>>>and what we were told was to be marked for MARVELS.  Plates 5575 and
>>>>>>5576 are both from the September drill run, which we were told not
>>>>>>to mark for MARVELS.  These plates are being requested to be plugged
>>>>>>for MARVELS by the autoscheduler.  Please advise if these plates
>>>>>>need to be marked and plugged for MARVELS or if the autoscheduler is
>>>>>>mistakenly choosing them to be plugged for MARVELS.
>>>>>>=20
>>>>>>              Cheers,
>>>>>>=20
>>>>>>                Dan
>>>>>>=20
>>>>>>>> (We have not received any signal for the MARVELS: PMT was less
>>>>>>>>than 6.)
>>>>>>>> After APOGEE exposure we disconnect cart 3 and have found that
>>>>>>>>many drilled
>>>>>>>> holes are not connected with fibers.
>>>>>>>=20
>>>>>>> Yesterday's APOGEE autoschedule requested for cart 3:
>>>>>>> 3 5275 --> 5576 X None Shared plate, please plug MARVELS fibers ||
>>>>>>>Please
>>>>>>> plug B plate fibers
>>>>>>>=20
>>>>>>> The platedb today shows that plate 5576 need A-side plugged. Same
>>>>>>>we have
>>>>>>> in the STUI platedb.
>>>>>>> We started observing the MARVELS with the plate at side A, then
>>>>>>>got zero
>>>>>>> signal, and tried to switch to side B on the fly for checking. Got
>>>>>>>the
>>>>>>> same zero signal, checked the plate visually after dismounting and
>>>>>>>found
>>>>>>> many unplugged holes.
>>>>>>>=20
>>>>>>> Dmitry & Viktor
>>>>>>>=20
>>>>>>>=20
>>>>>>> _______________________________________________
>>>>>>> Message 395 of sdss3-25mlog - Logs of nightly APO activities.
>>>>>>> sdss3-25mlog@sdss3.org
>>>>>>> https://sdss3.org/mailman/listinfo/sdss3-25mlog
>>>>>>=20
>>>>>> _______________________________________________
>>>>>> Message 397 of sdss3-25mlog - Logs of nightly APO activities.
>>>>>> sdss3-25mlog@sdss3.org
>>>>>> https://sdss3.org/mailman/listinfo/sdss3-25mlog
>>>>=20
>>>> Mark Klaene
>>>> Site Operations Manager Apache Point Observatory           voice: 575
>>>>437 6822
>>>> PO Box 59                                          fax:   575 434 5555
>>>> 2001 Apache Point Rd                     cell:  575 430 0210
>>>> Sunspot NM 88349-0059                web: www.apo.nmsu.edu
>>>>
>>>>=20
>>>>=20
>>>>=20
>>> _______________________________________________
>>> Message 816 of sdss3-plug - SDSS-III plate plugging activities.
>>> sdss3-plug@sdss3.org
>>> https://sdss3.org/mailman/listinfo/sdss3-plug
>>=20
>> _______________________________________________
>> Message 406 of sdss3-25mlog - Logs of nightly APO activities.
>> sdss3-25mlog@sdss3.org
>> https://sdss3.org/mailman/listinfo/sdss3-25mlog
>