ra-ng aims to be the home for agentic radio astronomy, from first steps to science-grade images and time series. rang-core is its Rust core and Python command line, MeerKAT first.
Documentation · Tutorials · Research index · Changelog
Status, November 2026: a tested research demonstrator, not an operational calibrator. No novelty is claimed: the goal is better calibration and imaging at comparable cost, or comparable quality at much lower cost, and neither has been shown. Two questions are closed as null, as tested: a gain-TV-guided threshold flagging policy, and beam and pointing. A flagger trained on gain TV stopped at its go/no-go test on one observation, before any training. A deeper field model (an external catalogue) is the first condition for reopening beam and pointing on real data. The reference imager GeMClean beats WSClean's time on 16 threads, not always on one, at 2.0–2.4 times the memory on the real pilot. Known limits.
What it is
- A Rust core. A Measurement Set reader and casacore table writer, zarr ingest with HTTP range fetch, QuartiCal's full-Jones solver, Tricolour's SumThreshold strategies, WSClean's imaging weights and w-stacking gridder (CPU, and GPU in a source build), ducc0's wgridder, CASA's flux standards and a component predictor.
- GeMClean, a reference imager.
gemcleantakes a Measurement Set to FITS with WSClean-style flags, using the exact image-domain value at each minor-cycle step. The wheel installs it as the commandgemclean. - A Python package and command line.
import rangreaches every kernel through the extensionrang._core, which releases the GIL.rang-core run config.yaml my.mstakes your MS to an image;rang-core research STAGE VERBreplays each chain. Every call writes a receipt. - The tools' file formats. CASA calibration tables, QuartiCal stores, Tigger,
WSClean and BBS sky models, H5parm, killMS solutions, CASA flag versions and
MeerKAT MVFv4 archives (
rang-core formats checkandconvert). - Oracles. Each port is gated on reproducing the upstream tool's output: QuartiCal, Tricolour, AOFlagger, WSClean, ducc0, casacore, CASA and katdal.
Install
pip install rang-core
One abi3 wheel per platform serves CPython 3.10 and newer, needs no Rust compiler
and carries every CPU kernel (the GPU paths need a source build with the core's gpu feature): Linux x86_64 and aarch64 (glibc 2.28 or newer), macOS
arm64 and x86_64, Windows x86_64.
| Extra | For |
|---|---|
notebook |
the tutorials and rang.notebook |
imaging |
nothing since astropy became required; kept so existing install lines work |
pointing, beam |
the JAX pointing path; the katbeam and EIDOS beam controls |
meerkat, formats |
MVFv4 archives through katdal; H5parm |
recipes, carta |
the Stimela2 recipes (Python 3.13 or older; installs nothing on 3.14); CARTA from the notebooks |
test, docs |
the test suite; the documentation site |
pip install rang-core installs 0.2.0, the first release with rang-core run and gemclean (known limitations in CHANGELOG.md). To follow main, install from source, with Rust 1.93 and cargo on PATH (more in the installation guide):
git clone https://github.com/gijzelaerr/rang-core && cd rang-core
python3 -m venv .venv
.venv/bin/python -m pip install -e '.[notebook,test]'
Quick start
The tutorial takes a simulated MeerKAT MS
to an image with rang-core run config.yaml a1-small.ms and gemclean in under a minute.
Or load the public 45 MB MeerKAT fixture (four antennas on PKS 1934−638) and solve its
full-Jones gains on the Rust core. With pip install 'rang-core[notebook]':
from rang.notebook import data, gains
zip_path = data.download_fixture("rang-cache") # once; SHA256 checked
ds = data.load_fixture(zip_path, cache_dir="rang-cache")
s = data.summary(ds)
print(s["dataset"], "|", s["antennas"], "|", s["channels"], "channels")
m = gains.solve(ds)["metrics"]
print(f"gain TV {m['tv']:.4f} test MSE {m['losses']['test']:.3f}")
After the download it takes about two seconds and prints:
fixture scan 9 (J1939-6342) | m000, m001, m002, m003 | 4096 channels
gain TV 0.1474 test MSE 24.920
The command line (rang-core -h; rang-core config defaults lists every configuration key):
| Command | What it does |
|---|---|
flag, calibrate, apply, image, selfcal, run config.yaml my.ms |
flag (Tricolour port); solve CARACal's K, G, B, A, F and polarisation terms into CASA tables (or complex into a QuartiCal store); apply to CORRECTED_DATA; image with gemclean; self-calibrate; resume |
research flags, gridder, wgridder, weights, imaging |
Tricolour's strategies, gridders, imaging weights, the imaging replay |
research campaign, campaign-array, campaign-1830, campaign-fieldmodel |
the LUNO real-data campaigns |
research injections, actions, prospective, signal, trend |
the flagging experiment's tracks |
research ms, meerkat; formats; check |
the readers, the file formats; the full local checks |
Documentation
- The site: installation, concepts, the command line and the research story.
- Tutorials and science notebooks: from a Measurement Set to an image with
rang-core run(on simulated truth); five tutorials (data and rank, flagging, gains and TV, imaging, the flagging experiment) and two research notebooks (the flagging verdict; beam and pointing), executed on the fixture. - API reference, generated from the docstrings.
Research results
| Question | Verdict | Report |
|---|---|---|
| Port the pipeline to one Rust core | Done: the archived chains reproduce, the solver to 1.4e-15; engineering, not a scientific claim | architecture, simplification |
| Does a gain-TV-guided threshold policy improve flagging? | Null: 90 pre-registered calls, none better or worse, at 4.6–5.9× the cost of CARACal's first pass | verdict |
| Can a flagger trained on gain TV be faster, with fewer tunable parameters? | Stopped before training: on one observation the gradient of gain TV barely ranks injected RFI (patch AUC 0.54–0.64 on four of five patterns, bar 0.80), where a residual score reaches 0.97–1.00. No network was trained, so speed and parameter count were not measured | F1 |
| Can selected pointing corrections beat the baselines on real data? | Null: self-calibration works in simulation (0.62′ to 0.054′), selection adds nothing measurable, and neither arm measures pointing on ESO137 with the self-calibrated model; an external catalogue is the first reopening condition | B1-3, B1-2, B1 |
| What is proven about CLEAN? | Data-fit convergence since Schwarz (1978); here a Gram-matrix formalism, Lean proofs and the measured exact-recovery transition | theory, transition |
| Can CLEAN with an exact value at each step beat WSClean? | No novelty claim. At matched gridding accuracy WSClean takes 1.21–2.35× as long at -j 16, 0.93–2.09× at -j 1; WSClean is faster on three of seven skies on one core at its best setting tried. With G7's defaults (coarse gridding) on the real pilot at 512 channels, at matched accuracy: 1.52× faster than WSClean at -j 16 and 1.31× slower at -j 1 natively, level at -j 16 and 1.24× slower at -j 1 on WSClean's OS layer, at 2.0–2.4× the memory (defaults; 3–5× before G2 and G7). Simulated skies and one real pilot; "4–5 major cycles" failed its held-out test (6, 6, 8, 5) |
GeMClean, speed, held-out test |
| An exact gridder | ducc0's wgridder ported at its speed; the w-stacking gridder on a GPU gains 1.2–3.3× over 16 threads | wgridder, GPU |
| A casacore table writer | Byte-identical to casacore 3.8.1 and CASA 6.7.6, bar uninitialised memory and alignment gaps | writer, the last of it |
| Re-validation against upstream | Tricolour 0.5.0-dev flag-identical; QuartiCal's #452 fix reproduced to 1e-15; AOFlagger agrees at kernel level, differs at stage level; CASA gaincal is 75–350× slower |
RV1, AOFlagger, gaincal |
Everything else, including the negative results and the earlier pointing pilots, is in the research index; the latest progress is in STATE.
Repository guide
| Path | Contents |
|---|---|
core/, src/ |
the Rust core (core/py builds rang._core); the root crate with the pointing simulation and gain TV |
python/rang/ |
the Python package, the command line and the JAX reference path |
notebooks/, docs/ |
the tutorials and science notebooks; the documentation site |
examples/, tests/ |
reproducible experiments and comparators; the test suite |
recipes/ |
Stimela2 recipes: rang-chain.yaml runs the commands on your MS; core-*.yaml are research recipes |
research/, formal/ |
reports and compact result archives; Lean proofs |
history/, data/ |
the frozen campaigns; fixture provenance |
Names
The project, repository, PyPI distribution and command line are rang-core; the Python package is rang.
"Rang" began as Radio Astronomy Next Generation, and rang is Dutch for rank, the first thing the identifiability survey measures.
Contributing
CONTRIBUTING.md has the local checks, the release procedure and the reporting rules.
Licence and data acknowledgements
rang-core is free software under the GNU General Public License, version 3 or later. Ported code keeps its upstream notices; no raw visibilities or beam maps are redistributed.
- MeerKAT data. The MeerKAT telescope is operated by the South African Radio Astronomy Observatory, which is a facility of the National Research Foundation, an agency of the Department of Science and Innovation.
- L-band holography beams (de Villiers 2023, DOI 10.48479/wdb0-h061): CC BY-NC 4.0.
- ESO137 field (Ramatsoku et al. 2020): CC BY 4.0.
Per upstream and dataset: licence and acknowledgements.
Citation
Cite the software through CITATION.cff (GitHub's "Cite this repository").
Metadata
Release files for rang-core 0.2.0
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 |
|---|---|---|---|---|
| rang_core-0.2.0.tar.gz | 2.0 MB | With provenance | Details for rang_core-0.2.0.tar.gz |
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| rang_core-0.2.0-cp310-abi3-win_amd64.whl | CPython 3.10 | abi3 | Windows x86-64 | Details for rang_core-0.2.0-cp310-abi3-win_amd64.whl |
| rang_core-0.2.0-cp310-abi3-manylinux_2_28_x86_64.whl | CPython 3.10 | abi3 | Linux glibc 2.28+ x86-64 | Details for rang_core-0.2.0-cp310-abi3-manylinux_2_28_x86_64.whl |
| rang_core-0.2.0-cp310-abi3-manylinux_2_28_aarch64.whl | CPython 3.10 | abi3 | Linux glibc 2.28+ ARM64 | Details for rang_core-0.2.0-cp310-abi3-manylinux_2_28_aarch64.whl |
| rang_core-0.2.0-cp310-abi3-macosx_11_0_arm64.whl | CPython 3.10 | abi3 | macOS 11.0+ ARM64 | Details for rang_core-0.2.0-cp310-abi3-macosx_11_0_arm64.whl |
| rang_core-0.2.0-cp310-abi3-macosx_10_12_x86_64.whl | CPython 3.10 | abi3 | macOS 10.12+ x86-64 | Details for rang_core-0.2.0-cp310-abi3-macosx_10_12_x86_64.whl |
Total release size: 23.7 MB
Release files / rang_core-0.2.0.tar.gz
| Download URL | rang_core-0.2.0.tar.gz |
|---|---|
| Size | 2.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8eeaf74ebeceefe54a938b8dcccef246c8903e907decc5d9db805dfc5e7204a2
|
|
BLAKE2b-256 checksum How to use checksums |
c6366128a43251598de350d4138bcad7da405d594d4813c5a6eb857371df36e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 14, 2026.
Transparency logRelease files / rang_core-0.2.0-cp310-abi3-win_amd64.whl
| Download URL | rang_core-0.2.0-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 4.7 MB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
69a23f2f0357c3916f167640b591cb78c78689650f403fa9f35b8efd0ae52333
|
|
BLAKE2b-256 checksum How to use checksums |
4dc6217ffa13df723ed0338f31d8502b24ee0e3c3d3e5763efbad79fc0c45916
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 14, 2026.
Transparency logRelease files / rang_core-0.2.0-cp310-abi3-manylinux_2_28_x86_64.whl
| Download URL | rang_core-0.2.0-cp310-abi3-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 4.9 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
55f42de99c23131f9ebf1a26d53b51808a67413ba434231a55cad3ebde0542a0
|
|
BLAKE2b-256 checksum How to use checksums |
91896f0df16e142ebe4f72308d69c3cb181608bf3dae808caa6839995782589e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 14, 2026.
Transparency logRelease files / rang_core-0.2.0-cp310-abi3-manylinux_2_28_aarch64.whl
| Download URL | rang_core-0.2.0-cp310-abi3-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 4.0 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
a146baf8a33ef18c5b22353c7d5204b679578e031b3b97b01e26e055cf208254
|
|
BLAKE2b-256 checksum How to use checksums |
6ea594de6520aa7117f4a7504f8103d8f37f3041d811bad7573ffb58ca2ad4cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 14, 2026.
Transparency logRelease files / rang_core-0.2.0-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | rang_core-0.2.0-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 3.7 MB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0183cdfd5051562d43c874cfa3914f0b0d83e15cd602bf70417be3e0659dfbeb
|
|
BLAKE2b-256 checksum How to use checksums |
2e403cb95a614f09fcbbdd6406eb4fbd6f9c6f530ae71c9c23384a5579eb3d4d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 14, 2026.
Transparency logRelease files / rang_core-0.2.0-cp310-abi3-macosx_10_12_x86_64.whl
| Download URL | rang_core-0.2.0-cp310-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 4.6 MB |
| Tags | CPython 3.10 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
70b0dea6f4e1b209f2c46c263e71827b0eb9b6dcb278dcb01a151e70416d6eb1
|
|
BLAKE2b-256 checksum How to use checksums |
a5ae733e6443bce1265e625171140955e687551a2c38244e5ed3b958dc5ae578
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 14, 2026.
Transparency logSecurity for rang-core 0.2.0
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 6 files in this release have been uploaded with provenance metadata.
Attestation for rang_core-0.2.0.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 Nov 14, 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.