Pyuvdata

Latest version: v2.4.3

Safety actively analyzes 630217 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 8

2.2.8

Added
- Parameter `check_azza_domain` in `UVBeam.interp()`, which can turn off the (relatively
expensive) check on input az/za values.

2.2.7

Added
- The `UVCal.initialize_from_uvdata` method to initialize a UVCal object using metadata
from a UVData object.
- An option to `UVData.reorder_blts` to sort the autos before the crosses.
- Added new functionality to `UVData.check` to verify that auto-correlations are real-only,
along with an option to force them to be real-only if non-zero imaginary components are detected.

Changed
- `UVFlag.to_baseline()` uses internal time tolerances (both rtol and atol) stored in the UVParameter
`_time_array.tols` to check whether times in the UVFlag object and the input UVFlag/UVData object match.

Deprecated
- The `with_conjugates` keyword in favor of the `include_conjugates` keyword in the
`utils.get_baseline_redundancies` function.

2.2.6

Added
- A new attribute to `UVData` called `flex_spw_polarization_array`, of type=int and shape=(`Nspws`,),
which allows for individual spectral windows to carry different polarization data.
- Added the `_make_flex_pol` and `remove_flex_pol` methods to `UVData`, which allows for
one to convert a standard `UVData` object to one with "flexible-polarization".
- Added a new method to `MirParser` called `_apply_tsys`, which will convert MIR visibility data
from correlation coefficients to pseudo-Jy.
- Added a method to `Mir` called `_init_from_mir_parser`, which allows for one to pass
a `MirParser` object to be converted into a UVData object (rather than reading from
a file on disk).
- Added the `flex_spw` attribute to the `UVCal` class, which can be set to True by using
the new `_set_flex_spw` method.
- Added the optional `flex_spw_id_array` attribute to UVCal class, of type=int and
shape=(`Nfreqs`,), which indexes individual channels along the frequency axis to `spw_array`.
- Added `use_future_array_shapes` method to UVCal to allow users to convert to using the
future array shapes now, with support throughout UVCal methods and related utility
functions. Also added `use_current_array_shapes` to revert to the standard shapes.
- Added support for wide-band gain calibrations via the `wide_band` attribute on the
`UVCal` class, which can be set using the new `_set_wide_band` method.
- Added `time_range`, `lsts`, and `lst_range` kwargs from UVH5.write_uvh5_part() to UVData.write_uvh5_part().
- Added `time_range`, `lsts`, and `lst_range` kwargs from UVH5.write_uvh5_part() to UVData.write_uvh5_part().

Changed
- General performance improvements in the `read_mir` method.
- Enabled `read_mir` to read in dual- and full-polarization data.

Fixed
- Fixed a bug where `UVData.compress_by_redundancy` sometimes produced incorrectly
conjugated visibilities.
- Fixed a bug where `lsts` and `lst_range` got ignored when doing partial i/o with multiple files.

2.2.5

Added
- Support for reading MWAX correlator fits files.
- Added a warning when using `UVData.write_uvfits` when the `vis_units` attribute is
anything other than `Jy`.
- Added a warning when using `UVData.write_uvfits` if a UVData object has > 256 antennas,
recommending use of `UVData.write_ms` if intending to import the data into CASA.
- Reading writing of scan numbers for MS files as `UVData.scan_number_array`.
- Grouping of contiguous integrations for a phase center into "scan numbers" in `UVData._set_scan_numbers`.
This grouping defines `UVData.scan_number_array` when not originally present in the data (e.g. reading in
a non-MS file) and is used when writing to an MS file.
- Added a `filename` attribute to UVCal, UVBeam and UVFlag objects.
- Support for reading MWAX/birli uvfits files.
- Flexible spectral windows to `read_mwa_corr_fits`.

Changed
- Changed the `UVData.write_ms` to reduce processing time and memory footprint.
- Changed the order in which data are written in Measurement Set format via the method
`UVData.write_ms`, where data are now first grouped together by `scan_number_array`.
- Changed the defaults by which the `UVData.antenna_names` attribute is set when reading
measurement sets (used to default to station names, now uses antenna names if available
and the MS file was not written using the CASA `importuvfits` routine).
- Fixed a bug where `UVData.x_orientation` and `UVData.vis_units` were not being written
to / read from measurement sets.
- Updated the astroquery requirement to >= 0.4.4, due to changes in the API handling for
calls to JPL Horizons.
- Assumes uvfits files are in ITRF frame unless explicitly stated otherwise. Consistent with AIPS 117.
- Improved readability, functionality, and memory usage in `read_mwa_corr_fits`.

Fixed
- A bug in writing calfits files when the optional `time_range` parameter is not set.
- A bug where the `TIME_CENTROID` field was not being filled in data sets written by
`UVData.write_ms`, which caused odd behavior in some CASA routines (e.g., `gaincal`).
- A bug in reading in uvfits files with baseline coordinates that have suffixes of
'---SIN' or '---NCP' which are allowed in uvfits files.
- A bug that could cause some routines in CASA to fail when using data sets written by
`UVData.write_ms`.
- A bug that could have resulted in `UVData.__add__` combining objects together incorrectly
when containing overlapping time-baselines/polarization/frequency channels together
that were ordered differently for the two `UVData` objects.
- A bug that prevented `extra_keywords` keys with a value of `None` from being
saved to UVH5 files.
- A bug that resulted in the wrong expected shapes for data-like arrays when metadata
only UVData objects were set to use future array shapes.
- A bug that caused an error when writing non-double antenna diameters to measurement set files
- Added a warning in `utils.uvcalibrate` when uvdata x_orientation is not set.
- Fixed a bug in `UVBeam.efield_to_power` when there is only one feed.

2.2.4

Fixed
- Fixed a bug in converting non-crosspol power beams to real in `UVBeam.efield_to_power`.

2.2.3

Fixed
- A bug that resulted in coordinate queries via for solar-system objects `utils.lookup_jplhorizons` to throw an error. The workaround temporarily requires the precision for ephemerides to be limited to 0.05 arcseconds.
- A bug that resulted in a potential error when attempting to write out multi-phase-center data sets into the UVH5 file format.

Page 3 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.