-
Notifications
You must be signed in to change notification settings - Fork 31
Use pixel-style MPDG readout for tracking until efficiency issues are resolved #1819
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
Conversation
Hello, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fine with me.
I was about to do the very same modification to revert to pixel-style MPGDs.
Can we add this plot as a benchmark? |
Yes, definitely. We discussed the need for this last Thurday. |
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin v1.24
git worktree add -d .worktree/backport-1819-to-v1.24 origin/v1.24
cd .worktree/backport-1819-to-v1.24
git switch --create backport-1819-to-v1.24
git cherry-pick -x b2d08908cecb1fb812afc1f240cb1289620f83a6 |
… resolved (#1819) As presented in the tracking WG meeting ([https://indico.bnl.gov/event/27589/contributions/105659/attachments/60986/104773/tracking1_040325.pdf](https://indico.bnl.gov/event/27589/contributions/105659/attachments/60986/104773/tracking1_040325.pdf)), the updated 2D MPGD digitization leads to inefficiencies for the Barrel MPGD. This PR restores the previous digitization scheme as the default, where the hits are used in the track reconstruction with high efficiency. Once the 2D readout can demonstrate comparable results, we will switch over. Results with 2D digitization: <img width="647" alt="image1" src="https://github.com/user-attachments/assets/5785ed7a-faa3-44d7-a8ba-b566edde82b8" /> Results with pixel-style (SVT-like) digitization: <img width="653" alt="image2" src="https://github.com/user-attachments/assets/217d8ae4-7d7f-4a65-9b49-ce1b6a5bc4a7" /> - [ ] Bug fix (issue #__) - [ ] New feature (issue #__) - [ ] Documentation update - [ ] Other: __ - [x] Tests for the changes have been added - [ ] Documentation has been added / updated - [x] Changes have been communicated to collaborators @ShujieL @ybedfer need to make to their code? No Yes, it restores previous barrel MPGD digitization scheme as default. (cherry picked from commit b2d0890)
Capybara summary for PR 1819
|
… resolved (#1819) As presented in the tracking WG meeting ([https://indico.bnl.gov/event/27589/contributions/105659/attachments/60986/104773/tracking1_040325.pdf](https://indico.bnl.gov/event/27589/contributions/105659/attachments/60986/104773/tracking1_040325.pdf)), the updated 2D MPGD digitization leads to inefficiencies for the Barrel MPGD. This PR restores the previous digitization scheme as the default, where the hits are used in the track reconstruction with high efficiency. Once the 2D readout can demonstrate comparable results, we will switch over. Results with 2D digitization: <img width="647" alt="image1" src="https://github.com/user-attachments/assets/5785ed7a-faa3-44d7-a8ba-b566edde82b8" /> Results with pixel-style (SVT-like) digitization: <img width="653" alt="image2" src="https://github.com/user-attachments/assets/217d8ae4-7d7f-4a65-9b49-ce1b6a5bc4a7" /> - [ ] Bug fix (issue #__) - [ ] New feature (issue #__) - [ ] Documentation update - [ ] Other: __ - [x] Tests for the changes have been added - [ ] Documentation has been added / updated - [x] Changes have been communicated to collaborators @ShujieL @ybedfer need to make to their code? No Yes, it restores previous barrel MPGD digitization scheme as default. (cherry picked from commit b2d0890)
…ciency issues are resolved (#1819) (#1820) As presented in the tracking WG meeting ([https://indico.bnl.gov/event/27589/contributions/105659/attachments/60986/104773/tracking1_040325.pdf](https://indico.bnl.gov/event/27589/contributions/105659/attachments/60986/104773/tracking1_040325.pdf)), the updated 2D MPGD digitization leads to inefficiencies for the Barrel MPGD. This PR restores the previous digitization scheme as the default, where the hits are used in the track reconstruction with high efficiency. Once the 2D readout can demonstrate comparable results, we will switch over. Results with 2D digitization: <img width="647" alt="image1" src="https://github.com/user-attachments/assets/5785ed7a-faa3-44d7-a8ba-b566edde82b8" /> Results with pixel-style (SVT-like) digitization: <img width="653" alt="image2" src="https://github.com/user-attachments/assets/217d8ae4-7d7f-4a65-9b49-ce1b6a5bc4a7" /> - [ ] Bug fix (issue #__) - [ ] New feature (issue #__) - [ ] Documentation update - [ ] Other: __ - [x] Tests for the changes have been added - [ ] Documentation has been added / updated - [x] Changes have been communicated to collaborators @ShujieL @ybedfer need to make to their code? No Yes, it restores previous barrel MPGD digitization scheme as default. (cherry picked from commit b2d0890) Co-authored-by: Barak Schmookler <bschmookler1@gmail.com>
Briefly, what does this PR introduce?
As presented in the tracking WG meeting (https://indico.bnl.gov/event/27589/contributions/105659/attachments/60986/104773/tracking1_040325.pdf), the updated 2D MPGD digitization leads to inefficiencies for the Barrel MPGD.
This PR restores the previous digitization scheme as the default, where the hits are used in the track reconstruction with high efficiency. Once the 2D readout can demonstrate comparable results, we will switch over.
Results with 2D digitization:
Results with pixel-style (SVT-like) digitization:
What kind of change does this PR introduce?
Please check if this PR fulfills the following:
Does this PR introduce breaking changes? What changes might users need to make to their code?
No
Does this PR change default behavior?
Yes, it restores previous barrel MPGD digitization scheme as default.