Subject: Re: [sdss3-25mlog 924] Re: 2.5m obslog 20121112 (MJD 56244)
From: Kaike Pan
Date: Tue, 13 Nov 2012 16:58:58 -0700
Hi Jim,
  Sorry. I was trying to say ~ 3 sec delay. Playing safe, waiting 5 sec =
should be enough.
On Nov 13, 2012, at 12:41 PM, jegunn wrote:
> If it is a timed `safety' issue, 30 seconds is FAR too long, and I =
think is far from `safe'. When the cold observer releases an E-stop and =
relays
> that information, he/she knows the telescope is going to move. If the
> telescope has to wait half a minute before moving, there is ample =
opportunity for a cold and tired observer to get herself in a dangerous
> situation again. So IMHO this needs fixing, even if one ignores the =
non-negligible hit in efficiency.
>=20
> --jim
>=20
> On Tue, 13 Nov 2012, Kaike Pan wrote:
>=20
>> I noticed that the "gotoField" command would fail if it is issued too =
soon after a E-stop
>> is released. So I  consider it as a feature. But John P. can weight =
on it if he can fix it
>> as a bug.
>>=20
>> The first command in "gotoField" is "axis init", then check to see if =
all axes are ready
>> for a telescope slew. If, not, the whole "gotoField" sequence will =
fail immediately.  Just for
>> your information, in the past, we do "axis init" as a separate =
command, then "gotoField".
>> Occasionally, "gotoField" would fail if it is issue too soon.
>>=20
>> -kaike
>>=20
>> On Nov 13, 2012, at 6:59 AM, Joe Huehnerhoff wrote:
>>=20
>>> Is this feature an implemented safety or is it a bug?
>>>=20
>>> Joe
>>>=20
>>> On Nov 13, 2012, at 6:56 AM, Kaike Pan wrote:
>>>=20
>>>>=20
>>>> On Nov 13, 2012, at 5:54 AM, hjbrew@apo.nmsu.edu wrote:
>>>>=20
>>>>>=20
>>>>>                    APACHE POINT OBSERVATORY SDSS 2.5M
>>>>>=20
>>>>>                              OBSERVING LOG
>>>>>                       Monday November 12, 2012
>>>>>=20
>>>>>                               (MJD 56244)
>>>>>=20
>>>>> ----  Observing Team ----
>>>>>=20
>>>>> Karen Kinemuchi
>>>>> Howard Brewington
>>>>>=20
>>>>> ---- Observing Plan ----
>>>>>=20
>>>>> 12 Nov 2012  56244.0  0.05  01:14 12:22  21:41 08:51  BOSS  11.1 =
hours
>>>>>=20
>>>>> ---- Observing Summary ----
>>>>>=20
>>>>> Clouds and poor seeing for most of the night.
>>>>>=20
>>>>> Observed:
>>>>> ---------
>>>>> Cart 10, 5033, BOSS, DONE
>>>>> Cart 11, 6134, BOSS, DONE
>>>>> Cart 13, 6187, BOSS, DONE
>>>>> Cart 14, 5700, BOSS, not done
>>>>> Cart 15, 6268, BOSS, not done
>>>>> Cart 17, 5177, BOSS, not done
>>>>> Cart 16, 6390, BOSS, DONE
>>>>> Cart 18, 5767, BOSS, not done
>>>>>=20
>>>>> 10:23Z started APOGEE cala
>>>>> 12:40Z started BOSS dark/bias exposures
>>>>>=20
>>>>> Notes for engCrew, swingShift, and developers
>>>>> ---------------------------------
>>>>>=20
>>>>> M1, Lateral F:	12.2809	12.2428 is on the edge of tolerance.  =
May need to
>>>>> home/relax. We also noticed, after we closed, that we have red =
values for M2 in
>>>>> the TPM.
>>>>>=20
>>>>>=20
>>>>> goToField failed on the first try for most of the night, e.g., =
Carts 11, 13, 14,
>>>>> 15, 16, and 18.
>>>>>=20
>>>>=20
>>>> There is a time delay. Please wait ~30 sec after E-stop buttons are =
pulled out before issue
>>>> "gotoField".
>>>>=20
>>>> _____________________________________________________
>>>> Message 922 of sdss3-25mlog - Logs of nightly APO activities.
>>>> =
https://trac.sdss3.org/tracmailman/browser/private/sdss3-25mlog/all/922.ht=
ml
>>>> sdss3-25mlog@sdss3.org
>>>> https://sdss3.org/mailman/listinfo/sdss3-25mlog
>>>=20
>>=20
>> _____________________________________________________
>> Message 924 of sdss3-25mlog - Logs of nightly APO activities.
>> =
https://trac.sdss3.org/tracmailman/browser/private/sdss3-25mlog/all/924.ht=
ml
>> sdss3-25mlog@sdss3.org
>> https://sdss3.org/mailman/listinfo/sdss3-25mlog
>>=20