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

fix: Early exit in the seeding if there are no space points for top/bottom… #3284

Merged
merged 3 commits into from
Jun 13, 2024

Conversation

CarloVarni
Copy link
Collaborator

@CarloVarni CarloVarni commented Jun 13, 2024

The following cut in the code was supposed to allow for an early exit of the code in case there are no space points that can be used as bottom or top candidates

if (state.bottomNeighbours.size() == 0 || state.topNeighbours.size() == 0)

Too bad this was buggy and it was always false, since those arrays were always filled even if there were no space points. This PR fixes it, since now the arrays state.topNeighbours and state.bottomNeighbours are filled only if the bin contains entries.

@CarloVarni CarloVarni added the Bug Something isn't working label Jun 13, 2024
@CarloVarni CarloVarni added this to the next milestone Jun 13, 2024
@github-actions github-actions bot added Component - Core Affects the Core module Seeding labels Jun 13, 2024
@CarloVarni CarloVarni requested a review from andiwand June 13, 2024 09:43
Copy link
Contributor

@andiwand andiwand left a comment

Choose a reason for hiding this comment

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

LGTM - Maybe @LuisFelipeCoelho whats to have another look

Copy link

codecov bot commented Jun 13, 2024

Codecov Report

Attention: Patch coverage is 0% with 7 lines in your changes missing coverage. Please review.

Project coverage is 47.36%. Comparing base (dda478e) to head (8577c19).
Report is 273 commits behind head on main.

Files with missing lines Patch % Lines
Core/include/Acts/Seeding/SeedFinder.ipp 0.00% 7 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3284      +/-   ##
==========================================
- Coverage   47.37%   47.36%   -0.01%     
==========================================
  Files         511      511              
  Lines       30254    30260       +6     
  Branches    14679    14680       +1     
==========================================
  Hits        14333    14333              
- Misses       5383     5389       +6     
  Partials    10538    10538              

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

Copy link
Member

@LuisFelipeCoelho LuisFelipeCoelho 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 fixing this @CarloVarni. It looks good to me. Do you know if this improves the CPU performance? Maybe for high-pileup it doesn't change much?

@CarloVarni
Copy link
Collaborator Author

Thanks for fixing this @CarloVarni. It looks good to me. Do you know if this improves the CPU performance? Maybe for high-pileup it doesn't change much?

I suspect a very minimal improvement, and only for single particle cases.

@AJPfleger
Copy link
Contributor

Just flickered the automerge label, because gitlab hasn't started yet and I squeezed in a PR, that already finished.

@kodiakhq kodiakhq bot merged commit 2877323 into acts-project:main Jun 13, 2024
51 checks passed
@CarloVarni CarloVarni deleted the ProperCheckOnCandidates branch June 13, 2024 17:51
paulgessinger pushed a commit to paulgessinger/acts that referenced this pull request Jun 14, 2024
…ottom… (acts-project#3284)

The following cut in the code was supposed to allow for an early exit of the code in case there are no space points that can be used as bottom or top candidates
```cpp
if (state.bottomNeighbours.size() == 0 || state.topNeighbours.size() == 0)
```

Too bad this was buggy and it was always false, since those arrays were always filled even if there were no space points. This PR fixes it, since now the arrays `state.topNeighbours` and `state.bottomNeighbours` are filled only if the bin contains entries.
@andiwand andiwand modified the milestones: next, v35.2.0 Jun 16, 2024
Matthewharri pushed a commit to Matthewharri/acts that referenced this pull request Jun 18, 2024
…ottom… (acts-project#3284)

The following cut in the code was supposed to allow for an early exit of the code in case there are no space points that can be used as bottom or top candidates
```cpp
if (state.bottomNeighbours.size() == 0 || state.topNeighbours.size() == 0)
```

Too bad this was buggy and it was always false, since those arrays were always filled even if there were no space points. This PR fixes it, since now the arrays `state.topNeighbours` and `state.bottomNeighbours` are filled only if the bin contains entries.
timadye pushed a commit to andiwand/acts that referenced this pull request Jun 27, 2024
…ottom… (acts-project#3284)

The following cut in the code was supposed to allow for an early exit of the code in case there are no space points that can be used as bottom or top candidates
```cpp
if (state.bottomNeighbours.size() == 0 || state.topNeighbours.size() == 0)
```

Too bad this was buggy and it was always false, since those arrays were always filled even if there were no space points. This PR fixes it, since now the arrays `state.topNeighbours` and `state.bottomNeighbours` are filled only if the bin contains entries.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Component - Core Affects the Core module Seeding
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants