STPSF: Simulated Point Spread Functions for the James Webb and Nancy Grace Roman Space Telescopes
STPSF HAS BEEN MIGRATED FROM WEBBPSF
STPSF produces simulated PSFs for the James Webb Space Telescope, NASA’s flagship infrared space telescope. STPSF can simulate images for any of the four science instruments plus the fine guidance sensor, including both direct imaging, coronagraphic, and spectroscopic modes.
STPSF also supports simulating PSFs for the upcoming Nancy Grace Roman Space Telescope (formerly WFIRST), including its Wide Field Instrument and a preliminary version of the Coronagraph Instrument.
Documentation can be found online at https://stpsf.readthedocs.io
STPSF requires input data for its simulations, including optical path difference (OPD) maps, filter transmission curves, and coronagraph Lyot mask shapes. These data files are not included in this source distribution. Please see the documentation to download the required data files.
3 maintainers
Metadata
3 maintainers
Release files for stpsf 2.3.1
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 |
|---|---|---|---|---|
| stpsf-2.3.1.tar.gz | 74.6 MB | With provenance | Details for stpsf-2.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| stpsf-2.3.1-py3-none-any.whl | Python 3 | none | any | Details for stpsf-2.3.1-py3-none-any.whl |
Total release size: 75.8 MB
Release files / stpsf-2.3.1.tar.gz
| Download URL | stpsf-2.3.1.tar.gz |
|---|---|
| Size | 74.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
58396ca822597b363a3d042dffbd1d44673a7104a0b7a13c85cbc527b3b94572
|
|
BLAKE2b-256 checksum How to use checksums |
e78f0346503fb962a8bd25fe0fc562a23e24d24c11331065c280b78e758c7186
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 11, 2026.
Transparency logRelease files / stpsf-2.3.1-py3-none-any.whl
| Download URL | stpsf-2.3.1-py3-none-any.whl |
|---|---|
| Size | 1.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
473dfb6f56fcd4933f082b747fd0118331a825d93623a9f3ce07f0f286fa68c9
|
|
BLAKE2b-256 checksum How to use checksums |
61261aa2e8969771e07ade1250bd2e1d95ea9767f95c6c7151cea457eeb4d659
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 11, 2026.
Transparency logSecurity for stpsf 2.3.1
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for stpsf-2.3.1.tar.gz
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 Nov 11, 2026.
Transparency logA 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.
