psimager
Fast dirty imaging of measurement sets for power spectrum analyses: dirty Stokes and PSF images with the ducc0 w-gridder, with the options, file names and FITS keywords of WSClean, so that pspipe and ps_eor read them as WSClean images.
The MSs are read once, in large row chunks, and the output channels are gridded in parallel, each by one ducc0 call. Imaging many channels is then many times faster than with WSClean, which reorders the data on disk and grids one image at a time.
Installation
pip install psimager
Usage
psimager -name img -size 400 400 -scale 6amin -pol IV -channels-out 363 -weight natural \
-minuv-l 5 -maxuv-l 100 -data-column CORRECTED_DATA -even-odd -make-psf -no-dirty obs*.MS
writes img-even-0000-I-image.fits, img-even-0000-V-image.fits, img-even-0000-psf.fits, ...,
for each output channel, for the even and the odd time steps.
Options
As WSClean's: -name, -data-column, -pol, -size, -scale, -channel-range,
-channels-out, -interval, -intervals-out, -even-timesteps, -odd-timesteps, -minuv-l,
-maxuv-l, -minuvw-m, -maxuvw-m, -weight natural|uniform|briggs ROBUST,
-visibility-weighting-mode, -taper-edge, -padding (of the weighting grid),
-wgridder-accuracy, -j, -parallel-gridding, -mem, -abs-mem, -make-psf, -no-dirty.
See psimager --help.
Differences with WSClean:
-even-oddimages the even and the odd time steps in one pass, asNAME-even-*andNAME-odd-*.-fits-keyword KEY=VALUE(repeatable) adds a header keyword to every output file, written with the file instead of updating it afterwards.-parallel-griddingdefaults to-j: one thread per output channel, which is the fastest.- No deconvolution and no
-MFS-images. - WSClean's gridding options (
-oversampling,-kernel-size,-nwlayers,-grid-mode,-reorder,-temp-dir, ...) are accepted and ignored, with a warning, so that a WSClean command line runs unchanged. - Only single-field, single-SPW MSs with linear correlations.
The data are read in chunks of at most 30 GB by default (-abs-mem), or -mem % (33) of the
node's memory if smaller, so that several psimager runs can share a node, e.g. as job steps of
a Slurm allocation; give -abs-mem to use more on a node of its own.
Images are in Jy/PSF (the PSF peaks at 1), one file per output channel and Stokes parameter, with
WSClean's WSCNVIS, WSCENVIS, WSCVWSUM, WSCIMGWG and WSCNORMF computed from the Stokes I
weights, and BMAJ, BMIN, BPA fitted to the PSF.
Metadata
Release files for psimager 0.3
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 |
|---|---|---|---|---|
| psimager-0.3.tar.gz | 26.2 kB | Without provenance | Details for psimager-0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| psimager-0.3-py3-none-any.whl | Python 3 | none | any | Details for psimager-0.3-py3-none-any.whl |
Total release size: 53.3 kB
Release files / psimager-0.3.tar.gz
| Download URL | psimager-0.3.tar.gz |
|---|---|
| Size | 26.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
feeb047f3623f1acdeb3ab9eb7c29b93f4479cec0821e11f02355ddfa404478c
|
|
BLAKE2b-256 checksum How to use checksums |
87c9770ae2be84372b81be897c9ea3a0077184715a0b0c31aa67b3e9837becb3
|
| 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 / psimager-0.3-py3-none-any.whl
| Download URL | psimager-0.3-py3-none-any.whl |
|---|---|
| Size | 27.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
489a03b81c8de8f1dcbfec959bb38d90b3c2ceef5e7ce02ba67c74070ef91aa4
|
|
BLAKE2b-256 checksum How to use checksums |
fda467ce9ae487e686f4a9dd8de53fc06181a763478ac62292a566e2ab817594
|
| 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 psimager 0.3
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.