Send array config + subband number/freq. to atv (aka rtmon)

[hsuyeep]

Currently, the parameters extracted from the parset by acontrol are not being fully passed to the various clients. AARTFAAC TV (atv) does not receive array configuration information, and the freq. info is hardcoded in the call to atv. The following are thus needed to atv:

• Array config
• Freq. of subband
• Polarization or stokes (Currently atv images a single pol., but in future it might be required to display both pols, or a stokes I created by atv, or cycle between the pols for diagnostics.)

[hsuyeep]

• List of antenna to be flagged. Different HBA configurations could result in one of the HBA tiles not being analog beamformed, but out correlator does not know or care. We can create a list of antennae to be flagged, which can be passed to both atv and calim pipeline (which already takes such a parameter in its xml configuration file).
• List of objects to be monitored in QuickLook images. Should be able to specify the RA/Dec of a source, which can then be kept under observation, say by atv.

[Error323]

That's a very nice idea indeed.

On Mon, Jun 29, 2015 at 2:46 PM, Peeyush Prasad [email protected]
wrote:

List of antenna to be flagged. Different HBA configurations could
result in one of the HBA tiles not being analog beamformed, but out
correlator does not know or care. We can create a list of antennae to be
flagged, which can be passed to both atv and calim pipeline (which already
takes such a parameter in its xml configuration file).

List of objects to be monitored in QuickLook images. Should be able to
specify the RA/Dec of a source, which can then be kept under observation,
say by atv.

—
Reply to this email directly or view it on GitHub
#6 (comment)
.

| Folkert Huizinga | [email protected]
| Sterrenkundig Instituut Anton Pannekoek | Phone: (020) 525 7855
| Universiteit van Amsterdam | Room: C4.142
| Science Park 904 |
| P.O. Box: 94249 |
| 1090 GE Amsterdam | Tuesday is my day off