pyuvdata
pyuvdata copied to clipboard
RadioAstronomySoftwareGroup
A pythonic interface for radio astronomy interferometry data (uvfits, miriad, others)
sky_field should not be required for sky style calibrations. Maybe should be an RA/dec in addition to (or instead of) of string.
x_orientation keyword might need some adaptation to support arrays where the dishes steer/rotate.
Both quality_array and total_quality_array on UVCal are used, but both should be optional.
Should use UVFlag to support flags in general. Flags in a UVCal object should indicate a calibration solution that is not to be used; they are not a way to...
time_array should be used, but time_range should be replaced by an integration_length-like array that defines what range of times the solution applies to. This will require some work on uvcalibrate...
It would be nice to have partial I/O capabilities for `UVCal` objects and `calfits` files. Just FYI, I did a line-profile on `UVCal.read_calfits` on a decently large file (~80 MB),...
We're planning to use UVCal objects to store mock gain errors. Technically, these aren't calibration solutions, since they weren't derived from any calibration algorithm. (The goal would be to test...
Right now the limiting factor in accessing the data quickly is looking up the indices corresponding to a given key. This would be substantially reduced if we can store the...
When reviewing #840, it occurred to me that we don't have a canonical reference for what we mean when we say ECEF vs ENU vs rotECEF (and that XYZ ==...
Occasionally I hear that pyuvdata is slow, though without further investigation this complaint is impossible to decouple from the size of the data being read.* However since we do not...
Metadata
Owner
Metadata
A pythonic interface for radio astronomy interferometry data (uvfits, miriad, others)