[evlatests] EVLA Flagging

[Chunai Cai]

Hi, Ken:

Yes, when you mentioned it, it was a "coming soon" situation, no follow-up 
from my side.....

If you refer to the edu.nrao.evla.commons.EVLAConstants class, no, Flagger 
didn't use the list. Even if Flagger uses the class to get the antenna 
list, whoever mantains the code still have to let others know that the 
code is changed and a new jar file is made for it.

As I told Bryan, it does not worth the overhead to get the big 
edu.nrao.evla.commons jar file into Flagger in order to just get the one
mixture list of evla and vla ids out, then parse through it to get evla
antennas out.

If it's crucial that Flagger includes the new evla antenna the 
minute it comes alive, we can think of a dynamic way of getting a updated 
list from somewhere.

Chunai




On Wed, 25 Oct 2006, Ken Sowinski wrote:

> On Wed, 25 Oct 2006, Bryan Butler wrote:
>
>> chunai tells me that antenna 26 is not even in the list of things that 
>> flagger
>> is checking, so the flags for 26 are getting generated on the Modcomp side 
>> of
>> things?  i'm guessing she should add antenna 26 to the list?
>
> I vaguely rememeber suggestingthat 26 be
> included in the list, but don't know if
> I really did, or if it was.  Does flagger
> use the facility we have in lace for defining
> EVLA antennas to the executor?
>
> Even if it is not in the list, the Modcomp
> will  generate flags for IFs which have
> outlandish T5 total power.
>
> Ken
>