Subject: Re: [sloan-25mlog 3093] Re: 2.5m obslog 20160909 (SJD 57641)
From: Conor Sayres
Date: Sat, 10 Sep 2016 11:30:26 -0700
When relaxing the M1, I would not be surprised about weird output in the =
mirror status window (timers counting down negatively).
The relaxing routine bypasses the mirror controller, and anytime you do =
this and command moves, the mirror controller/STUI will show confusing =
output for move timers/durations.  I=92ve actually never relaxed the M1 =
and I don=92t know exactly what the script does.  If it=92s an issue we =
could look at building the RELAX into the mirror controller and I think =
the output could look more sane.
I would recommend typing in STUI =93tcc mir status=94, to refresh the =
STUI display if you are seeing confusing output (timers counting down =
forever?) when commanding direct XQ# commands to the galil.
As I noted in an earlier reply, desired orientations for the M1 will not =
equal the =93measured/commanded=94 orientation of the M1 because =
commanded values rounded to the nearest 50.
Would you like me to commit the current state of the tccdata repo?
Conor
=20
On Sep 10, 2016, at 10:07 AM, Kaike Pan  wrote:
> Conor, This may be ok, but I think it=92s worthy to let everyone know.=20=
>=20
> normally, M1 status (in tcc mirror status window) will be =93DONE=94 =
without
> anything when home/relax id completed. And this is the case before
> we updated the default.dat file (all zeros), and PrimOrient and =
PrimDesOrient
> are the same.  However, after  we updated default.dat with tilt found =
in
> optical collimation and reload the instrument block, we run M1 relax
> again, we first noticed that PrimOrient have all numbers in updated
> default.dat file but PrimOrient in x-tilt, y-tilt, X_trans, and =
Y_trans are slightly
> different from their corresponds in PrimDesOrient, the biggest =
different in trans
> is about 1 um, and 0.5=94 in tilt. Moreover, we noticed that M1 status=20=
> is =93DONE=94 with a time count continuously counting toward a more =
negative=20
> numbers after HOME/RELAX is completed, The counter will not stop until=20=
> the next action on the telescope (such as slew etc) is triggered. This =
may be
> fine, but just want to let you know. The continuous running time =
counter
> may indicate something is not in its expected status?
>=20
>=20
> FYI: Optical Collimation is done and instrument block is updated.=20
>=20
> -kaike
>=20
>> On Sep 10, 2016, at 5:15 AM, gfreischlad@apo.nmsu.edu wrote:
>>=20
>>=20
>>                      APACHE POINT OBSERVATORY SDSS 2.5M
>>=20
>>                                OBSERVING LOG
>>                         Friday September 09, 2016
>>=20
>>                                 (SJD 57641)
>>=20
>> ----  Observing Team ----
>>=20
>> Dmitry Bizyaev
>> Gordon Freischlad
>>=20
>> Kaike Pan
>>=20
>> ---- Observing Summary ----
>>=20
>> We declared new MIG numbers, completed the optical collimation and =
instrument
>> block update just in time
>> for the wind gusts and humidity to spike. Weather permitting, the =
pointing model
>> will happen tomorrow.
>>=20
>> Seeing ~0.9 - 1.3"/
>>=20
>> Notes:
>> Conor and others, the telescope would not move exactly to the new =
home position
>> once we updated it to the new default location (in the sense that we =
observe
>> small difference between Prim des and Prim orient values). It was =
close, but
>> since the
>> mirrors had no problem moving to exactly 0,0,0,0,0 (Prim des =3D Prim =
orient) it
>> seems worth noting. Also, while we were trying to debug this we
>> commanded some small **x- and y-tilt** moves near the
>> new default which caused the **Piston** to move about 1um despite no =
piston move
>> command being given.=20
>>=20
>>=20
>> ---- Observing Plan ----
>=20
> ____________________________________________________________
> Logs of Nightly APO Activities
> =
https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/index.html