pz-rail-lephare
RAIL LePHARE
This package allows users to run the LePHARE code through RAIL. It can be installed via pip with the following command. Full documentation is available at the main LePHARE documentation.
pip install pz-rail-lephare
RAIL: Redshift Assessment Infrastructure Layers
This package is part of the larger ecosystem of Photometric Redshifts in RAIL. This package in particular is concerned with wrapping the LePHARE template fitting code within RAIL.
Developer installation
This package can be installed from source using the following commands to allow working on the code.
git clone https://github.com/LSSTDESC/rail_lephare.git
cd rail_lephare
conda install -c conda-forge pytables
pip install -e '.[dev]'
Citing RAIL
RAIL is open source and may be used according to the terms of its LICENSE (BSD 3-Clause). If you used RAIL in your study, please cite this repository https://github.com/LSSTDESC/RAIL, and RAIL Team et al. (2025) https://arxiv.org/abs/2505.02928
@ARTICLE{2025arXiv250502928T,
author = {{The RAIL Team} and {van den Busch}, Jan Luca and {Charles}, Eric and {Cohen-Tanugi}, Johann and {Crafford}, Alice and {Crenshaw}, John Franklin and {Dagoret}, Sylvie and {De-Santiago}, Josue and {De Vicente}, Juan and {Hang}, Qianjun and {Joachimi}, Benjamin and {Joudaki}, Shahab and {Bryce Kalmbach}, J. and {Kannawadi}, Arun and {Liang}, Shuang and {Lynn}, Olivia and {Malz}, Alex I. and {Mandelbaum}, Rachel and {Merz}, Grant and {Moskowitz}, Irene and {Oldag}, Drew and {Ruiz-Zapatero}, Jaime and {Rahman}, Mubdi and {Rau}, Markus M. and {Schmidt}, Samuel J. and {Scora}, Jennifer and {Shirley}, Raphael and {St{\"o}lzner}, Benjamin and {Toribio San Cipriano}, Laura and {Tortorelli}, Luca and {Yan}, Ziang and {Zhang}, Tianqing and {the Dark Energy Science Collaboration}},
title = "{Redshift Assessment Infrastructure Layers (RAIL): Rubin-era photometric redshift stress-testing and at-scale production}",
journal = {arXiv e-prints},
keywords = {Instrumentation and Methods for Astrophysics, Cosmology and Nongalactic Astrophysics, Astrophysics of Galaxies},
year = 2025,
month = may,
eid = {arXiv:2505.02928},
pages = {arXiv:2505.02928},
doi = {10.48550/arXiv.2505.02928},
archivePrefix = {arXiv},
eprint = {2505.02928},
primaryClass = {astro-ph.IM},
adsurl = {https://ui.adsabs.harvard.edu/abs/2025arXiv250502928T},
adsnote = {Provided by the SAO/NASA Astrophysics Data System}
}
Please consider also inviting the developers as co-authors on publications resulting from your use of RAIL by making an issue. A convenient list of what to cite may be found under Citing RAIL on ReadTheDocs. Additionally, several of the codes accessible through the RAIL ecosystem must be cited if used in a publication.
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.
Metadata
Release files for pz-rail-lephare 2.0.4
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 | |
|---|---|---|---|---|
| pz_rail_lephare-2.0.4.tar.gz | 324.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pz_rail_lephare-2.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 336.3 kB
Release files / pz_rail_lephare-2.0.4.tar.gz
| Download URL | pz_rail_lephare-2.0.4.tar.gz |
|---|---|
| Size | 324.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
079d6cb69137808aa7790a227cf1b48eed8c63b87175298ae5a109bacc3b8ad8
|
|
BLAKE2b-256 checksum How to use checksums |
ffd4637ff22f458bd3b8a385e60ba65bedbce091126682331151a5d2e6d1627f
|
| 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 25, 2026.
Transparency logRelease files / pz_rail_lephare-2.0.4-py3-none-any.whl
| Download URL | pz_rail_lephare-2.0.4-py3-none-any.whl |
|---|---|
| Size | 11.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bb572ab1c182df60be71ed7d7b21186620efd4757689b296d244f57d081ab8ad
|
|
BLAKE2b-256 checksum How to use checksums |
d6f6d62eef32258d999c200a88838567727fb7644f3f8287b6ec0be9d844a5ee
|
| 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 25, 2026.
Transparency logSecurity for pz-rail-lephare 2.0.4
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pz_rail_lephare-2.0.4.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 Jun 25, 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.