Skip to main content

pytauargus-tui

An interactive terminal UI for Tau-Argus, the statistical disclosure control engine. It is a thin view over the pytauargus engine — every action is a call the headless CLI already makes — and installing it gives you the tauargus CLI as well.

Screenshots

Loaded table — every cell coloured by its safety status

Suppression preview — inspect the throwaway result before accepting

Accepted — the preview becomes the working session

What it does

  • Runs your .arb batch — the full Tau-Argus pipeline (apriori safety rules, suppression, rounding, audit) with every computed table browsable. Start without a file and a .arb file browser opens.
  • Colours cells by status — green safe · red unsafe (a sensitive value) · cyan protected · yellow hidden by a suppression · dim empty. All 14 engine status codes are recognised and named.
  • Shows what any cell means — value, status name, pending mark, and after an audit the realised feasibility interval, for the cell under the cursor.
  • Lets you mark cells before solving — u require suppression, p protect (keep), S override safe. Marks are instant draft edits with toggle/replace and undo/redo; the solver never runs until you ask.
  • Previews suppression and rounding — s (OPT, whole table) and r (RND) run on a throwaway copy of your batch: you inspect the previewed grid, then y accepts or n cancels. Your working table never changes behind your back, and a preview that is no longer current is flagged.
  • Audits — realised feasibility intervals per cell (a).
  • Exports — writes the accepted table as a legacy INTERMEDIATE .tab file (o).
  • Saves the workspace — a versioned, fingerprinted JSON manifest of everything you did (accepted operations, cell marks) next to the .arb (w).
  • Reopens a saved workspace — launch tauargus-tui on the .workspace.json (or pick it in the file browser): the accepted result is rebuilt through the engine, the pending draft comes back (undoable), and the revisions are continuous. If the .arb changed since the save, the old outcome is not treated as current — the current input opens fresh instead, with a clear message.
  • Writes a replay batch — R materialises the accepted recipe as a headless-runnable .arb (plus apriori files) next to the input, so tauargus run <stem>.replay.arb reproduces the recorded operator intent.

What it can't do (yet)

  • Mark total cells — that needs the real total code, which the display labels do not preserve; the app blocks such marks with a message.
  • Choose the rounding base — r always uses the engine's minimum base.
  • Work on several batches — one .arb per session, and the batch spec itself is not editable from the UI.

Install

pip install pytauargus-tui
# or, as an extra of the engine package:
pip install "pytauargus[tui]"

Run

tauargus-tui                          # opens a file browser (.arb + saved workspaces)
tauargus-tui path/to/batch.arb        # opens that .arb batch directly
tauargus-tui path/to/batch.workspace.json   # reopens a saved workspace

Full user guide — every key, every status code, the whole workflow: docs/tui.md.

Develop (monorepo)

cd bindings/tui
uv sync --extra test
.venv/bin/python -m pytest

Metadata

Release files for pytauargus-tui 0.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for pytauargus-tui 0.4.0
File Interpreter ABI Platform
pytauargus_tui-0.4.0-py3-none-any.whl Python 3 none any Details

Release files / pytauargus_tui-0.4.0-py3-none-any.whl

Download URL pytauargus_tui-0.4.0-py3-none-any.whl
Size 28.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f506bfd33e6b691e9bab99b2fa7ab63c38c0359ddcbc80a3ba568c259cadf3b5
BLAKE2b-256 checksum
How to use checksums
d6bfc0d70fd1e440b6bc841e03cfe12e35cd7556cde8ad987d314fa56ca8baed
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 12, 2026.

Transparency log

Release history Release notifications | RSS feed

0.5.5

1 release file

0.5.4

1 release file

0.5.3

1 release file

0.5.2

1 release file

0.5.1

1 release file

0.5.0

1 release file

This release

0.4.0 This release

1 release file

0.3.4

1 release file

0.3.3

1 release file

0.3.2

1 release file

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page