Skip to content

Conversation

@ftouchte
Copy link
Collaborator

Feature:

  • compute leadingEdgeTime even if the type is bad (the cut on the type can be done at the analysis level)
  • if time < 0, set the distance to be 0
  • use the time2distance from simulation

Copy link
Collaborator

@baltzell baltzell left a comment

Choose a reason for hiding this comment

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

Looks like this adds another feature to AHDC's "sim" mode, doing things differently for real/fake data, based on the user's configuration file.

@c-dilks c-dilks enabled auto-merge (squash) September 2, 2025 14:26
@c-dilks c-dilks merged commit b08ee20 into JeffersonLab:development Sep 2, 2025
32 checks passed
c-dilks pushed a commit that referenced this pull request Sep 15, 2025
…(clas12Tags) (#805)

* use a specific time to distance for simulation and if time < 0 then distance is 0

* compute leadingEdgeTime even if the type may seem bad
tongtongcao pushed a commit that referenced this pull request Sep 22, 2025
…(clas12Tags) (#805)

* use a specific time to distance for simulation and if time < 0 then distance is 0

* compute leadingEdgeTime even if the type may seem bad
@ftouchte ftouchte deleted the recon/simu branch October 3, 2025 08:47
tongtongcao pushed a commit that referenced this pull request Nov 18, 2025
…(clas12Tags) (#805)

* use a specific time to distance for simulation and if time < 0 then distance is 0

* compute leadingEdgeTime even if the type may seem bad
tongtongcao pushed a commit that referenced this pull request Nov 21, 2025
…(clas12Tags) (#805)

* use a specific time to distance for simulation and if time < 0 then distance is 0

* compute leadingEdgeTime even if the type may seem bad
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.

3 participants