pyuvdata

pyuvdata copied to clipboard

Adding support for future array shapes in UVBeam objects

2

Following the merge of #909, `UVBeam` objects and methods now need to be updated to allow for the new handling of multiple spectral windows, and more generally to allow for...

kartographer

Add some metadata to UVFlag

2

UVFlag is missing some important metadata. The spw information needs to be added to support flexible spectral windows - spw_array - flex_spw_id_array - telescope_name - channel_width - antenna_numbers - antenna_names...

bhazelton

Warnings about future array shapes

1

Should we start warning on file read about future array shapes? We could add an option to `read` to convert to the future shapes on read to avoid the warning....

bhazelton

Add deprecation warnings for `phase_type`, `phase_center_ra/dec`, `frame`, `epoch` attributes

1

These will be going away in version 3.0 favor of the new phasing approach.

bhazelton

Adding support for flexible spws with UVFlag objects

1

Following the merge of #909, `UVFlag` objects and methods now need to be updated to allow for the new handling of multiple spectral windows, and more generally to allow for...

kartographer

Similar to the one on UVData, desired by HERA users.

bhazelton

For better typing and robust checking of things.

bhazelton

There are a lot of checks that are done in the interpolation methods, some of which are more compute-intensive than others. For example, #1144 adds the ability to skip one...

steven-murray

Rethink sky-based calibration meta-data in UVCal

1

Nsources for sky-based calibration is a useful concept but doesn’t really capture everything we want. We should make sure that this and several other sky-optional parameters really capture the full-provenance...

jpober

Needed now that we support multiple phase centers.

bhazelton