Skip to content

Conversation

@asanchezcastillo
Copy link
Contributor

@asanchezcastillo asanchezcastillo commented Jan 20, 2026

Description

This PR fixes a minor bug on the light propagation correction module spotted by @henrylay97. Previously, the minimum of VIS and VUV light propagation time was assigned to both coated and uncoated channels. Now uncoated channels always receive the VIS light propagation time. The impact of the bug was expected to be minimal since uncoated channels hardly every contribute to the OpFlash timing estimation.

$${\color{red}!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!}$$

$${\color{red}\bf{\textrm{IMPORTANT UPDATE June 22nd 2025:}}}$$ If you are making a PR which is intended as a patch for the CURRENT production (which started in Spring 2025), you must make two PRs: one for develop and one for the production/v10_06_00 branch.

$${\color{red}!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!}$$

Checklist

  • Added at least 1 label from available labels.
  • Assigned at least 1 reviewer under Reviewers,
  • Assigned all contributers including yourself under Assignees
  • Linked any relevant issues under Developement
  • Does this PR affect CAF data format? If so, please assign a CAF maintainer (PetrilloAtWork or JosiePaton) as additional reviewer.
  • Does this affect the standard workflow?
  • Is this PR a patch for the ongoing production? If so, separate PR must also be made for production/v10_06_00 branch!

Relevant PR links (optional)

Does this PR require merging another PR in a different repository (such as sbnanobj/sbnobj etc.)?

Link(s) to docdb describing changes (optional)

Is there a docdb describing the issue this solves or the feature added?

@asanchezcastillo asanchezcastillo self-assigned this Jan 20, 2026
@asanchezcastillo asanchezcastillo added the bug Something isn't working label Jan 20, 2026
Copy link
Member

@henrylay97 henrylay97 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 acting so quick Alejandro. Just a couple of queries before I wave this through :D

Comment on lines +39 to +43
if(fPDSMap.pdType(opch)=="pmt_coated") fOpDetType.push_back(0);
else if(fPDSMap.pdType(opch)=="pmt_uncoated") fOpDetType.push_back(1);
else if(fPDSMap.pdType(opch)=="xarapuca_vuv") fOpDetType.push_back(2);
else if(fPDSMap.pdType(opch)=="xarapuca_vis") fOpDetType.push_back(3);
else fOpDetType.push_back(-1);
Copy link
Member

Choose a reason for hiding this comment

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

A couple of questions:

  1. Given this is only used in one place, is it worth having this vector? Could just have the if statements directly query the fPDSMap.pdType.
  2. If you are keeping the vector setup, is it worth defining the numbers as an enum in the header file?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

Status: Waiting on Reviewer

Development

Successfully merging this pull request may close these issues.

3 participants