Subject: Re: [sloan-25mlog 2689] 2.5m obslog 20151112 (SJD 57339)
From: "John K. Parejko"
Date: Fri, 13 Nov 2015 09:39:32 -0800
There is a ticket on this topic:
https://trac.sdss.org/ticket/2400
Maybe we can look at it during the hackweek next week.
John
On 13Nov 2015, at 07:00, Dan Long  wrote:
> Hi Dan & Katie,
>=20
>   Yes, the rotator hit the positive limit.  The slew put the rotator =
at 253 degrees and the track then moved it in the positive direction.  =
After tracking for just short of three hours the rotator hit the =
positive limit of 360 degrees.
>=20
>   If you see an axis approaching a limit, it would be best to re-slew =
between exposures and reacquire.  The tcc command show block axelim will =
return the limits in the tcc.
>=20
> 14:41:45 CmdStarted: APO.long 2 tcc show block axelim
> 14:41:45 APO.long 2 tcc i Text=3D"# AxeLim data"
> 14:41:45 APO.long 2 tcc i Text=3D"# Minimum position of Az, Alt, Rot =
(deg)"
> 14:41:45 APO.long 2 tcc i Text=3D"minPos -195.0 18.2 -180.0"
> 14:41:45 APO.long 2 tcc i Text=3D"# Maximum position of Az, Alt, Rot =
(deg)"
> 14:41:45 APO.long 2 tcc i Text=3D"maxPos 435.0 90.0 360.0"
>=20
>   A more involved (and better) solution would be to have the slewing =
software determine the longest track for all possible wraps and choose =
that one.  In last night=92s example if rotwrap negative had been chosen =
for the track command, the rotator would have started at -107 and never =
reached a limit.
>=20
> 		Cheers,
>=20
> 		   Dan
>=20
>=20
> On Nov 13, 2015, at 6:31 AM, doravetz@apo.nmsu.edu wrote:
>=20
>>=20
>>                      APACHE POINT OBSERVATORY SDSS 2.5M
>>=20
>>                                OBSERVING LOG
>>                         Thursday November 12, 2015
>>=20
>>                                 (SJD 57339)
>>=20
>> ----  Observing Team ----
>>=20
>> Katie Grabowski
>> Dan Oravetz
>>=20
>> ---- Observing Summary ----
>>=20
>> Mostly clear; variable seeing at the beginning of the night =
stabilized for the
>> last few hours. Observed:
>>=20
>> eBOSS
>> =3D=3D=3D=3D=3D
>> Cart. 14, 7666 - 6X900s; DONE
>> Cart. 10, 7672 - 4X900s; DONE
>> Cart. 17, 7894 - 5X900s; DONE
>> Cart. 15, 8789 - 5X900s
>>=20
>> MaNGA
>> =3D=3D=3D=3D=3D
>> Cart. 4, 8728 [MaNGA-led co-obs]; DONE
>>     1XNSE + 3XAB (APOGEE-2 piggy-backing)
>>     Missing fibers: [20, 39, 48, 151, 278]
>>     Faint fibers: [197, 211, 242, 248, 277, 280, 284]
>>=20
>> Cart. 3, 8713 [MaNGA-led co-obs]; DONE
>>      4XNSE + 13XAB (APOGEE-2 piggy-backing)
>>      Missing fibers: []
>>      Faint: [133, 173, 197, 211, 217, 247, 248, 249, 250, 258, 277, =
278, 290]
>>=20
>> Notes
>> =3D=3D=3D=3D=3D
>> (1) SoS did not provide S/N feedback for plate 8789 (0.0's across the =
board),
>> but we likely did not complete it given its 2X SN2 depth requirement.
>>=20
>> (2) At 08:38Z, azimuth, followed shortly thereafter by altitude, went =
out of
>> closed-loop during the gotoField slew. No time lost.
>>=20
>> (3) We lost 27 minutes of MaNGA time because the rotator hit an =
apparent limit
>> during tracking on cart. 3, 8713. See Problems section for details.
>>=20
>=20
>=20
>=20
> ____________________________________________________________
> Logs of Nightly APO Activities
> =
https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/index.html
--
*************************
John Parejko
parejkoj@uw.edu
http://www.astro.yale.edu/~jp727/
Department of Physics and Astronomy
University of Washington
Seattle, WA
**************************