This release is a pre-release and may not be stable for production use.
xarray Datasets from CASA Tables
Constructs xarray Datasets from CASA Tables via arcae.
The Variables contained in the Dataset are dask arrays backed by
deferred calls to arcae.lib.arrow_tables.Table.getcol, which release
the GIL and read through multiple independent table instances.
Supports writing Variables back to the respective column in the Table.
The intention behind this package is to support the Measurement Set as a data source and sink for the purposes of writing parallel, distributed Radio Astronomy algorithms.
Installation
To install with xarray support:
$ pip install dask-ms[xarray]Without xarray similar, but reduced Dataset functionality is replicated in dask-ms itself. Expert users may wish to use this option to reduce python package dependencies.
$ pip install dask-msDocumentation
Gitter Page
Example Usage
import dask.array as da
from daskms import xds_from_table, xds_to_table
# Create xarray datasets from Measurement Set "WSRT.MS"
ds = xds_from_table("WSRT.MS")
# Set the flag Variable on first Dataset to it's inverse
ds[0]['flag'] = (ds[0].flag.dims, da.logical_not(ds[0].flag))
# Write the flag column back to the Measurement Set
xds_to_table(ds, "WSRT.MS", "FLAG").compute()
print ds
[<xarray.Dataset>
Dimensions: (chan: 64, corr: 4, row: 6552, uvw: 3)
Coordinates:
ROWID (row) int32 dask.array<shape=(6552,), chunksize=(6552,)>
Dimensions without coordinates: chan, corr, row, uvw
Data variables:
IMAGING_WEIGHT (row, chan) float32 dask.array<shape=(6552, 64), chunksize=(6552, 64)>
ANTENNA1 (row) int32 dask.array<shape=(6552,), chunksize=(6552,)>
STATE_ID (row) int32 dask.array<shape=(6552,), chunksize=(6552,)>
EXPOSURE (row) float64 dask.array<shape=(6552,), chunksize=(6552,)>
MODEL_DATA (row, chan, corr) complex64 dask.array<shape=(6552, 64, 4), chunksize=(6552, 64, 4)>
FLAG_ROW (row) bool dask.array<shape=(6552,), chunksize=(6552,)>
CORRECTED_DATA (row, chan, corr) complex64 dask.array<shape=(6552, 64, 4), chunksize=(6552, 64, 4)>
PROCESSOR_ID (row) int32 dask.array<shape=(6552,), chunksize=(6552,)>
WEIGHT (row, corr) float32 dask.array<shape=(6552, 4), chunksize=(6552, 4)>
FLAG (row, chan, corr) bool dask.array<shape=(6552, 64, 4), chunksize=(6552, 64, 4)>
TIME (row) float64 dask.array<shape=(6552,), chunksize=(6552,)>
SIGMA (row, corr) float32 dask.array<shape=(6552, 4), chunksize=(6552, 4)>
SCAN_NUMBER (row) int32 dask.array<shape=(6552,), chunksize=(6552,)>
INTERVAL (row) float64 dask.array<shape=(6552,), chunksize=(6552,)>
OBSERVATION_ID (row) int32 dask.array<shape=(6552,), chunksize=(6552,)>
TIME_CENTROID (row) float64 dask.array<shape=(6552,), chunksize=(6552,)>
ARRAY_ID (row) int32 dask.array<shape=(6552,), chunksize=(6552,)>
ANTENNA2 (row) int32 dask.array<shape=(6552,), chunksize=(6552,)>
DATA (row, chan, corr) complex64 dask.array<shape=(6552, 64, 4), chunksize=(6552, 64, 4)>
FEED1 (row) int32 dask.array<shape=(6552,), chunksize=(6552,)>
FEED2 (row) int32 dask.array<shape=(6552,), chunksize=(6552,)>
UVW (row, uvw) float64 dask.array<shape=(6552, 3), chunksize=(6552, 3)>
Attributes:
FIELD_ID: 0
DATA_DESC_ID: 0]Limitations
Many Measurement Sets columns are defined as variably shaped, but the actual data is fixed. dask-ms will infer the shape of the data from the first row and must be consistent with that of other rows. For example, this may be issue where multiple Spectral Windows are present in the Measurement Set with differing channels per SPW.
dask-ms works around this by partitioning the Measurement Set into multiple datasets. The first row’s shape is used to infer the shape of the partition. Thus, in the case of multiple Spectral Window’s, we can partition the Measurement Set by DATA_DESC_ID to create a dataset for each Spectral Window.
Release files for dask-ms 0.3.0a1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dask_ms-0.3.0a1.tar.gz | 156.8 kB | With provenance | Details for dask_ms-0.3.0a1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dask_ms-0.3.0a1-py3-none-any.whl | Python 3 | none | any | Details for dask_ms-0.3.0a1-py3-none-any.whl |
Total release size: 321.8 kB
Release files / dask_ms-0.3.0a1.tar.gz
| Download URL | dask_ms-0.3.0a1.tar.gz |
|---|---|
| Size | 156.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
78025f4da2ecfd0e99f3b952604fc78a55d459b2d2fb04626cd0eeaa41af2635
|
|
BLAKE2b-256 checksum How to use checksums |
28c6666daf620bea416059732725c9203545685fbeb2862258a33d660e7be61b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / dask_ms-0.3.0a1-py3-none-any.whl
| Download URL | dask_ms-0.3.0a1-py3-none-any.whl |
|---|---|
| Size | 164.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0e4c29f6ae53a847cd9deb27bf411b47a464aad4cb0f10715c2239d757f5fb1e
|
|
BLAKE2b-256 checksum How to use checksums |
09b80934e21682ea479236e4d0051d2968038ab28e020b96672664d13a56e191
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logSecurity for dask-ms 0.3.0a1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for dask_ms-0.3.0a1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
