pyuvdata

pyuvdata copied to clipboard

We noticed this function isn't used in the repo at all... maybe it's leftover from legacy code in QM?

adampbeardsley

UVFlag needs smarter key handling (like what is in `UVData`), which is a pre-requisite for `get_*` methods and the ability to track conjugated antpairs. Related to #651 and #704

nkern

When initializing a UVFlag from a UVCal object, the `time_range` parameter is currently ignored. This has not yet, but may make issues when trying to broadcast flags created from per...

mkolopanis

Make UVFlag add smarter

2

Right now the UVFlag add method requires an axis to be specified and it blindly concatenates. We should make it smarter to check for compatibility and figure out which axis...

adampbeardsley

Implement support for reading CST beam files with phi ranging from -180 to 180.

1

In the default configuration for CST's exported beam files, the phi/azimuthal angle ranges from 0 to 360 degrees. There is an option to export it as -180 to 180 degrees,...

mickeyhorn

read_cst_beam turning negative gain values into positives

2

I am attempting to use the read_cst_beam feature of UVBeam and am running into an odd bug. [Chiropter_NS_PECBico_ff70_YupZnull.txt](https://github.com/RadioAstronomySoftwareGroup/pyuvdata/files/4782880/Chiropter_NS_PECBico_ff70_YupZnull.txt) is a standard CST export file of the directivity/gain of the farfield...

mickeyhorn

Currently select has it's own logic that more or less duplicates what is in `_key2inds`.

bhazelton

modernize test files

1

adampbeardsley

Noted in #827 this block of code is used in the averaging feature of the compress by redundancy, but it is possible we could replace the for loops with a...

mkolopanis

In general, further work is required for tandem/hybrid calibration that combines sky and redundant. Need to determine what parameters are required. Or more generally, any iterative calibration is harder to...

jpober