Subject: Re: 2.5m obslog 000329 (MJD 51633) (WRONG num of pix)
Date: Tue, 04 Apr 2000 17:29:51 -0500
From: Ronald Rechenmacher
Hi,
I now know that the "WRONG num of pix" message for ccd 0 was
"throttled."  This means that the problem could be with either
the camera, data sender, or VCI+.  I have changed the "throttling"
code to indicate the potential for the next message to be throttled.
--Ron
ron@fnapcf.fnal.gov said:
> The one occurrence on Mar 14 was associated with a complete line. It
> was the line before it that had that had missing pixels on 4 of the 5
> ccds: Mar 14 20:16:28 sdssid2    dLine      dsc_E_trcErr WRONG num of
> pix?? for (sr   dLine      dsc_E_trcErr WRONG num of pix?? 667 should be 2128  Mar
> 14 20:16:28 sdssid2    dLine      dsc_E_trcErr WRONG num of pix?? for
> (sr    dsc_E_trcErr WRONG num of pix?? 668 should be 2128  Mar 14 20:16:28
> sdssid2    dLine      dsc_E_trcErr WRONG num of pix?? for
> (sr    dsc_E_trcErr WRONG num of pix?? 668 should be 2128  Mar 14 20:16:28
> sdssid2    dLine      dsc_E_trcErr WRONG num of pix?? for
> (sr    dsc_E_trcErr WRONG num of pix?? 668 should be 2128  Mar 14 20:16:28
> sdssid2    dLine      dsc_E_trcErr vci fiber protocol fail This is
> very significant! I don't know how this could happen! By process of
> eliminating the least likely candidates, the most likely candidate is
> the VCI+ card, but this is truly baffling! The rest in March were of
> the missing one pixel on one ccd variety; occurring twice on ccd 0 and
> once on ccd 3.