Re: EDD/DM: Passing multiple arguments for color rule definition ?

[tvedt@noao.edu (Janet Tvedt)]

> From Marian.Zurek@cern.ch Tue Jun  3 07:51:21 1997
> Sender: mzurek@cern.ch
> Date: Tue, 03 Jun 1997 16:45:11 +0200
> From: Marian ZUREK <Marian.Zurek@cern.ch>
> Organization: CERN. European Lab. for Particle Physics
> X-Mailer: Mozilla 2.02 (X11; I; SunOS 5.5.1 sun4u)
> Mime-Version: 1.0
> To: "Anna M. Estes" <a.m.estes@larc.nasa.gov>
> Cc: tech-talk@aps.anl.gov, kerstien@luke.atdiv.lanl.gov
> Subject: Re: EDD/DM: Passing multiple arguments for color rule  definition ?
> Content-Transfer-Encoding: 7bit
> 
> > > In the EDD/DM I need to implement color rule which represents the
> > > highest alarm severity of two channels.
> > >
> > > Then I didn't found how to pass two or more arguments to the rule (is it
> > > possible at all ?)
> > >
> > Yes, it is possible to pass more than one argument.  However,
> > you can't directly compare one alarm severity to another since
> > the right hand terms (the terms following the comparators)
> > are basically constants.
> > 
> > In the modify property page for the item in the "color rule
> > arguments" field, you can enter something like:
> >         A=chan1.SEVR, B=chan2.SEVR
> > 
> > Your color rule definition could be something like:
> >         $(A)    equals          MAJOR   and
> >         $(B)    less than       2       use     <A>B color>
> >         $(A)    equals          MINOR   and
> >         $(B)    equals          NONE    use     <A>B color>
> >         $(B)    equals          MAJOR   and
> >         $(A)    less than       2       use     <B>A color>
> >         $(B)    equals          MINOR   and
> >         $(A)    equals          NONE    use     <B>A color>
> > 
> > 
> > Note that the color is selected on a "first match" basis,
> > Also comparisons are done based upon the type of entry, i.e.
> > if a string is in the third column, the value of the first
> > column will be compared using a string compare and a numerical
> > compare will be done otherwise. It's awkward since you have to
> > define all possible comparisons separately.
> > 
> > Let me know if you have more questions.
> 
> Thanks for your reply.
> 
> I put the rule as below:
> 
>          $(A).SEVR    equals          MAJOR   or
>          $(B).SEVR    equals          MAJROR  use     <A>B color>
>          $(A).SEVR    equals          MINOR   or 
>          $(B).SEVR    equals          MINOR   use     <A>B color>
>          $(B).SEVR    equals          NO_ALARM   and
>          $(A).SEVR    equals          NO_ALARM use     <B>A color>
>          
> and passed arguments to them: 
> 	A=XXX:YYY:Z:chan1Alarm,B=XXX:YYY:Z:chan2Alarm
> 
> But then when I activate the display dm "dies" (not possible to perform
> any action on the display, besides killing it from WM)
> Is there any limit concerning the total length of the arguments in the
> line ?
> Thanks for any comments.
> 
> Regards,
> Marian
> --
> Marian Zurek
> CERN/ECP-CO
> 
> 

Yes, I believe the 29 character limit applies here.  DM also dies
when attempting to use strings longer than 29 characters for display
arguments in related display objects.

---------------------------------------------------------------------------
Janet Tvedt, Engineering Technical Services     Internet: tvedt@noao.edu
National Optical Astronomy Observatories        Phone:    (520) 318-8388
950 N. Cherry Ave., Tucson, AZ  85719           FAX:      (520) 318-8360