Skip to content

Releases

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 14 Nov 12:11

The owner released 0.2.0 on 2026-11-14. Its finish line
(research/finish-plan.md section 1) is met in part, and the parts not met
move to 0.3.0 (research/roadmap.md).

Known limitations

  • Not every stage is within its oracle tolerance.
    • E2-B is the acceptance run on processed LUNO MeerKAT L-band data against
      CASA 6.7.6.14, WSClean and QuartiCal (research/e2-acceptance.md 7.3-7.5).
    • Met: run and write-back, the readers (casacore, CASA listobs and
      flagmanager, WSClean, dask-ms), FITS output, gridding (exact on all
      1.1e9 cells), K, KCROSS, Xf, Df, and 3C 286 polarisation parity
      (|Δχ| ≤ 0.055°).
    • Not met, in the frozen and in the amended arm:
      • Gpol: median 0.124° in the amended arm, against a 0.1° limit.
      • The fcal and gcal K G B composites: median 1.1e-3.
      • CASA applycal on rang's tables: 40 cells over, max 25 eps; flags exact.
      • Image gate 3c.
      • Polarisation angle on 1830−211: |Δχ| up to 13°.
      • Transfer χ (polarisation angle carried from calibrator to target).
      • Rang's leakage: 0.30 %.
    • The diagnosis (research/e2b-misses.md, from code and archived numbers;
      no new runs) confirms no rang bug among the seven. Its likely causes:
      • CASA's oracle solved on different flags and weights (composites);
      • the estimators weight data differently (Gpol);
      • float32 rounding in CASA's long apply chain (applycal);
      • a scorer error and unmasked cleaning (3c);
      • χ at p of 0.02-0.06 % (1830−211);
      • LUNO's receptor angle and ionospheric RM (transfer χ).
    • Pre-registered arms A1-A5 test these in v0.3.0.
  • The measurements still to come are now v0.3.0 work:
    • the E2-A run on ESO 137;
    • E3, the comparison with CARACal's MeerKAT strategy (image quality, flux,
      wall time and memory);
    • the E5 review.
  • Native MeerKAT data is not tested. The acceptance data is processed LUNO
    data plus simulation (issue #7).
  • No absolute χ claim. LUNO's χ offset is not explained; see
    research/chi-offset.md.
  • flagdata mode tfcrop is refused, and the trained flagger is not shipped.

Changes since 0.1.0

  • Fixed (2026-11-14): a tools/heavy_lock.py run or tools/check_all.py started inside a heavy-lock
    hold (RANG_HEAVY_LOCK_HELD, set by heavy_lock.py run for its child) runs inside that hold
    instead of queueing again. A check wrapped in heavy_lock.py run held 4 slots idle for five hours
    while its own inner ticket waited, and would deadlock on a full queue. A nested request for more
    than the hold warns and still runs.

  • New (2026-11-14): tools/heavy_lock.py status prints each hold's real CPU use (its process tree,
    sampled for 2 s) next to its booked slots, marks a hold IDLE under 5 % of one core per booked slot,
    and ends with booked N slots, using ~M cores. Report only; nothing is stopped.

  • Fixed (correctness audit, research/correctness-audit-2026-11-13.md): bad input now fails clearly
    instead of running wrong. A NaN visibility made every gain, bandpass, delay or Df solution NaN with
    its flag clear; non-finite data, model and weight cells are now flagged, which gives exactly the
    solution of the same cells flagged (gain, bandpass, delay, KCROSS, Xf, Df). core_grid.invert(gridder="wgrid") with a GPU device raises instead of
    running on the CPU. gemclean's FITS reader (-predict models, -fits-mask) no longer panics on a
    non-ASCII header byte. -threshold, -abs-threshold and -auto-threshold must be finite and not
    negative. The gain and bandpass solvers refuse zero rows and per-row arrays of the wrong length; delay refuses zero rows.
    Write-back refuses out-of-range DATA_DESCRIPTION ids (a negative one picked the last row). Flag-version
    names with \ : * ? " < > | are refused on every platform. fluxstd.manual refuses non-positive
    frequencies. No default's numbers change.

  • Changed (task df-flag-rule, research/p-flag-spread.md): with apply.parang, P now flags as CASA's
    applycal(parang=True) does on linear feeds: a cell with any correlation flagged after the tables
    (input flags, a bad receptor, a Df-flagged cross hand) is flagged in all four, since P rotates XX and
    YY out of all four correlations. New key apply.parang_flags (spread, the default; none, the
    previous flags) and parang_flags= on rang.applycal.applycal and rang.cal_pol.apply. Values are
    unchanged; without parang nothing changes.

  • Fixed (E5 final E5-02): gemclean -model-column DATA, or a model column equal to the column being
    imaged (-data-column, or CORRECTED_DATA when the MS has it), overwrote that column after imaging;
    both are refused with exit 2 before anything is read. -no-update-model-required still writes nothing.

  • Changed (E5 final F-05): the licence page and THIRD-PARTY-NOTICES.txt list CASA's C++ sources that
    the calibration and flag-extension ports follow (GPL-2.0-or-later, LGPL-2.0/2.1-or-later), with
    their copyright notices; each derived file names CASA.

  • Changed (E5 final F-01): astropy is a required dependency. Every polarisation solve and apply.parang
    take the parallactic angle from it, and a bare pip install rang-core stopped there with
    ModuleNotFoundError; the imaging extra is kept and now adds nothing.

  • New: a known-limits page (docs/limits.md, linked from the README): scope, flagging, calibration,
    self-calibration, imaging and platform limits with the reports behind them; the E2 and E3 results
    are added when they land (E5 final, research/e5-final.md).

  • Changed (finish-plan item 27, f11fdd1): an unset calibrate.refant (it was refused) means CARACal's
    auto choice, or antenna 0 when no antenna qualifies; the default selfcal reference antenna is the
    same choice (it was antenna 0), and selfcal.refant: auto runs; the image.niter default is
    1,000,000 (it was 100,000).

  • Changed: Measurement Set reads take a channel slice in the reader (core/src/ms.rs), 2.1-2.2x
    faster on the channel-chunked polarisation solves and bit-identical on 19 frozen comparisons
    (research/sliced-read.md).

  • Changed (E5 pre-review "Later" findings, research/e5-prereview.md section 2.3): image.fits_mask
    and a selfcal FITS cleanmask_method are read relative to the configuration file, as flag.strategy
    and calibrate.model.lsm; deprecated: a mask found only relative to the working directory is still
    used, with a warning, and a mask found in neither place is refused before anything runs (E5-41).
    Repeated YAML keys are refused with their line numbers (PyYAML kept the last one). Unknown commands and
    options exit 2 on stderr (was 1); --version works after other global options; run --force STAGE of a
    stage outside run.stages is refused; the complex-term refusals and unknown term keys say what to change
    (E5-40). Data whose OBSERVATION TELESCOPE_NAME is not MeerKAT run with a warning, and state.json
    records telescope (E5-39). A flag version left unlisted by a kill is listed by the next save of the same
    flags; a flag version the last attempt recorded but the MS no longer has is warned about
    (restore_missing) (E5-42). Every source file carries an SPDX GPL-3.0-or-later line (E5-45).

  • New: calibrate.average_time (default false; task E2, research/e2-average-time.md). With it on,
    the K, G, B, F, Gpol, KCROSS, Xf and Df solves use CASA's estimator for long intervals: data and
    model averaged in time within each solution interval (weighted means over unflagged cells after the
    pre-applied tables and P, weight the sum, per baseline, channel and correlation), streamed in blocks
    of rows, and the memory plan counts the averaged rows. E2's whole-scan solves on 4096-channel
    MeerKAT data (176 GiB per interval unaveraged) then fit data.memory_limit_gb: 8. Off, every
    solve and the stage hash are unchanged. Refused with a complex term.

  • New: selfcal.average_time (default false; task E2): Sp and Sa solve on data and model averaged
    in time within each solution interval, as calibrate.average_time does, so CARACal's solint 120 fits
    8 GiB at 4,096 channels (333 GiB per interval without). Not CubiCal's estimator, which solves every
    sample (owner item 33(3)). Off, the stage hash is unchanged. Refused with Sd.

  • New: calibrate.average_freq (default false; task E2, the pre-registered "E2-B amended" arm,
    research/e2-average-freq.md): the G, F and Gpol solves average their data and model over the
    window's channels before solving (weighted means per row and correlation after the pre-applies and
    P), as CASA's G-type solves do; K, B, KCROSS, Xf and Df are unchanged. Off, every solve and the
    stage hash are unchanged.

  • Changed (owner decisions on the E5 pre-review, research/e5-prereview.md section 3): receipts are
    rang.receipt version 5; a Measurement Set a command modified is listed by its listing_sha256 (file
    sizes and mtimes), not a full content hash; the stage summaries hash the flags, gain solutions and images
    written and name the tables and settings behind a written column (E5-20). This holds for every directory
    a command modified, not only the MS. The default run.stages is the whole chain, flag, calibrate, apply, image, selfcal (was flag,
    calibrate, image, which imaged uncalibrated DATA) (E5-28). The simms antenna tables data/*.itrf.txt are
    recorded in docs/licence.md as facts, not code; the sdist carries only meerkat.itrf.txt, which GeMClean
    compiles in (E5-11). docs/licence.md lists codex-africanus and katdal's test helpers (BSD-3), and as
    behaviour reimplemented with no code copied CARACal's get_refant, msutils, CASA's flag extension,
    fluxscale and applycal semantics and casacore's table formats, plus casacore-data's observatory
    positions (E5-33). rang/data/README.md records the source and SHA256 of casacore_observatories.json
    (E5-34). The sdist leaves out .claude/ and the checkout tools under tools/ other than `too...

Read more

v0.1.0

Choose a tag to compare

@github-actions github-actions released this 02 Nov 14:49

First release. A research demonstrator for MeerKAT calibration and
flagging, not an operational calibrator; no advantage over the state of
the art is claimed.

The Rust core. The calibration chain of the gain-TV flagging
experiment runs in one Rust core, reached from Python through the PyO3
extension rang._core: fused visibility statistics, a QuartiCal-style
gain solver, the component predictor, blosc decoding of the public zarr
stores with HTTP range reads, the Tricolour strategies and SumThreshold,
WSClean imaging weights, a w-stacking gridder and the exact wgridder, a
read-only Measurement Set reader and a casacore table writer that creates
Measurement Sets and CASA calibration tables byte-identical to casacore
3.8.1 and CASA 6.7.6 (bar uninitialised memory). Every port is checked against its upstream oracle
(QuartiCal, Tricolour, AOFlagger, WSClean, python-casacore, casacure) or
against the archived results of the frozen campaigns.

Simplification and speed. The solver, the fused pass, SumThreshold and
the gridder run in parallel; the w-stacking gridder and FFT also run on the
GPU through wgpu behind the gpu feature. The ctypes backend is gone:
importing rang or calling a kernel never runs Cargo, and the extension
releases the GIL around every kernel. One command line, rang-core STAGE VERB, writes a rang.receipt per call and a rang.archive per run. The
frozen QuartiCal and Stimela campaigns, their containers and modules moved
to history/; the package keeps verbatim extracts of what the core uses.
The package was renamed from rangtoy to rang (distribution
rang-core). rang-core --version and rang.__version__ report the
version.

Wheels and CI. One abi3 wheel per platform for CPython 3.10 and newer:
Linux x86_64 and aarch64 (manylinux_2_28), macOS arm64 and x86_64, and
Windows x86_64, each tested on CPython 3.10 and 3.14 on its own OS with
Cargo absent, with casacure as a second oracle of the table reader and
writer. A v* tag that equals the pyproject.toml version attaches the
wheels and the sdist to a GitHub release and publishes them to PyPI by
trusted publishing. The sdist holds only the crates, the Python package
and the tests the wheel runs.

Documentation. A Sphinx site (https://pythonic.nl/rang-core/)
with installation, concepts, the command line, the API reference and the
research story; five executed tutorial notebooks (data and rank, flagging
step by step, gains and TV, imaging, the flagging experiment) and two
science notebooks (the gain-TV verdict; beam and pointing).

Science verdicts. The gain-TV-guided flagging experiment is closed as
null: on LUNO 1934−638 at four stations and across the whole array, on
PKS 1830−211 under a stored and a scalar model, under CARACal's field model
and with a closure-invariant arm, 90 pre-registered calls gave 64 null and
26 undecidable, none better or worse, and the method costs 4.6–5.9× the
baseline. The solver study changed no default (the QuartiCal issue 452
weight fix is opt-in through RANG_SOLVE_OPTIONS). For beam and pointing,
the SARAO holography beam is the reference and the SARAO/SKA Gaussian
pointing fit is ported bit-exact; the identifiability survey finds
per-antenna pointing and squint constrainable on the calibrator and ESO137
data, array-common pointing and ellipticity on the ESO137 track, and beam
width nowhere. Pointing self-calibration against those baselines is the
next step. Negative results are kept in research/.
This covers a gain-TV-guided threshold policy; a flagger trained on gain TV
is a separate question, not yet tested.

Provenance and the wheel (wave 4 fixes). Receipts (rang.receipt
version 3) record every result-affecting RANG_* variable from one registry
and the package source; the solver takes its options as an argument; commit
is null outside a checkout (W4-1). The closure and flux-standard kernels run
in the extension, so no kernel call builds with Cargo and the wheel is
self-contained (W4-3).