Date: Sat, 21 Aug 2010 16:28:21 -0400
Subject: Re: 2.5m obslog 20100820 (MJD 55429)
From: David Kirkby
--0016e64c1aa4a885b8048e5b411c
Content-Type: text/plain; charset=ISO-8859-1
Hi Elena - please file a ticket against STUI for your request below. I am a
little concerned that the keyword log is so central to following "current
events and details of the telescope operation". Don't the STUI windows
already do this adequately? Is there particular status info missing from
them that forces you to rely on the log window?
David
> To developers:
> We request that the debugging output displayed in the STUI log be removed
> so
> that we better see the current events and details of the telescope
> operation.
> It is currently difficult to identify necessary telescope functions because
> of
> the clutter. It uploads log until log's limit very quickly and we cannot
> monitor important operational information even for duration of one exposure.
> The example of one block of debug output is in problem section, reported as
> an operational problem. This boss monitoring block is ~75 lines and repeat
> every 2 minutes. All information from that block is saving in archiver.
--0016e64c1aa4a885b8048e5b411c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Hi Elena - please file a ticket against STU=
I for your request below. I am a little concerned that the keyword log is s=
o central to following "current events and details of the telescope op=
eration". Don't the STUI windows already do this adequately? Is th=
ere particular status info missing from them that forces you to rely on the=
 log window?
David=A0To developers:
We request that the debugging output displayed in the STUI log be removed s=
o
that we better see the current events and details of the telescope operatio=
n.
It is currently difficult to identify necessary telescope functions because=
 of
the clutter. It uploads log until log's limit very quickly and we canno=
t monitor important operational information even for duration of one exposu=
re.
The example of one block of debug output is in problem section, reported as=
an operational problem. This boss monitoring block is ~75 lines and repeat
every 2 minutes. All information from that block is saving in archiver.
--0016e64c1aa4a885b8048e5b411c--