rail_delight
Delight-based stages for RAIL.
This is a hybrid approach that uses both the physics of SEDs and machine learning to produce photometric redshift estimates.
Note when installing, it may fail to build delight. You may need to build delight by hand.
RAIL: Redshift Assessment Infrastructure Layers
RAIL is a flexible software library providing tools to produce at-scale photometric redshift data products, including uncertainties and summary statistics, and stress-test them under realistically complex systematics. A detailed description of RAIL's modular structure is available in the Overview on ReadTheDocs.
RAIL serves as the infrastructure supporting many extragalactic applications of the Legacy Survey of Space and Time (LSST) on the Vera C. Rubin Observatory, including Rubin-wide commissioning activities. RAIL was initiated by the Photometric Redshifts (PZ) Working Group (WG) of the LSST Dark Energy Science Collaboration (DESC) as a result of the lessons learned from the Data Challenge 1 (DC1) experiment to enable the PZ WG Deliverables in the LSST-DESC Science Roadmap (see Sec. 5.18), aiming to guide the selection and implementation of redshift estimators in DESC analysis pipelines. RAIL is developed and maintained by a diverse team comprising DESC Pipeline Scientists (PSs), international in-kind contributors, LSST Interdisciplinary Collaboration for Computing (LINCC) Frameworks software engineers, and other volunteers, but all are welcome to join the team regardless of LSST data rights.
Installation
Installation instructions are available under Installation on ReadTheDocs.
Contributing
The greatest strength of RAIL is its extensibility; those interested in contributing to RAIL should start by consulting the Contributing guidelines on ReadTheDocs.
Citing RAIL
RAIL is open source and may be used according to the terms of its LICENSE (BSD 3-Clause). If you make use of the ideas or software here in any publication, you must cite this repository https://github.com/LSSTDESC/RAIL as "LSST-DESC PZ WG (in prep)" with the Zenodo DOI. Please consider also inviting the developers as co-authors on publications resulting from your use of RAIL by making an issue. Additionally, several of the codes accessible through the RAIL ecosystem must be cited if used in a publication. A convenient list of what to cite may be found under Citing RAIL on ReadTheDocs.
2 maintainers
Metadata
2 maintainers
Release files for pz-rail-delight 1.1.0
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_delight-1.1.0.tar.gz | 566.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pz_rail_delight-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.1 MB
Release files / pz_rail_delight-1.1.0.tar.gz
| Download URL | pz_rail_delight-1.1.0.tar.gz |
|---|---|
| Size | 566.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cab6acc15267c7f262b6579be30007d73d969949cda7a3b8142cedc179198a6a
|
|
BLAKE2b-256 checksum How to use checksums |
5106d60e81b9e1c4f2a456f9d74beaad4f44b6379b44b6f78adc0a5930e09121
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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 Feb 10, 2025.
Transparency logRelease files / pz_rail_delight-1.1.0-py3-none-any.whl
| Download URL | pz_rail_delight-1.1.0-py3-none-any.whl |
|---|---|
| Size | 551.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1d4f3d9e63a6411a84912a0c4a6fef0d27a7232a0b7b8f882f654f3d735fb929
|
|
BLAKE2b-256 checksum How to use checksums |
b4db4a998f8607c9602b3ee9e42cc9049232a682b15ded16497abdcf9093101a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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 Feb 10, 2025.
Transparency logSecurity for pz-rail-delight 1.1.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pz_rail_delight-1.1.0.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 Feb 10, 2025.
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.
