pspipe
pspipe is the data-analysis pipeline used by the LOFAR Epoch of Reionization
and NenuFAR Cosmic Dawn projects. It turns calibrated low-frequency radio
MeasurementSets into images, weighted Kelvin visibility cubes, power spectra,
and foreground-separated products. It tracks observations and processing
revisions so that large, multi-night analyses remain reproducible.
It provides two commands:
psdbcreates configurations and manages observations and processing revisions;pspiperuns processing tasks on observations registered in that database.
The pipeline uses WSClean for imaging and
ps_eor for cubes, flagging, power spectra,
and ML-GPR. Optional MeasurementSet-processing tasks also call
DP3 and
NenuCal.
Documentation
The pspipe documentation follows the complete workflow from installation and calibrated MeasurementSets to images, visibility cubes, power spectra, multi-night combinations, and foreground removal. New users should begin with the getting-started page and then follow the user guide.
The documentation also includes the full configuration, command-line, and Python API references.
Installation
pspipe requires Python 3.10 or newer:
pip install pspipe
For ML-GPR:
pip install "pspipe[ml-gpr]"
Minimal workflow
After installation, create a workspace, register an observation, make its images, and convert them to visibility cubes:
mkdir pspipe-analysis && cd pspipe-analysis
psdb init nenufar /path/to/analysis-data first_run
psdb add_obs first_run.toml NIGHT_001 -m /path/to/ms_lists/NIGHT_001
psdb list_all_obs first_run.toml
pspipe image first_run.toml NIGHT_001
psdb list_rev_img first_run.toml -o NIGHT_001
pspipe gen_vis_cube first_run.toml NIGHT_001
Review the generated configuration before running: in particular the MeasurementSet data column, image and cube UV ranges, field of view, frequency bins, window, and primary beam. Inspect the FITS images and visibility cubes between stages; the separate commands above make those validation gates explicit. Once a setup is established, tasks can be chained with commas. The user guide continues from this point by loading the visibility data and producing power spectra from Python.
Metadata
Release files for pspipe 0.13
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 |
|---|---|---|---|---|
| pspipe-0.13.tar.gz | 47.0 kB | Without provenance | Details for pspipe-0.13.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pspipe-0.13-py3-none-any.whl | Python 3 | none | any | Details for pspipe-0.13-py3-none-any.whl |
Total release size: 102.8 kB
Release files / pspipe-0.13.tar.gz
| Download URL | pspipe-0.13.tar.gz |
|---|---|
| Size | 47.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
08fa0eff2b345ef7d9f84fc4f931e76f964fd63ddbc805f4b67940201ffd5c62
|
|
BLAKE2b-256 checksum How to use checksums |
844f5726f83184f93e229f4080ebbec2527f1dd1df9a0df1f7df62d7e924073c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.4.1 CPython/3.14.4 Linux/7.0.0-38-generic
|
Release files / pspipe-0.13-py3-none-any.whl
| Download URL | pspipe-0.13-py3-none-any.whl |
|---|---|
| Size | 55.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7339a93d9548fe4b1fa8913c427875584be5d05cb334eceb1b7838069fac5bb1
|
|
BLAKE2b-256 checksum How to use checksums |
cf0a8fd71507e8507114c9976986ffccbd1ce61a8fabf8aecf745898d40447bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.4.1 CPython/3.14.4 Linux/7.0.0-38-generic
|
Security for pspipe 0.13
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.