Skip to main content

lst-dl0-converter

lst-dl0-converter is a tool designed to convert LST-1 R0 data files into CTAO DL0 format. This makes it possible to analyze LST-1 data using standard CTAO software (DPPS).

Most LST commissioning data has been written as uncalibrated R0 data using an older definition of the R1 event data structure (ProtoR1).

To convert this data to DL0 compliant with the data model and the current ACADA to DPPS ICD, several steps are necessary:

  • Calibrate the waveforms applying DRS4 corrections and calibration from adc counts to photo electrons
  • Computing pixel_timeshift from DRS4 time correction and flatfielding
  • For older data: compute best event timestamp from available sources.
  • For older data: determine R1 event_type from lower level trigger bit information
  • Optional: using lstchain muon analysis results to tag muon candidate events
  • Optional: using lstchain DVR pixel selection to apply DVR. Most data still available in the onsite cluster is already data volume reduced, but not calibrated (R0V), so this step should not be necessary in most cases.
  • Write out the calibrated, tagged events to DL0 files using the directory structure and filenames as prescribed by the ACADA-DPPS ICD.

Reading the R0 data and calibrating it to R1 is handled by ctapipe_io_lst, converting the R1 to DL0 is performed by code in this repository and most of the writing is handled by the acada-mock package.

Applying the DRS4 corrections is compute intensive. For this reasons, the converter will work best when converting LST subruns in parallel to equivalent chunks. This however violates the chunking prescribed by the ACADA-DPPS ICD:

  • Files with shower candidates will not follow the event_id based chunking and will contain roughly 13000 events, that's the LST chunk size of 13250 minus the calibration events of that chunk.
  • Files with calibration events will be much smaller than the chunk size, as any given subrun will only contain hundreds of calibration events.
  • Files with the muon event candidates will be very small.

Since all LST data that needs this conversion is monoscopic LST-1 data, this does not seem to be an issue. The chunking could be made to follow the ICD in a second step, but this is currently not planned.

Finding calibration files

The converter needs several files with calibration coefficients. While the converter itself does not depend on lstchain and it is at least currently not possible to have lstchain in the same environment due to different requirements on ctapipe, this repository provides a script using lstchain to find the needed calibration files in the IT cluster and put them into a config file for the converter.

Use a separate environment with lstchain and run the script to find the files for a given run:

$ python scripts/create_config_for_run.py 11961 > config_11961.yaml

Metadata

Release files for ctao-lst-dl0-converter 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ctao-lst-dl0-converter 0.1.2
File Size Uploaded Provenance
ctao_lst_dl0_converter-0.1.2.tar.gz 26.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for ctao-lst-dl0-converter 0.1.2
File Interpreter ABI Platform
ctao_lst_dl0_converter-0.1.2-py3-none-any.whl Python 3 none any Details

Total release size: 45.0 kB

Release files / ctao_lst_dl0_converter-0.1.2.tar.gz

Download URL ctao_lst_dl0_converter-0.1.2.tar.gz
Size 26.2 kB
Tags Source
SHA-256 checksum
How to use checksums
e4585da6e4449b88adb68cbd6c5f9104b6922adf1f79a09673c38609e7b0ec4e
BLAKE2b-256 checksum
How to use checksums
b76b11488b6f2c09b0177ebd986d6f2521b96ad747c656f3618412e8b268a6fc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.12.15

Release files / ctao_lst_dl0_converter-0.1.2-py3-none-any.whl

Download URL ctao_lst_dl0_converter-0.1.2-py3-none-any.whl
Size 18.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f93ede7a2438e694b5cdc774b3cdde3a802b048ac00cb413d4ac816f3c089a07
BLAKE2b-256 checksum
How to use checksums
d23e6078258682e3b4b3c70ce9877c0fd18df7846145e358561338cce53e1e23
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.12.15

Security for ctao-lst-dl0-converter 0.1.2

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page