Skip to content

Fix issue where CRT HitTree in calibration tuples did not store run number [Develop]#861

Open
francescopoppi wants to merge 2 commits intodevelopfrom
feature/fp_fixCRTHit_CRTDataAnalysis_develop
Open

Fix issue where CRT HitTree in calibration tuples did not store run number [Develop]#861
francescopoppi wants to merge 2 commits intodevelopfrom
feature/fp_fixCRTHit_CRTDataAnalysis_develop

Conversation

@francescopoppi
Copy link
Copy Markdown
Contributor

[Develop Version]
This PR fixes a bug where due to the fact CRTData were dropped from Stage0, running Stage1 did not fill run number and sub run number. This caused the usage of uninitialized variables. This error was spotted thanks to @mt82 who did consistency checks between productions.
On a side note, I cleaned the code from some bad indentation that made the code unreadable.
I also added Trigger Timestamp to the DAQTree, it should have been there since the beginning.

@francescopoppi francescopoppi self-assigned this Oct 28, 2025
@francescopoppi francescopoppi added the bug Something isn't working label Oct 28, 2025
@jas1005
Copy link
Copy Markdown
Contributor

jas1005 commented Apr 3, 2026

@aheggest

I'm going through old PRs and it looks like this one never got approved. I realize the number of changes isn't trivial, but I hope your relative familiarity with the code will make things easier. Do you have time to review this PR or should I ask someone else? Would you like me to ask someone else to also review this PR?

Copy link
Copy Markdown
Contributor

@aheggest aheggest left a comment

Choose a reason for hiding this comment

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

I approve these changes.

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

None yet

Development

Successfully merging this pull request may close these issues.

3 participants