This release is a pre-release and may not be stable for production use.
HST/STIS Pixel-Based CTI-Correction Scripts
Utilities needed to correct for Charge Transfer Inefficiency (CTI) in the Hubble Space Telescope (HST) STIS CCD.
Scripts installed in shell:
stis_cti – Runs CTI correction on raw files, handling super-dark creation
archive_dark_query – Determines component darks needed to remake a super-dark
For more information, type:
stis_cti --help
Python usage:
import stis_cti stis_cti.stis_cti(...)
Other utilities:
stis_cti.StisPixCteCorr(…) – Code to run pixel-based CTI-correction on intermediate products
stis_cti.viable_ccd_file(…) – Test to see which FITS files on which to run the correction
stis_cti.archive_dark_query(…) – Utility to query MAST for needed component darks
See documentation at http://pythonhosted.org/stis_cti/
Release files for stis-cti 0.4-beta9
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 | |
|---|---|---|---|---|
| stis_cti-0.4-beta9.tar.gz | 1.2 MB | Without provenance | Details |
Release files / stis_cti-0.4-beta9.tar.gz
| Download URL | stis_cti-0.4-beta9.tar.gz |
|---|---|
| Size | 1.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
05b584359d904895ef4aab3706aa5fb00733e0f626dcb6bdbe73d8e6fc75d101
|
|
BLAKE2b-256 checksum How to use checksums |
011c82a29ae74128f88a2a5088e4497c9d2bc012b2093ccb75013b8dcce5f019
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for stis-cti 0.4-beta9
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.
