Subject: Re: [sloan-25mlog 6671] 2.5m obslog 20230406 (SJD 60041)
From: Kaike
Date: Fri, 7 Apr 2023 08:35:37 -0600
> On Apr 7, 2023, at 5:10 AM, dmbiz@apo.nmsu.edu wrote:
>=20
>=20
>                       APACHE POINT OBSERVATORY SDSS 2.5M
>=20
>                                 OBSERVING LOG
>                          Thursday April 06, 2023
>=20
>                                  (SJD 60041)
>=20
> ----  Observing Team ----
>=20
> Dmitry Bizyaev
>=20
>=20
> ---- Observing Plan ----
>=20
> Thu 06 Apr 2023 60041 0.99 02:21 02:36 11:34 08:33 17:33 --- bright ( =
9.2 h, w/ 0.2 h for 12 deg design)
>=20
>=20
> ---- Observing Summary ----
>=20
> Clear and dusty night with terrible seeing. =20
>=20
> Notes
> -----
> - dust accumulated: 40.2K. Please clean optics, if you can.=20
>=20
> - I was unable to improve transparency of MTP6 by moving gang =
connector back and fore
>  and blowing it. Sorry, MTP6 stays low for tonight.=20
>=20
> - A collision was detected in positioner 809, with two attempts for =
field-design 100346-113778.
>  Ii skipped the design.=20
>=20
> - at 8:34 collision was reported for robot 1246. I spent an hour for =
disentangling 1246 and=20
>  its neighbors. No success: apparently, beta-arm of 1246 got stuck or =
broken. I can move
>  all other robots with --go-cowboy flag, but not this beta-arm. The =
problem is aggravated
>  by inability to run "jaeger unwind --force" command - it fails. As a =
result, I have
>  to leave the FPS UNFOLDED! I've sent an email to Jose - hopefully he =
can read
>  the message in the morning in the place where he is now.=20
Sometime, power off/on fps helps. My first =E2=80=9Cjaeger unwind=E2=80=9D=
 reported a collision on 1246, following up =E2=80=9Cjaeger unlock=E2=80=9D=
, =E2=80=9Cjaeger explode 5=E2=80=9D, and =E2=80=9Cjaeger unwind=E2=80=9D =
sent all robots homes successfully.