olab_rf
olab_rf is a local-first Python package for RF-derived telemetry. It
normalizes ADS-B, AIS, synthetic replay tracks, and scanner workflows into
Python APIs with a SQLite history store and an optional local web UI (a
demo/test surface over the Python backend, not a production frontend).
Migrated from ~/Projects/cuas_practice/src/ub_rf per
docs/plans/olab_packages_reorg_plan.md,
Migration sequence step 3. CUAS notebooks, data, tools, and project-specific
planning notes stay in cuas_practice, outside this package; cuas_practice
becomes a consumer of this package rather than owning the source.
The MVP is receive-only. Do not install Python dependencies into system Python; use a project virtual environment.
python3 -m venv venv
source venv/bin/activate
pip install "olab-rf[web,ais,pyrtlsdr,nats]"
Local development, against an olab_code checkout, to run the test
suite or make changes:
pip install -e "packages/olab_rf[dev,web,ais,pyrtlsdr,nats]"
pytest packages/olab_rf/tests -q
System package installation is intentionally not automated. Run
olab-rf-check to inspect local tool availability before installing SDR
decoder tools.
Inspect saved SQLite values with:
olab-rf-history favorites --config olab_rf.yaml
olab-rf-history frequency-scans --config olab_rf.yaml
Further reading
- Python API and validated active-channel scanner workflow: docs/python_api.md
- Installation and decoder setup (RTL-SDR,
readsb,rtl_ais, driver conflicts): docs/install.md - SDRTrunk/JMBE operator capability probe: docs/sdrtrunk_capability_probe.md
- Demo web UI boundary: docs/web_demo.md
- Radio voice segment integration: docs/voice_segment_integration.md
Examples
Runnable examples live under examples/: replay_tracks.py,
frequency_scan.py, baseline_then_scan.py, history.py, and
iq_range_scan.py (exercised directly by
tests/test_iq_range_scan_example.py).
Test Strategy
Most tests are model-free and run unconditionally. Tests requiring an
optional dependency (pyais for AIS parsing, msgpack for the NATS
transport, fastapi/uvicorn for the web demo) self-skip via
pytest.importorskip/existing guards when that extra isn't installed —
CI's base-only install runs a green, if smaller, subset; install
[dev,web,ais,pyrtlsdr,nats] locally for full coverage.
Metadata
Release files for olab-rf 0.1.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 | |
|---|---|---|---|
| olab_rf-0.1.0.tar.gz | 97.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| olab_rf-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 177.2 kB
Release files / olab_rf-0.1.0.tar.gz
| Download URL | olab_rf-0.1.0.tar.gz |
|---|---|
| Size | 97.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea7e828f8311e2f4eafa2c67e2629d1c857ae3d34cf0a52a0f4e887d8a4b77f9
|
|
BLAKE2b-256 checksum How to use checksums |
5f3e253bb9aa4e7dde469688b420fb064d1a4f623704714d09d1ae4e8aff9bfd
|
| 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 7, 2026.
Transparency logRelease files / olab_rf-0.1.0-py3-none-any.whl
| Download URL | olab_rf-0.1.0-py3-none-any.whl |
|---|---|
| Size | 79.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
de6fc8050eabf5cb3ae7b101f64083b01338033c5ec11fb6b692f8eac7b86d7d
|
|
BLAKE2b-256 checksum How to use checksums |
f85fc7217808531073464d4075a05007994e7d16191a7fdbb1766de396c78680
|
| 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 7, 2026.
Transparency log