[evlatests] All EVLA antennas

[Bryan Butler]

yes, we talked about getting realistic severity levels in for the VLA/CMP alerts 
this morning.  the engineers (organized by steve) will do it just as they have 
for the EVLA alerts - and send an excel spreadsheet along to rich.

	-bryan


On 4/30/07 13:37, Pat Van Buskirk wrote:
> We found that it generates an alert, in grey, for the t5, with a DCSxx 
> origin and monitor point ifdtp. The severity is marked as unknown with 
> the action, "The severity for this alert has not been identified."
> 
> We're talking to Rob Long about how we can correct the alert to be more 
> meaningful.
> 
> Cheers,
> Pat
> 
> 
> Ken Sowinski wrote:
>> On Sun, 29 Apr 2007, Ken Sowinski wrote:
>> 
>>> When a deformatter fails there is no power presented to the T5 and the 
>>> TP monitor point will read close to zero.  The Modcomps will flag the 
>>> data and present a checker message on the printer and the error screen. 
>>> In this case there should have been four messages about "TP out of 
>>> range" for each of the EVLA antennas in use at the time.
>> 
>> I just examined the Modcomp checker and must revise this
>> statement.  When there is no backend TP the data will
>> be flagged however there will be no checker messages.
>> All messages have been suppressed for EVLA antennas
>> because all but one make no sense.  The one that does
>> make sense is: backend TP out of range.  Unless there
>> is serious clamor I do not propose to change the Modcomps
>> to correct this.
>> 
>> We should be sure that the CMP generates alerts for this
>> condition and that they are considered 'serious'.  I 
>> understand that idcaf catches these alerts and turns them
>> into flags, though this particular flagging event has not
>> been explicitly tested.
>> 
>> _______________________________________________
>> evlatests mailing list
>> evlatests at listmgr.cv.nrao.edu
>> http://listmgr.cv.nrao.edu/mailman/listinfo/evlatests
>> 
>