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

feat: Reintroduce default bin finder constructor #1197

Merged

Conversation

stephenswat
Copy link
Member

In Acts version 15.0.0, we see support being added for dynamic bins in the bin finder. However, this also means that we no longer have useful default constructors for this class. This has caused me a few issues in terms of backwards compatibility. I think it would be a good idea to reintroduce some sane default configuration for the bin finder, and I discussed with @LuisFelipeCoelho that having an empty list of z neighbours with a single φ neighbour would be a good default.

@stephenswat stephenswat self-assigned this Mar 22, 2022
@stephenswat stephenswat added Component - Core Affects the Core module Improvement Changes to an existing feature Impact - Minor Nuissance bug and/or affects only a single module labels Mar 22, 2022
@stephenswat stephenswat added this to the next milestone Mar 22, 2022
@stephenswat stephenswat removed their assignment Mar 22, 2022
In Acts version 15.0.0, we see support being added for dynamic bins in
the bin finder. However, this also means that we no longer have useful
default constructors for this class. This has caused me a few issues in
terms of backwards compatibility. I think it would be a good idea to
reintroduce some sane default configuration for the bin finder, and I
discussed with @LuisFelipeCoelho that having an empty list of z
neighbours with a single phi neighbour would be a good default.
@stephenswat stephenswat force-pushed the feat/binfinder_default_constructor branch from 5427364 to 8cea3ba Compare March 22, 2022 15:43
@codecov
Copy link

codecov bot commented Mar 22, 2022

Codecov Report

Merging #1197 (9ccdf26) into main (3e014d5) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1197   +/-   ##
=======================================
  Coverage   47.75%   47.75%           
=======================================
  Files         360      360           
  Lines       18616    18616           
  Branches     8774     8774           
=======================================
  Hits         8890     8890           
  Misses       3674     3674           
  Partials     6052     6052           
Impacted Files Coverage Δ
Core/include/Acts/Seeding/BinFinder.hpp 0.00% <ø> (ø)
Core/include/Acts/Seeding/BinFinder.ipp 0.00% <ø> (ø)

📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

@paulgessinger
Copy link
Member

Format fails.

@stephenswat
Copy link
Member Author

On code that I didn't touch 😢

@paulgessinger
Copy link
Member

That is pretty weird. The CI is not setup to only format changes, this was merged the way it's formatted now in #1038, and there clang-format was happy... and has been on every commit to main since then. But here it fails, and locally on my machine clang-format also reformats that file...

What the heck?

@stephenswat
Copy link
Member Author

That's what I thought as well. 😄

As much as I dislike staging and committing unrelated changes like this it's really no problem.

Copy link
Member

@paulgessinger paulgessinger left a comment

Choose a reason for hiding this comment

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

@LuisFelipeCoelho had approved before, no changes since then other than formatting.

@kodiakhq kodiakhq bot merged commit b2364f6 into acts-project:main Mar 23, 2022
@paulgessinger paulgessinger modified the milestones: next, v18.0.0 Apr 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Component - Core Affects the Core module Impact - Minor Nuissance bug and/or affects only a single module Improvement Changes to an existing feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants