Pyuvdata
A pythonic interface for radio astronomy interferometry data (uvfits, measurement sets, uvh5, others)
Install / Use
/learn @RadioAstronomySoftwareGroup/PyuvdataREADME
pyuvdata
pyuvdata defines a pythonic interface to interferometric data sets. Currently pyuvdata supports reading and writing of miriad, uvfits, CASA measurement sets and uvh5 files and reading of FHD (Fast Holographic Deconvolution) visibility save files, SMA Mir files and MWA correlator FITS files.
Documentation of the API, conventions used throughout the package, and a tutorial is hosted on ReadTheDocs.
Motivation
The main goals are:
- To provide a high quality, well documented path to convert between file formats.
- Support the direct use of interferometric datasets from python with minimal software.
- Provide precise data definitions and convention details via both human readable code and high quality documentation.
Package Details
pyuvdata has four major user classes:
- UVData: supports interferometric data (visibilities) and associated metadata
- UVCal: supports interferometric calibration solutions (antenna-based) and associated metadata.
- UVBeam: supports primary beams (E-field or power) and associated metadata. A number of analytic beam objects are also available and the BeamInterface object serves as a unified interface for UVBeam and analytic beam objects.
- UVFlag: A class to handle the manipulation and combination of flags for data sets. Also can convert raw data quality metrics into flags using thresholding. (This object is somewhat new and experimental. Consider it to be a beta version)
UVData File standard notes
- Miriad has been thoroughly tested with aipy-style Miriad files and minimally tested with ATCA files. Reading/writing Miriad files is not supported on Windows.
- UVFITS conforms to AIPS memo 117 (as of March 2020). It is tested against
FHD, CASA, and AIPS. However AIPS is limited to <80 antennas and CASA's
importuvfitstask does not seem to support >255 antennas. Because of this and other limitations to CASA'simportuvfitstask, we reccommend that users planning to work in CASA avoid usingimportuvfitsand use the measurement set writer instead. - CASA measurement sets, primarily conforming to
CASA Memo 229, with some elements taken
from the proposed v3.0 format documented in
CASA Memo 264. Measurement
sets are tested against datasets from VLA, MWA (filled via
cotter), ALMA, and SMA (filled using theimportuvfitstask). Extensive loopback testing has been done to verify that pyuvdata written measurement sets are compatible with CASA. - UVH5 is an HDF5-based file format defined by the HERA collaboration, details in the uvh5 memo. Note that this is a somewhat new format, so it may evolve a bit but we will strive to make future versions backwards compatible with the current format. It is probably not compatible with other interferometric HDF5 files defined by other groups.
- FHD (read-only support, tested against MWA and PAPER data)
- MIR (read-only support, though experimental write functions are available, tested against SMA data)
- MWA correlator FITS files (read-only support, tested against Cotter outputs and FHD)
UVCal file formats
- CalH5: a new an HDF5-based file format defined in pyuvdata, details in the calh5 memo. Note that this format is a somewhat new format, so it may evolve a bit but we will strive to make future versions backwards compatible with the current format.
- Measurement Set calibration files (read and write, gains/delay/bandpass supported, beta version). Tested against a limited set of SMA, LWA, and VLA calibration files generated in CASA.
- CalFITS: a custom format defined in pyuvdata, details in the calfits memo. Note that this format does not support all possible UVCal objects, so we prefer CalH5 which has full support for all variations of UVCal objects.
- FHD calibration files (read-only support)
UVBeam file formats
- BeamFITS: a custom format defined in pyuvdata that supports both regularly gridded beams and beams on a HEALPix grid for both E-field and power beams, details in the beamfits memo.
- CST beam text files (read only support) with a defined yaml file format for metadata, details here: cst settings file
- FEKO beam ffe files (read only support)
- MWA Beams (read only support)
Known Issues and Planned Improvements
- Incorporating numba to alleviate bottlenecks and to replace some existing cython extensions as appropriate.
See our issue log for a full list.
Community Guidelines
Contributions to this package to add new file formats or address any of the issues in the issue log are very welcome, as are bug reports and feature requests. Please see our guide on contributing
Telescopes
pyuvdata has been used with data from the following telescopes. If you use it on data from a telescope we don't have listed here please let us know how it went via an issue! We would like to make pyuvdata generally useful to the community for as many telescopes as possible.
- MWA
- HERA
- PAPER
- LWA
- ALMA
- VLA
- ATCA
- SMA
- ATA
- VLBA
Versioning
We use a generation.major.minor version number format. We use the generation
number for very significant improvements or major rewrites, the major number
to indicate substantial package changes (intended to be released every 3-4 months)
and the minor number to release smaller incremental updates (intended to be
released approximately monthly and which usually do not include breaking API
changes). We do our best to provide a significant period (usually 2 major
generations) of deprecation warnings for all breaking changes to the API.
We track all changes in our changelog.
History
pyuvdata was originally developed in the low frequency 21cm community to support the development of and interchange of data between calibration and foreground subtraction pipelines. Particular focus has been paid to supporting drift and phased array modes.
Citation
Please cite both of our JOSS papers:
Keating et al., (2025). pyuvdata v3: an interface for astronomical interferometric data sets in Python. Journal of Open Source Software, 10(109), 7482, https://doi.org/10.21105/joss.07482 [ADS Link]
Hazelton et al, (2017), pyuvdata: an interface for astronomical interferometeric datasets in python, Journal of Open Source Software, 2(10), 140, doi:10.21105/joss.00140 [ADS Link]
Installation
Simple installation via conda is available for users, developers should follow the directions under Developer Installation below.
For simple installation, the latest stable version is available via conda
(preferred: conda install -c conda-forge pyuvdata) or pip (pip install pyuvdata).
There are some optional dependencies that are required for specific functionality, which will not be installed automatically by conda or pip. See Dependencies for details on installing optional dependencies.
Dependencies
Required:
- astropy >= 6.0
- docstring_parser>=0.15
- h5py >= 3.7
- numba >= 0.57.0
- numpy >= 1.23
- pyerfa >= 2.0.1.1
- python >= 3.11
- pyyaml >= 5.4.1
- scipy >= 1.9
- setuptools_scm >= 8.1
Optional:
- astropy-healpix >= 1.0.2 (for working with beams in HEALPix formats)
- astroquery >= 0.4.4 (for enabling phasing to ephemeris objects using JPL-Horizons)
- hdf5plugin >= 3.3.1 (for enabling bitshuffle and other hdf5 compression filters in uvh5 files)
- lunarsky >=0.2.5 (for working with simulated datasets for lunar telescopes)
- matplotlib>=3.7 (for making plots)
- novas and novas_de405 (for using the NOVAS library for astrometry)
- pooch >= 1.8 (for downloading test data for tutorials)
- python-casacore >= 3.5.2 (for working with CASA measurement sets)
The numpy and astropy versions are important, so make sure these are up to date.
We suggest using conda to install all the dependencies. If you want to install
python-casacore and astropy-healpix, you'll need to add conda-forge as a channel
(conda config --add channels conda-forge).
If you do not want to use conda, the packages are also available on PyPI
(python-casacore may require more effort, see details for that package below).
You can install the optional dependencies via pip by specifying an option
when you install pyuvdata, as in pip install pyuvdata[healpix]
which will install all the required packages for using the HEALPix functionality
in pyuvdata. The options that can be passed in this way are:
astroquerycasahdf5_compressionhealpixlunarnovasplottingalltutorialtestdocdev
The first set (astroquery, casa, hdf5_compression, healpix,
``lun
Related Skills
node-connect
347.2kDiagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps
claude-opus-4-5-migration
108.0kMigrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5
frontend-design
108.0kCreate distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
model-usage
347.2kUse CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON.
