Subject: Re: [sdss3-25mlog 1371] 2.5m obslog 20130903 (MJD 56539)
From: "John K. Parejko"
Date: Wed, 4 Sep 2013 10:05:08 -0400
Those messages just mean that the dust monitor isn't working, and thus =
apoActor isn't returning any values at all.
I'm reopening ticket #1843, considering it's the second time such a =
ticket was filed:
https://trac.sdss3.org/ticket/1843
apoActor should probably return "not responding" or something other =
value that better signifies that the given sensor isn't on.
John
On 4Sep 2013, at 08:26, dmbiz@apo.nmsu.edu wrote:
>=20
>                       APACHE POINT OBSERVATORY SDSS 2.5M
>=20
>                                 OBSERVING LOG
>                          Tuesday September 03, 2013
>=20
>                                  (MJD 56539)
...
> Attention to Jon Brinkmann:
> We got strange BOSS warnings that we don't know how to fix.
> Most probably something wrong is coming from "apo" actor.
>=20
> 09:58:15 APO.karen.sop 723 boss w text=3D"failed to index =
KeyVar('apo',
> dusta=3D(None,)) by None from dusta for DUSTA: KeyVar('apo', =
dusta=3D(None,)) is
> unknown"
> 09:58:15 APO.karen.sop 723 boss w text=3D"failed to index =
KeyVar('apo',
> dustb=3D(None,)) by None from dustb for DUSTB: KeyVar('apo', =
dustb=3D(None,)) is
> unknown"
--
*************************
John Parejko
john.parejko@yale.edu
http://www.astro.yale.edu/~jp727/
203 432-9759
JWG 465
Department of Physics
Yale University
New Haven, CT
**************************