pyuvdata
pyuvdata copied to clipboard
A pythonic interface for radio astronomy interferometry data (uvfits, miriad, others)
On import of a single pol or feed beam the rotate_pol option sets whether to create an opposite polarization beam by rotating by 90 degrees. The default behavior is rotate_pol...
UVFlag currently implements a `clear_unused_attributes` function to try to get rid of old attributes that no long make sense when changing forms (e.g. going to waterfall, or antenna mode). Some...
As described in the current UVH5 memo, the UVH5 format seems to assume/require that antennas have only one position for all the visibilities in the file. Normally data are not...
UVH5 requires that all cross-polarizations for each pair of antennas are grouped together in the `visdata` dataset. In fact, `Npols` is a dimension of `visdata`. This is fine for radio...
Although `UVParameter` attributes can be individually accessed, providing a functionality of a convenience function that prints the summary of the parameters, somewhat along the lines of a `FITS` header or...
This would have similar logic to the `to_waterfall` method, but it would apply a collapse method over baselines associated with each antenna. There would be some double counting, since each...
As currently implemented, uvcal.check() throws a ValueError if _any_ uvcal object is missing this parameter. See https://pyuvdata.readthedocs.io/en/latest/uvcal_parameters.html.
Following the merge of #909, the addition of the flexible spectral windows feature removes the need for the spectral window axis to be present, as its length is always equal...
Following the merge of #909, the `frequency_average` method needs to be upgraded to handle this new feature, particularly when the number of spectral windows is greater than 1. After this...
Hi, I tried using the software for reading some simulated SKA data (obtained using OSKAR simulator in the CASA Measurement Set format (.ms)). It gave me an error given in...