Subject: Re: [sloan-25mlog 3518] 2.5m obslog 20170522 (SJD 57896)
From: Kaike Pan
Date: Tue, 23 May 2017 07:47:35 -0600
> On May 23, 2017, at 5:38 AM, asimmons@apo.nmsu.edu wrote:
>=20
>=20
>                       APACHE POINT OBSERVATORY SDSS 2.5M
>=20
>                                 OBSERVING LOG
>                          Monday May 22, 2017
>=20
>                                  (SJD 57896)
>=20
> ----  Observing Team ----
>=20
> Elena Malanushenko
> Audrey Oravetz
>=20
> ---- Observing Summary ----
>=20
> Clear night.
>=20
> Cart 6, M&Ap plate 9876, 042+87; 1XAB (twi) + 3XNSE + 9XAB - DONE
> Missing fibers: [181, 277]
> Faint fibers:   [15, 34, 105, 289, 294]
> -----------------
>=20
> Cart 4, M&Ap plate 9185, 057+35; 1XNSE + 3XAB - DONE
> Missing fibers: [20, 39, 151, 241, 277, 278]
> Faint fibers:   [284]
> -----------------
>=20
> Cart 14, plate 8413; 4x900 - not done
> Cart 17, plate 8528; 2x900 - DONE
> Cart 15, plate 8527; 4x900 - not done
>=20
> Cart 1, Ap&M plate 9117, 034-06 - 1XAB + 1XC - not done
> Missing fibers: [277]
> Faint fibers:   [10, 227]
> -----------------
>=20
> Notes:
> =3D=3D=3D=3D=3D=3D
>=20
> - We had one instance of gotoField failing due to the delay in axis =
status. See
> problem section for STUI cut-out.=20
>=20
For the record, this is our normall =E2=80=9CgotoField=E2=80=9D failure =
due to the SOP check tcc axis readiness status too soon.=20
As I mentioned in another email, we typically have this type of failure =
once per night or so.=20
This failure differ from ones we saw several nights ago. That was due to =
SET.TIME timed out. =20
Based on well behavior of MCP in last three nights, we am glad to report =
that MCP is back to normal after its reboot on
5/20. Will send another email to infrastructure mailing on my =
understanding on the issue later.=20=