Date: Thu, 20 Aug 2015 22:47:31 -0000 (UTC)
Subject: Re: [sloan-25mlog 2486] 2.5m obslog 20150819 (SJD 57254)
From: kpan@apo.nmsu.edu
Hi Dan and Patrick,
  I tried to identify the cause, but could not find any smoking gun.
The plots looks normal except for slightly bigger scatters, no obvious
outlier or systematic trends.
  The only thing off my head is that I do noticed that new fiducial tables
have bigger fitting errors then they had. For example, in the past, the
fitting errors for rot tables have typical errors of 3 ticks for
individual ID, and biggest one at about 10. In the new table (include
the one took a few days ago) has typical error of 15, the biggest one of
30.
The latitude table has 10 ticks  bigger fitting errors too. But not sure
how much worse pointing this could introduces.
  Let's try the normal MaNGA and eBOSS observations tonight, and check how
good/bad the pointings are. Please keep eyes on MaNGA plate guiding, and
notice in the log if guiding is consistently off more than 2.0". Thanks,
-kaike
>
>                        APACHE POINT OBSERVATORY SDSS 2.5M
>
>                                  OBSERVING LOG
>                           Wednesday August 19, 2015
>
>                                   (SJD 57254)
>
> ----  Observing Team ----
>
> Olena Malanushenko
> Dan Oravetz
> Kaike Pan (support)
>
> ---- Observing Summary ----
>
> A few passing clouds at times, seeing generally
> Obtained a 20-point pointing model during some intermittent clouds that
> had a
> resultant Sky RMS of 3". Then we moved on to the 155-point pointing model,
> but
> did not implement it because the Sky RMS was relatively large (>5"). We
> will
> wait further instructions from Kaike.
>
> Notes
> =====
> Roughly half a dozen times during the 155-point pointing model the Az
> and/or Alt
> axes went out of closed loop. Once this was due to a star in the DIMM
> avoidance
> region, but the cause of other events was not clear.
>
> Az fiducials 15 and 27 consistently reported large errors.
>
> When we tried to restart mcp via the MCP Menu (running from sdss-hub), it
> produced an error message (see Log body), but didn't actually execute the
> reset,
> so we went down to the lower enclosure and manually toggled the reset
> switch. We
> don't recall having this misbehavior when MCP Menu was running from
> sdsshost.
>
> ---- Observing Plan ----
>