ALDERAAN
Automated Lightcurve Detrending, Exoplanet Recovery, and Analysis of Autocorrelated Noise
ALDERAAN is a fast and reliable pipeline for processing exoplanet transit photometry. The pipeline is currently capable of handling data from the Kepler Space Telescope, but in the near future will be extended to handle data from K2 and TESS.
Detrending and transit fitting are optimized for high-fidelity measurements of [P, t0, Rp/Rs, b, T14] and for inference of dynamical transit timing variations (TTVs). Noise arising from instrumental and astrophysical sources is handled using a combination of Gaussian Processes (GP) regression and autocorrelated frequency analysis. Model sampling is performed using dynamic nested sampling.
For detailed documentation, see readthedocs.org
Installation instructions
ALDERAAN requires a complex set of dependencies in order to run. To create a conda environment capable of running the ALDERAAN pipeline, copy environment.yml from the alderaan github repository to your local machine:
curl -o ./environment.yml https://raw.githubusercontent.comefs/heads/develop/environment.yml
Then run:
conda env create -n <ENV_NAME> -f environment.yml
If <ENV_NAME> is not specified, the conda environment will be named "alderaan-env".
You can then activate your environment and safely pip install the package:
conda activate alderaan-env
then
pip install alderaan
Running the pipeline
To run the pipeline, navigate into the alderaan source directory and run the following commmand:
python alderaan/pipelines/alderaan_pipeline.py -m Kepler -t K00148 -c configs/default_config.cfg
The flags -m (mission) -t (target) and -c (config) are required and set the pipeline run conditions.
Attribution
If you make use of alderaan in your work, please cite Gilbert, Petigura, & Entrican (2025).
Please also cite the following core dependencies:
astropyAstropy Collaboration et al. (2022)batmanKreidberg (2015)celeriteForeman-Mackey 2018dynestySpeagle (2020)numpyHarris et al, (2020)PyMC3Salvatier, Wiecki, & Fonnesbeck (2016)scipyVirtanen et al. (2020)
Metadata
Release files for alderaan 0.2.3
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 | Actions |
|---|---|---|---|---|
| alderaan-0.2.3.tar.gz | 109.9 kB | Without provenance | Details for alderaan-0.2.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| alderaan-0.2.3-py3-none-any.whl | Python 3 | none | any | Details for alderaan-0.2.3-py3-none-any.whl |
Total release size: 238.0 kB
Release files / alderaan-0.2.3.tar.gz
| Download URL | alderaan-0.2.3.tar.gz |
|---|---|
| Size | 109.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fe4b7cec245fae98ca024dcfb81b96891266ff984b18ea4865b1777cbc9a8fdf
|
|
BLAKE2b-256 checksum How to use checksums |
c4d436bb61cb0cbe66fa1286b06697a6eee9f17c20ef11feb854b8054dbbf5a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.23
|
Release files / alderaan-0.2.3-py3-none-any.whl
| Download URL | alderaan-0.2.3-py3-none-any.whl |
|---|---|
| Size | 128.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6e15af3a5f386136d30ceab615d0cab6ab0b0a597bb206f93c0e439b5932140c
|
|
BLAKE2b-256 checksum How to use checksums |
93c236fb7c7271989245b47804a8527d0b243c047d06665060de2046c38c1210
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.23
|
Security for alderaan 0.2.3
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.