Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comparison with CTA-MARS: Calibration #31

Closed
4 tasks done
HealthyPear opened this issue Nov 14, 2019 · 0 comments · Fixed by #58
Closed
4 tasks done

Comparison with CTA-MARS: Calibration #31

HealthyPear opened this issue Nov 14, 2019 · 0 comments · Fixed by #58
Labels
enhancement New feature or request summary A summary of issues related to the same subject
Milestone

Comments

@HealthyPear
Copy link
Member

HealthyPear commented Nov 14, 2019

This issue is part of a project described in issue #24

The following is a "real-time" list of points that are found to be differences between the pipelines using the comparison.
Not all features are critical to recover the missing performance, but all should be implemented (as more similar as possible) in order to allow their optional use when comparing different algorithms.


  • Remove images that do not survive the preliminary image cleaning in-between the 2 passes of image extraction

Issues


Description:

  • protopipe performs calibration entirely through ctapipe,
  • in ctapipe 0.7.0 the default gain choice comes from CHEC-camera development in which there is only one channel
    • the code was set up to choose the first channel, which is the high gain one
    • as correctly reported here by @moralejo, old plots (which will be updated from the above-mentioned PR) refer to such channel,
  • also, thanks to this project, we found that in ctapipe such gain choice was done using R1-level data instead of R0 (see GainSelection should be applied to R0 waveform, not R1 ctapipe#1166)

  • missing 2nd-pass in pulse integration

Pull-Requests

Description:
explained in detail here.
As with many other features, it will be developed in parallel in the developoment version of ctapipe (and imported from there with the new release) and in protopipe (based on ctapipe 0.7 conda version)


  • Add support and apply calibscale

It should be done in ctapipe but for the moment done also here in PR #140 .

Description:
as explained here/Conversion to "photoelectrons",

the factor to transform the integrated charges (in ADC counts) into number of photoelectrons is the pixel-wise one calculated by simtelarray (0.92*LasCalData->calib[][][]).

We thus need to check if in ctapipe this value is taken into account.

@HealthyPear HealthyPear added the enhancement New feature or request label Nov 14, 2019
@HealthyPear HealthyPear added this to the Release 0.3 milestone Nov 14, 2019
@HealthyPear HealthyPear moved this from In progress to To do in Pipeline features and enhancements Jan 31, 2020
@HealthyPear HealthyPear moved this from To do to Summary issues in Pipeline features and enhancements Feb 12, 2020
@HealthyPear HealthyPear added the summary A summary of issues related to the same subject label Feb 19, 2020
Pipeline features and enhancements automation moved this from Summary issues to Done Dec 1, 2020
@HealthyPear HealthyPear changed the title Comparison with CTA-MARS: Calibration phase Comparison with CTA-MARS: Calibration Jan 22, 2021
@HealthyPear HealthyPear reopened this May 17, 2021
Pipeline features and enhancements automation moved this from Done to In progress May 17, 2021
Pipeline features and enhancements automation moved this from In progress to Done Feb 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request summary A summary of issues related to the same subject
Development

Successfully merging a pull request may close this issue.

1 participant