Pipeline Releases
Note
A working conda installation (Miniconda, Mamba, Anaconda, etc.) is required (see Install Conda).
Warning
stenv does not support Python 2.
Warning
stenv does not support 32-bit operating systems.
Pipeline releases differ from the standard software stack and serve a different purpose.
The release files, described below, are immutable snapshots of STScI operational software and can be used to replicate the environment used by STScI to perform mission-specific data processing.
Be aware that upgrading packages with conda update is not recommended, as it will likely introduce unwanted bugs and / or break the environment all together.
Installation
Pipeline release installations use the following conda create command format:
conda create -n demo_2016.1 --file http://ssb.stsci.edu/releases/hstdp/2016.1/hstdp-2016.1-linux-py35.0.txt
conda activate demo_2016.1
Warning
The URL shown in this example does not reflect the latest iteration available. Please consult the File URLs section to ensure you are installing the correct release.
File URLs
Select the URL that matches your intended platform and environment.
HST Data Processing (HSTDP)
HSTDP was previously known as OPUS.
Instructions for installation of each delivery may be found in the respective subdirectories of the releases repository: https://github.com/astroconda/astroconda-releases/tree/master/caldp
Warning
The repository is located within the Astroconda GitHub organization for legacy reasons. Astroconda is no longer supported as of February 1st, 2023.
20221010
20220527
20220406
20220214
20220127
20211129
20211119
20210928
20210827
20210721
20210505
20210415
20210323
20201208
20201012
20200812
20200708
20200611
20200421
20200323
Historical deliveries used an older naming convention: https://github.com/astroconda/astroconda-releases/tree/master/hstdp
2019.5.2
2019.5.1
2019.5
2019.4
2019.3c
2019.3b
2019.3a
2019.3
2019.2
2018.3a
2018.3
2018.1
2017.3
2017.2a
2017.2
2017.1
2016.2
2016.1
Continuous Integration
This example BASH function provides a starting point for users intending to execute pipeline software from within a continuous integration environment. This installation method is unsupported and your mileage may vary. Use at your own risk.
function get_pipeline()
{
# Do we have enough arguments?
if [[ $# < 3 ]]; then
echo "Not enough arguments."
return 1
fi
# Setup basic argument list & Example Input(s)
local conda_env="$1" # hst_env
local name="$2" # hstdp, ...
local build="$3" # 2017.2, 2016.2 ...
local python_version="$4" # py[35, 27, ...]
local iteration="$5" # final | post[0, 1, 2, ...]
# Detect platform
local _platform=$(uname -s)
local platform=""
# Convert platform string to match file naming convention
if [[ ${_platform} == Linux ]]; then
platform="linux"
elif [[ ${_platform} == Darwin ]]; then
platform="osx"
else
echo "Unsupported platform: ${_platform}"
return 1
fi
unset _platform
# Handle optional arguments.
if [[ -z ${python_version} ]]; then
# Notice the "py" prefix and condensed version here
python_version="py35"
fi
if [[ -z ${iteration} ]]; then
iteration="final"
fi
# Assemble pipeline spec file URL
local ac_root="http://ssb.stsci.edu/releases"
local ac_base="${ac_root}/${name}/${build}"
local ac_spec="${name}-${build}-${platform}-${python_version}.${iteration}.txt"
local ac_url="${ac_base}/${ac_spec}"
# Perform installation
conda create -q -n "${conda_env}" --file "${ac_url}"
return $?
}
#
# Usage example:
#
# Silently generate a pipeline environment called "hst_env"
get_pipeline hst_env hstdp 2017.2
# Enter environment
source activate hst_env
# ... do work ...
# EOF