Subject: Re: [sdss3-25mlog 1317] 2.5m obslog 20130708 (MJD 56482)
From: Elena Malanushenko
Date: Mon, 15 Jul 2013 12:16:07 -0600
Dear Observers,=20
I want to comment fantom hartman problem.=20
I am still working with problem.=20
As I know it does not affect observations.=20
The previous hartman values were printed on time.=20
But the same last values were printed=20
one more time after stui was disconnected two hours later.=20
No hartman was commanded and so no any move.=20
I want to note, that the next lines in logFun
do not indicate any move and you do not need to=20
worry to check real collimator positions: =20
> 11:38:21  hartSp2: r=3D-701, b=3D-2.4, txt=3DOK, sp2Temp =3D 11.8
> 11:38:21  sos.sp1AverageMove =3D -1401
This is echo from idl procedure to calculate=20
collimate adjustments if it will be requested.=20
The real move indicator is output likes
03:01:28  sp1.motor.move=3D -691, -689, -695,=20
I track of the motor positions, watching for the change of=20
these positions, calculate the difference between old and new sets,=20
and print echo in logFun window.=20
Regards, Elena
On 07 /10/ 13, at 4:57 AM, kinemuchi@apo.nmsu.edu wrote:
>=20
>                       APACHE POINT OBSERVATORY SDSS 2.5M
>=20
>                                 OBSERVING LOG
>                          Tuesday July 09, 2013
>=20
>                                  (MJD 56483)
>=20
>=20
>=20
> Garrett received more phantom hartmann moves after logging into STUI. =
See
> problems in detail.
On 07 /09/ 13, at 5:54 AM, kinemuchi@apo.nmsu.edu wrote:
>                       APACHE POINT OBSERVATORY SDSS 2.5M
>=20
>                                 OBSERVING LOG
>                          Monday July 08, 2013
>=20
>                                  (MJD 56482)
>=20
>=20
> 11:38Z  As Garrett logged out of STUI on landru, a phantom hartmann =
appeared on
> his logFun window (see below).  We confirmed that the positions did =
not change
> for the SP cameras.  I did not see the hartmann commands on my logFun =
window
> running on minidru.  Perhaps some sort of software hiccup?
>=20
> 11:27:09  loadCart: ct=3D18, pl=3D6514,  sd=3DA;
> 11:29:00  encl25m : closed;
> 11:30:58  sp2.motor.move=3D 0, -1, 0
> 11:31:06  boss exposure    0.0, file=3D164429
> 11:32:08  boss Idle
> 11:32:33  boss exposure    0.0, file=3D164430
> 11:33:34  boss Idle
> 11:33:54  boss exposure    0.0, file=3D164431
> 11:34:56  boss Idle
> 11:35:16  boss exposure    0.0, file=3D164432
> 11:36:20  boss Idle
> 11:36:41  boss exposure    0.0, file=3D164433
> 11:37:20  apogee.expose=3DapRaw-09200019, 60, A, Dark
> 11:37:42  boss Idle
> 11:38:02  boss exposure    0.0, file=3D164434
> 11:38:21  sos.sp1AverageMove =3D -1401
> 11:38:21  hartSp2: r=3D-701, b=3D-2.4, txt=3DOK, sp2Temp =3D 11.8
> 11:38:21  hartSp1: r=3D761, b=3D2.6, txt=3DOK, sp1Temp =3D 12.5
> 11:38:21  sos.sp2AverageMove =3D 618