Date: Fri, 26 Aug 2005 13:10:45 -0500
From: "Eric H. Neilsen, Jr."
Subject: Re: 2.5m obslog 20050825 (MJD 53608)
observer@devel1.apo.nmsu.edu wrote:
>This data was all correct for the engcam tracking in mount coordinates. Next, I
>lied to the TCC by pretending we were scanning a stripe, put in some offsets,
>and they showed up. NOTE THAT THE SCALE AND FOCUS DIDN'T SHOW UP until I did a
>"show scale and show foc in telrun". Here are the results, which look quite
>real. Note
>that GCTimer, ArcRaOff and ArcDecOff are still missing:
>
>
>
Asside from when the user issues commands to the TCC through the tccMon
command line, I do not think tccMon has *ever* prodded the TCC for
information; it just listenens in on what the TCC is saying. Unless
there is something else prodding the TCC for scale or focus information,
the TCC doesn't mention it, and tccMon doesn't know it. I believe that
this is how it has always worked.
>Murmur Log:
>----------
>Eric worked on the murmur log not murmuring MCP info. We'll have to wait for
>the DA phone con to see what he found out.
>
>
Actually, the murmur problem I worked on has nothing to do with the MCP.
I was working with Margaret to figure out why, if a single process sends
more than 40 or so lines to the murmur log at once, later results get
delayed. Margaret and I have been unable to reproduce this behavior on
the test stand at Fermilab (I dumped 5000 lines to the murmur log on
sdss3daq.fnal.gov at once, no problem), but I see it reliably on devel1.
If there is a problem with murmur getting MCP information, someone who
knows what the problem is should file a PR.
    -Eric