Skip to main content

slop Kanna doing Wi-Fi plumbing

csiphon

csiphon is an online-first processing library for WiFi Channel State Information. Compose reusable DSP steps, compile them against your capture setup, then pour a complete recording or stream live chunks through the same validated pipeline.

from csiphon import AcquisitionProfile, Pipeline
from csiphon.steps import GainNormalize, Magnitude, WindowedVariance

# Define the hardware setup
profile = AcquisitionProfile(
    n_rx_antennas=3,
    subcarrier_indices=tuple(range(52)),
    sampling_rate_hz=1000.0,
)

# Define the pipeline steps
siphon = (
    Pipeline()
    .then(Magnitude())
    .then(GainNormalize())
    .then(WindowedVariance(win_size_s=0.1))
    .compile(profile)
)

# Generate a summary of the pipeline
print(siphon.describe())

# Push some data through it to run
features = siphon.pour(profile.raw_signal(csi, timestamps)).single()

What it does

  • Catches structural mistakes before execution. Compilation checks axes, shapes, value semantics, and physical representations before data starts flowing.
  • Runs the same recipe in batch or live. Every step states whether its streaming computation matches batch, differs intentionally, or requires the complete recording.
  • Supports branching pipelines. Split into parallel feature paths, merge them again, and expose named intermediate outlets.
  • Keeps real timestamps. Non-uniform CSI sampling is expected; resampling is explicit rather than silently assumed.
  • Describes itself. Steps and compiled siphons expose their contracts, layouts, parameters, and streaming behavior, and can save that information alongside results for reproducibility.
  • Measures itself. siphon.measure(signal) pours once and reports each step's time and output shape (memory on request), per step or for a named group of consecutive steps.

The built-in steps cover calibration, cleaning, filtering, delay and time-frequency transforms, temporal features, pooling, statistics, reduction, and restructuring. Custom steps use the same contracts and inspection tools.

Install

pip install -e .

The core only depends on NumPy. Install every optional transform with:

pip install -e ".[all]"

Runnable recipes live in examples/.

Metadata

Release files for csiphon 0.2.0

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

Source distribution (sdist)

Source distribution for csiphon 0.2.0
File Size Uploaded
csiphon-0.2.0.tar.gz 178.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for csiphon 0.2.0
File Interpreter ABI Platform
csiphon-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 346.5 kB

Release files / csiphon-0.2.0.tar.gz

Download URL csiphon-0.2.0.tar.gz
Size 178.8 kB
Tags Source
SHA-256 checksum
How to use checksums
38b82d8a11ac254a708434123f0d92cdd9c8df357316d55dcc3760c2c7c2a139
BLAKE2b-256 checksum
How to use checksums
11ddfa6ed164043ba1e350c260a06db44f48ecbb67fcf2f07c5b2efe3d46279f
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 Sep 16, 2026.

Transparency log

Release files / csiphon-0.2.0-py3-none-any.whl

Download URL csiphon-0.2.0-py3-none-any.whl
Size 167.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4ab91a754346116c91fc75a4cabc4293faa85003676f1d942f96f0aef0e7a120
BLAKE2b-256 checksum
How to use checksums
b04f3e1fb8a6d59c3bfb9b1140893f16d1d349326c28b2a83215297b345eb761
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 Sep 16, 2026.

Transparency log

Release history Release notifications | RSS feed

0.3.1

2 release files

0.3.0

2 release files

This release

0.2.0 This release

2 release files

0.1.1

2 release files

0.1.0

2 release files

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