pz-rail-pipelines
TODO List
To ensure that your project and repository is stable from the very start there are a few todo items that you should take care of. Unfortunately the RAIL project template can not do these for you, otherwise it would :)
Immediate actions
- In your repository settings:
- Grant the
LSSTDESC/rail_admingroup administrator access - Grant the
LSSTDESC/photo-zgroup maintainer access
- Grant the
- Configure Codecov for the repository
- Go here, https://github.com/apps/codecov, click the "Configure" button
- Log in to PyPI.org and configure Trusted Publishing following these instructions https://docs.pypi.org/trusted-publishers/creating-a-project-through-oidc/
- Create a Personal Access Token (PAT) to automatically add issues to the RAIL project tracker
- Follow these instruction to create a PAT: https://github.com/actions/add-to-project#creating-a-pat-and-adding-it-to-your-repository
- Save your new PAT as a repository secret named
ADD_TO_PROJECT_PAT
Before including in Rail-hub
- Make sure your
mainbranch is protected - Update this README
- Create an example notebook
- Run
pylinton your code - Remove this TODO list once all items are completed
RAIL: Redshift Assessment Infrastructure Layers
This package is part of the larger ecosystem of Photometric Redshifts in RAIL.
Citing RAIL
This code, while public on GitHub, has not yet been released by DESC and is still under active development. Our release of v1.0 will be accompanied by a journal paper describing the development and validation of RAIL.
If you make use of the ideas or software in RAIL, please cite the repository https://github.com/LSSTDESC/RAIL. You are welcome to re-use the code, which is open source and available under terms consistent with the MIT license.
External contributors and DESC members wishing to use RAIL for non-DESC projects should consult with the Photometric Redshifts (PZ) Working Group conveners, ideally before the work has started, but definitely before any publication or posting of the work to the arXiv.
Citing this package
If you use this package, you should also cite the appropriate papers for each code used. A list of such codes is included in the Citing RAIL section of the main RAIL Read The Docs page.
2 maintainers
Metadata
2 maintainers
Release files for pz-rail-pipelines 2.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pz_rail_pipelines-2.0.2.tar.gz | 26.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pz_rail_pipelines-2.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.7 kB
Release files / pz_rail_pipelines-2.0.2.tar.gz
| Download URL | pz_rail_pipelines-2.0.2.tar.gz |
|---|---|
| Size | 26.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b86063020a98458e51bb8ed8bfd8b3138ed03c9f04440c7a0032e97cece9b98f
|
|
BLAKE2b-256 checksum How to use checksums |
3c7edfc87e12b7c3c170ece893eeade5f2374ab12b928c259eb886eb42692f38
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 18, 2026.
Transparency logRelease files / pz_rail_pipelines-2.0.2-py3-none-any.whl
| Download URL | pz_rail_pipelines-2.0.2-py3-none-any.whl |
|---|---|
| Size | 13.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7c28bf425db5952e14005a0b7cbd47911a04462032f00d222d7475fd464a4e99
|
|
BLAKE2b-256 checksum How to use checksums |
204305e0cc10b7df40079cda6a9b0c46802b6aad57e1aa9f738da31964971d5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 18, 2026.
Transparency log
