pySTAMPS
Python-first STA(MPS)-style runtime for staged InSAR/PS processing, verification, and deterministic audit checks.
Run staged pipelines, inspect dataset progress, and validate outputs against a reference dataset.
Install
From source:
git clone git@github.com:sirbastiano/pystamps.git
cd pystamps
uv sync
uv run pystamps describe-backends
Editable install:
python -m pip install -e .
python -m pip install -e "[dev]"
cargo is required only for editable/source installs that build the Rust extension. Wheels from PyPI may avoid local compilation.
Run by stage
Set a local dataset path and always work on a writeable copy:
export DATASET_SOURCE=/path/to/original_dataset
export DATASET_COPY=/path/to/dataset_copy
cp -a "$DATASET_SOURCE" "$DATASET_COPY"
First, check status and verify what can execute:
uv run pystamps status --dataset "$DATASET_COPY"
Run a single stage or stage range:
uv run pystamps run --dataset "$DATASET_COPY" --start-step 1 --end-step 1 # stage 1 only
uv run pystamps run --dataset "$DATASET_COPY" --start-step 2 --end-step 2 # stage 2 only
uv run pystamps run --dataset "$DATASET_COPY" --start-step 3 --end-step 3 # stage 3 only
uv run pystamps run --dataset "$DATASET_COPY" --start-step 4 --end-step 4 # stage 4 only
uv run pystamps run --dataset "$DATASET_COPY" --start-step 5 --end-step 5 # stage 5 only
uv run pystamps run --dataset "$DATASET_COPY" --start-step 6 --end-step 6 # stage 6 only
uv run pystamps run --dataset "$DATASET_COPY" --start-step 7 --end-step 7 # stage 7 only
uv run pystamps run --dataset "$DATASET_COPY" --start-step 8 --end-step 8 # stage 8 only
uv run pystamps run --dataset "$DATASET_COPY" --start-step 1 --end-step 8 # full pipeline
Use --dry-run to preview actions without writing:
uv run pystamps run --dataset "$DATASET_COPY" --start-step 1 --end-step 8 --dry-run
Verify a run
export RUN_COPY=/path/to/run_copy
export GOLDEN_DATASET=/path/to/golden_dataset
uv run pystamps verify --run "$RUN_COPY" --golden "$GOLDEN_DATASET"
Stage-backend profile (optional)
uv run pystamps describe-backends
Create native-kernels.yaml and pass it with --config:
cat > native-kernels.yaml <<'YAML'
runtime:
backend: auto
stage2_kernel_backend: native
stage2_native_threads: 0
kernel_backend_overrides:
stage2_grid_accumulate: native
stage2_histogram: native
stage2_topofit: native
stage2_topofit_row_invariant: native
stage2_topofit_coh_row_invariant: native
stage4_edge_stats: native
stage7_scla: native
stage8_edge_noise: native
io_workers: 8
cpu_workers: 0
stage7_chunk_ps: 100000
stage8_chunk_edges: 200000
YAML
uv run pystamps --config native-kernels.yaml run --dataset "$DATASET_COPY" --start-step 2 --end-step 8
Use python backends for reference behavior in debugging, and native for the compiled Rust/CPU path.
Benchmarking and audit checkpoints
make benchmark
make audit
make audit reads the manifest in pystamps/data/audited_workflow_manifest.json.
Notes
- Do not point docs or examples at a fixed repository dataset path.
- Always treat outputs in your run tree as authoritative; avoid running on your only source copy.
- Optional repo assets are kept for parity and offline reproducibility, not required for runtime usage.
Read the docs
- Pipeline and science guide
- Quick Start
- Getting Started
- Usage
- Configuration
- Architecture
- Verification
- API Reference
- Release workflow
Notebooks
notebooks/start_here.ipynbnotebooks/00_pystamps_beginner_walkthrough.ipynb
Metadata
Release files for pystamps-insar 0.1.2
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 |
|---|---|---|---|---|
| pystamps_insar-0.1.2.tar.gz | 4.3 MB | Without provenance | Details for pystamps_insar-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pystamps_insar-0.1.2-cp314-cp314-manylinux_2_35_x86_64.whl | CPython 3.14 | CPython 3.14 | Linux glibc 2.35+ x86-64 | Details for pystamps_insar-0.1.2-cp314-cp314-manylinux_2_35_x86_64.whl |
Total release size: 4.8 MB
Release files / pystamps_insar-0.1.2.tar.gz
| Download URL | pystamps_insar-0.1.2.tar.gz |
|---|---|
| Size | 4.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9d9f81e77faec2422671de830507b9bbd191bfe33fec44b390ae5f833045620c
|
|
BLAKE2b-256 checksum How to use checksums |
cde14237e2b3de9f399d825ca1cce4477469ab97619a8c73d3c50fe57cebc085
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Release files / pystamps_insar-0.1.2-cp314-cp314-manylinux_2_35_x86_64.whl
| Download URL | pystamps_insar-0.1.2-cp314-cp314-manylinux_2_35_x86_64.whl |
|---|---|
| Size | 541.4 kB |
| Tags | CPython 3.14 Linux glibc 2.35+ x86-64 |
|
SHA-256 checksum How to use checksums |
a8c2224371ee82c7fa11a3f074bdca5852fb5d24a39bd4c12757afeeceb17bd5
|
|
BLAKE2b-256 checksum How to use checksums |
bd962079ed6c3145783865f6e16206b81565b3ed9c3305257b84c7e18a22525e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for pystamps-insar 0.1.2
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.