Skip to main content

STCAL

Documentation Status CI codecov

STScI Calibration algorithms and tools.

STCAL is intended to be used as a support package for calibration pipeline software, such as the JWST and Roman calibration pipelines. STCAL is a separate package because it is also intended to be software that can be reused by multiple calibration pipelines. Even though it is intended to be a support package for calibration pipelines, it can be installed and used as a stand alone package. This could make usage unwieldy as it is easier to use STCAL through calibration software. The main use case for stand alone installation is for development purposes, such as bug fixes and feature additions. When installing calibration pipelines that depend on STCAL this package automatically gets installed as a dependency.

Installation

The easiest way to install the latest stcal release into a fresh virtualenv or conda environment is

pip install stcal

Detailed Installation

The stcal package can be installed into a virtualenv or conda environment via pip. We recommend that for each installation you start by creating a fresh environment that only has Python installed and then install the stcal package and its dependencies into that bare environment. If using conda environments, first make sure you have a recent version of Anaconda or Miniconda installed. If desired, you can create multiple environments to allow for switching between different versions of the stcal package (e.g. a released version versus the current development version).

In all cases, the installation is generally a 3-step process:

  • Create a conda environment
  • Activate that environment
  • Install the desired version of the stcal package into that environment

Details are given below on how to do this for different types of installations, including tagged releases and development versions. Remember that all conda operations must be done from within a bash/zsh shell.

Installing latest releases

You can install the latest released version via pip. From a bash/zsh shell:

conda create -n <env_name> python
conda activate <env_name>
pip install stcal

You can also install a specific version, for example stcal 1.3.2:

conda create -n <env_name> python
conda activate <env_name>
pip install stcal==1.3.2

Installing the development version from Github

You can install the latest development version (not as well tested) from the Github master branch:

conda create -n <env_name> python
conda activate <env_name>
pip install git+https://github.com/spacetelescope/stcal

Installing for Developers

If you want to be able to work on and test the source code with the stcal package, the high-level procedure to do this is to first create a conda environment using the same procedures outlined above, but then install your personal copy of the code overtop of the original code in that environment. Again, this should be done in a separate conda environment from any existing environments that you may have already installed with released versions of the stcal package.

As usual, the first two steps are to create and activate an environment:

conda create -n <env_name> python
conda activate <env_name>

To install your own copy of the code into that environment, you first need to fork and clone the stcal repo:

cd <where you want to put the repo>
git clone https://github.com/spacetelescope/stcal
cd stcal

Note: python setup.py install and python setup.py develop commands do not work.

Install from your local checked-out copy as an "editable" install:

pip install -e .

If you want to run the unit or regression tests and/or build the docs, you can make sure those dependencies are installed too:

pip install -e ".[test]"
pip install -e ".[docs]"
pip install -e ".[test,docs]"

Need other useful packages in your development environment?

pip install ipython jupyter matplotlib pylint ipdb

Contributions and Feedback

We welcome contributions and feedback on the project. Please follow the contributing guidelines to submit an issue or a pull request.

We strive to provide a welcoming community to all of our users by abiding with the Code of Conduct.

If you have questions or concerns regarding the software, please open an issue at https://github.com/spacetelescope/stcal/issues.

Unit Tests

Unit tests can be run via pytest. Within the top level of your local stcal repo checkout:

pip install -e ".[test]"
pytest

Need to parallelize your test runs over all available cores?

pip install pytest-xdist
pytest -n auto

Metadata

Release files for stcal 1.21.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for stcal 1.21.0
File Size Uploaded Provenance Actions
stcal-1.21.0.tar.gz 933.2 kB Without provenance Details for stcal-1.21.0.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for stcal 1.21.0
File Actions
stcal-1.21.0-cp311-abi3-musllinux_1_2_x86_64.whl CPython 3.11 abi3 Linux musl 1.2+ x86-64 Details for stcal-1.21.0-cp311-abi3-musllinux_1_2_x86_64.whl
stcal-1.21.0-cp311-abi3-musllinux_1_2_aarch64.whl CPython 3.11 abi3 Linux musl 1.2+ ARM64 Details for stcal-1.21.0-cp311-abi3-musllinux_1_2_aarch64.whl
stcal-1.21.0-cp311-abi3-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 abi3 Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 Details for stcal-1.21.0-cp311-abi3-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
stcal-1.21.0-cp311-abi3-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl CPython 3.11 abi3 Linux glibc 2.28+ ARM64, Linux glibc 2.27+ ARM64 Details for stcal-1.21.0-cp311-abi3-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
stcal-1.21.0-cp311-abi3-macosx_11_0_arm64.whl CPython 3.11 abi3 macOS 11.0+ ARM64 Details for stcal-1.21.0-cp311-abi3-macosx_11_0_arm64.whl

Total release size: 14.1 MB

Release files / stcal-1.21.0.tar.gz

Download URL stcal-1.21.0.tar.gz
Size 933.2 kB
Tags Source
SHA-256 checksum
How to use checksums
5887b81f6696c0f7a6eb615f578ed769d8e923c6c49df6a553396fe2f0756ef4
BLAKE2b-256 checksum
How to use checksums
33439a27238f06387570d513800163a472c3a657fc6c74abd44b9c3f4cfd3910
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.16

Release files / stcal-1.21.0-cp311-abi3-musllinux_1_2_x86_64.whl

Download URL stcal-1.21.0-cp311-abi3-musllinux_1_2_x86_64.whl
Size 3.6 MB
Tags CPython 3.11 Linux musl 1.2+ x86-64 abi3
SHA-256 checksum
How to use checksums
5cf4a6f64a267ba95ef3ebf4c68c26efd13742dcd285d99100717f53af75e678
BLAKE2b-256 checksum
How to use checksums
94268c7689549b46de7a423d4b544998f7c73f4c3eba50472869e10bacf72f92
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.16

Release files / stcal-1.21.0-cp311-abi3-musllinux_1_2_aarch64.whl

Download URL stcal-1.21.0-cp311-abi3-musllinux_1_2_aarch64.whl
Size 3.5 MB
Tags CPython 3.11 Linux musl 1.2+ ARM64 abi3
SHA-256 checksum
How to use checksums
716bf0fa0b4c968d1951edccd9c801d07d113528dd7993abec4dccf13fb22ae8
BLAKE2b-256 checksum
How to use checksums
db275b063f0834fe1777ebdb792c0a9e2e04de141e6925f0c89f7f5089dacb6e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.16

Release files / stcal-1.21.0-cp311-abi3-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl

Download URL stcal-1.21.0-cp311-abi3-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
Size 2.6 MB
Tags CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 abi3
SHA-256 checksum
How to use checksums
23bee69dfa90e280bc304d187a4c6ec39d439df9c381d07d64f0732c1e09d220
BLAKE2b-256 checksum
How to use checksums
908f337d559ab98352b6866368c30c44f7f092a153f24db0c5e7b9af42a79884
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.16

Release files / stcal-1.21.0-cp311-abi3-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl

Download URL stcal-1.21.0-cp311-abi3-manylinux_2_27_aarch64.manylinux_2_28_aarch64.whl
Size 2.5 MB
Tags CPython 3.11 Linux glibc 2.27+ ARM64 Linux glibc 2.28+ ARM64 abi3
SHA-256 checksum
How to use checksums
f46e49fcbdb3487b786ad8a6934073c1816858ab61469071d60cbd1832a5808e
BLAKE2b-256 checksum
How to use checksums
97054a954f03c840d5ca344c1102e4b8dd5718e96a9a62a48901024c90a7027d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.16

Release files / stcal-1.21.0-cp311-abi3-macosx_11_0_arm64.whl

Download URL stcal-1.21.0-cp311-abi3-macosx_11_0_arm64.whl
Size 1.0 MB
Tags CPython 3.11 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
7a48d9f63400809939dbf0ad5e8e0b1fbc7876a5599131a79d8212595be6dc08
BLAKE2b-256 checksum
How to use checksums
68c9385a4d73ced95141916d8c6ea5367e377b1c8f8e93039a8987b97bf54100
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.16

Security for stcal 1.21.0

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.

Release history Release notifications | RSS feed

This release

1.21.0 This release

6 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page