Skip to content

Latest commit

 

History

History
112 lines (80 loc) · 4.64 KB

README.md

File metadata and controls

112 lines (80 loc) · 4.64 KB
Raw

cta-lstchain Build Status DOI PyPI version Conda version

Repository for the low-level analysis of the LST up to DL3 level. The analysis is heavily based on ctapipe, adding custom code for mono reconstruction. Higher-level analysis starting from DL3 can be performed with Gammapy.

Note that notebooks are currently not tested and not guaranteed to be up-to-date.
In doubt, refer to tested code and scripts: basic functions of lstchain (reduction steps R0-->DL1, DL1-->DL2 and DL2-->DL3) are unit-tested and should be working as long as the build status is passing.

Install

You will need to install mamba/miniforge (recommended) or miniconda first.

As user

You can create an environment and install lstchain from conda-forge as:

mamba create -c conda-forge -n lstchain-v0.10.7 python=3.11 lstchain=0.10.7

Alternatively, you can also install lstchain from PyPi with pip:

LSTCHAIN_VER=0.10.7  (or the version you want to install - usually the latest release)
wget https://raw.githubusercontent.com/cta-observatory/cta-lstchain/v$LSTCHAIN_VER/environment.yml
conda env create -n lst -f environment.yml
conda activate lst
pip install lstchain==$LSTCHAIN_VER
rm environment.yml

As developer

  • Create and activate the conda environment:
git clone https://github.com/cta-observatory/cta-lstchain.git
cd cta-lstchain
conda env create -f environment.yml
conda activate lst-dev

Note: To prevent packages you installed with pip install --user from taking precedence over the conda environment, run:

conda env config vars set PYTHONNOUSERSITE=1 -n <environment_name>

To update the environment (e.g. when dependencies got updated), use:

conda env update -n lst-dev -f environment.yml
  • Install lstchain in developer mode:
pip install -e .

To run some of the tests, some non-public test data files are needed. These tests will not be run locally if the test data is not available, but are always run in the CI.

To download the test files locally, run ./download_test_data.sh. It will ask for username and password and requires wget to be installed. Ask one of the project maintainers for the credentials. If you are a member of the LST collaboration you can also obtain them here:

https://ctaoobservatory.sharepoint.com/:i:/r/sites/ctan-onsite-it/Shared%20Documents/General/information_2.jpg?csf=1&web=1&e=suUkV6

To run the tests that need those private data files, add -m private_data to the pytest call, e.g.:

pytest -m private_data -v lstchain

To run all tests, run

pytest -m 'private_data or not private_data' -v lstchain

Contributing

All contributions are welcomed.

Guidelines are the same as ctapipe's ones. See here for the general guidelines on how to make a pull request to contribute to the repository. Since the addition of the private data, the CI tests for Pull Requests from forks are not working, therefore we would like to ask you to push your modified branches directly to the main cta-lstchain repo. If you do not have writing permissions in the repo, please contact one of the main developers.

Report issue / Ask a question

Use GitHub Issues.

Cite

If you use lstchain in a publication, please cite the exact version you used from Zenodo Cite as, see https://doi.org/10.5281/zenodo.6344673

Please also cite the following proceedings by adding the bibtex entry:

@inproceedings{lstchain_adass_2020,
    author = "L\'opez-Coto, Rub\'en and others",
    collaboration = "CTA, LST Project",
    title = "{lstchain: An Analysis Pipeline for LST-1, the First Prototype Large-Sized Telescope of CTA}",
    journal = "ASP Conf. Ser.",
    volume = "532",
    pages = "357",
    year = "2022"
}