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

Adapt the pixel_status to the change on the R1 format #68

Merged
merged 1 commit into from
Mar 4, 2025

Conversation

vmarandon
Copy link
Contributor

According to A.1.5 section of the R1 CTA format, the pixel status contains:

  • bit 0 and 1 : DVR Info
  • bit 2 and 3 : channel info
  • bit 4 : saturation
  • bit 5, 6 and 7 : pixel trigger info.

The previous version of the code was assigning the hardware_failing_pixel at True in the pixel_status of the mon object only in the case : pixel_status == 0.
Nevertheless according to change request : CTA-CRE-ACA-303000-0038, R1 format out of the camera should always put the DVR info at 1, and so on the test does not work anymore.

The proposed changed will use only bit 2 and 3 for the comparison. According to the documentation, if the channel info is 0, then pixel if off/broken/missing.

@vmarandon vmarandon requested review from jlenain and frnbrun March 3, 2025 20:52
@vmarandon vmarandon self-assigned this Mar 3, 2025
Copy link

codecov bot commented Mar 3, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.43%. Comparing base (31f990f) to head (4da6129).
Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #68   +/-   ##
=======================================
  Coverage   85.43%   85.43%           
=======================================
  Files           7        7           
  Lines         934      934           
=======================================
  Hits          798      798           
  Misses        136      136           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

@frnbrun frnbrun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the modifications to the code. Looks good to me!

Copy link
Contributor

@jlenain jlenain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot for that ! Would you have a reference for this change request ? I am not really sure to understand what we are talking about.

@sizun
Copy link
Contributor

sizun commented Mar 4, 2025

The CRE reference is CTA-CRE-ACA-303000-0038.
It was discussed here: https://gitlab.cta-observatory.org/cta-computing/common/acada-array-elements/acada_lst1_int/-/issues/146#note_161626

@jlenain
Copy link
Contributor

jlenain commented Mar 4, 2025

The CRE reference is CTA-CRE-ACA-303000-0038. It was discussed here: https://gitlab.cta-observatory.org/cta-computing/common/acada-array-elements/acada_lst1_int/-/issues/146#note_161626

Thanks a lot, @sizun !

@jlenain jlenain merged commit 68479e4 into cta-observatory:main Mar 4, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants