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: Add chi2 cut option for outliers to KF fitter function #4059

Merged
merged 4 commits into from
Jan 30, 2025

Conversation

benjaminhuth
Copy link
Member

@benjaminhuth benjaminhuth commented Jan 29, 2025

self explaining

--- END COMMIT MESSAGE ---

Any further description goes here, @-mentions are ok here!

  • Use a conventional commits prefix: quick summary
    • We mostly use feat, fix, refactor, docs, chore and build types.
  • A milestone will be assigned by one of the maintainers

Summary by CodeRabbit

  • New Features

    • Added a configurable chi-squared cut parameter to the Kalman track fitting process.
    • Introduced an optional outlier detection mechanism for track fitting.
    • Allows users to control track quality filtering during reconstruction.
  • Improvements

    • Enhanced track fitting flexibility by adding chi-squared threshold parameter.
    • Provides more granular control over track selection criteria.

@benjaminhuth benjaminhuth added this to the next milestone Jan 29, 2025
Copy link

coderabbitai bot commented Jan 29, 2025

Walkthrough

A new chi2Cut parameter, introduced to the Kalman track fitting functionality, spans multiple files. This parameter allows for the specification of a chi-squared threshold for filtering track states, with a default value set to infinity. Changes include updates to C++ header and implementation files, Python bindings, and example scripts, ensuring the integration of the new outlier detection mechanism is consistent throughout the codebase.

Changes

File Change Summary
.../TrackFitting/include/...TrackFitterFunction.hpp Added chi2Cut parameter to makeKalmanFitterFunction with default std::numeric_limits<double>::infinity()
.../TrackFitting/src/KalmanFitterFunction.cpp Introduced SimpleOutlierFinder struct with chi2Cut and isOutlier method; updated KalmanFitterFunctionImpl to include outlierFinder
.../Python/python/acts/examples/reconstruction.py Added chi2Cut parameter to addKalmanTracks function
.../Python/src/TrackFitting.cpp Updated Python binding for makeKalmanFitterFunction to include chi2Cut
.../Scripts/Python/truth_tracking_kalman_refitting.py Added "chi2Cut": float("inf") to kalmanOptions

Possibly related PRs

Suggested Reviewers

  • andiwand

Poem

In the realm of tracks, a new path we weave,
Chi-squared whispers, in data we believe.
Infinity's call, a threshold so bright,
Guiding our fitting through the quantum night.
A Kalman dance, with precision we strive,
In the world of algorithms, we thrive! 🌌✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e6f0307 and b8272c8.

📒 Files selected for processing (1)
  • Examples/Scripts/Python/truth_tracking_kalman_refitting.py (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • Examples/Scripts/Python/truth_tracking_kalman_refitting.py
⏰ Context from checks skipped due to timeout of 90000ms (80)
  • GitHub Check: merge-sentinel
  • GitHub Check: CI Bridge / build_exatrkx
  • GitHub Check: CI Bridge / build_exatrkx_cpu
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, clang++)
  • GitHub Check: CI Bridge / clang_tidy
  • GitHub Check: missing_includes
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, g++)
  • GitHub Check: build_debug
  • GitHub Check: merge-sentinel
  • GitHub Check: CI Bridge / build_exatrkx
  • GitHub Check: CI Bridge / build_exatrkx_cpu
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, clang++)
  • GitHub Check: CI Bridge / clang_tidy
  • GitHub Check: missing_includes
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, g++)
  • GitHub Check: build_debug
  • GitHub Check: merge-sentinel
  • GitHub Check: CI Bridge / build_exatrkx
  • GitHub Check: CI Bridge / build_exatrkx_cpu
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, clang++)
  • GitHub Check: CI Bridge / clang_tidy
  • GitHub Check: missing_includes
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, g++)
  • GitHub Check: build_debug
  • GitHub Check: merge-sentinel
  • GitHub Check: CI Bridge / build_exatrkx
  • GitHub Check: CI Bridge / build_exatrkx_cpu
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, clang++)
  • GitHub Check: CI Bridge / clang_tidy
  • GitHub Check: missing_includes
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, g++)
  • GitHub Check: build_debug
  • GitHub Check: merge-sentinel
  • GitHub Check: CI Bridge / build_exatrkx
  • GitHub Check: CI Bridge / build_exatrkx_cpu
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, clang++)
  • GitHub Check: CI Bridge / clang_tidy
  • GitHub Check: missing_includes
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, g++)
  • GitHub Check: build_debug
  • GitHub Check: merge-sentinel
  • GitHub Check: CI Bridge / build_exatrkx
  • GitHub Check: CI Bridge / build_exatrkx_cpu
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, clang++)
  • GitHub Check: CI Bridge / clang_tidy
  • GitHub Check: missing_includes
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, g++)
  • GitHub Check: build_debug
  • GitHub Check: merge-sentinel
  • GitHub Check: CI Bridge / build_exatrkx
  • GitHub Check: CI Bridge / build_exatrkx_cpu
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, clang++)
  • GitHub Check: CI Bridge / clang_tidy
  • GitHub Check: missing_includes
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, g++)
  • GitHub Check: build_debug
  • GitHub Check: merge-sentinel
  • GitHub Check: CI Bridge / build_exatrkx
  • GitHub Check: CI Bridge / build_exatrkx_cpu
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, clang++)
  • GitHub Check: CI Bridge / clang_tidy
  • GitHub Check: missing_includes
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, g++)
  • GitHub Check: build_debug
  • GitHub Check: merge-sentinel
  • GitHub Check: CI Bridge / build_exatrkx
  • GitHub Check: CI Bridge / build_exatrkx_cpu
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, clang++)
  • GitHub Check: CI Bridge / clang_tidy
  • GitHub Check: missing_includes
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, g++)
  • GitHub Check: build_debug
  • GitHub Check: merge-sentinel
  • GitHub Check: CI Bridge / build_exatrkx
  • GitHub Check: CI Bridge / build_exatrkx_cpu
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, clang++)
  • GitHub Check: CI Bridge / clang_tidy
  • GitHub Check: missing_includes
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, g++)
  • GitHub Check: build_debug

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added Component - Examples Affects the Examples module Track Fitting labels Jan 29, 2025
Copy link

github-actions bot commented Jan 29, 2025

📊: Physics performance monitoring for b8272c8

Full contents

physmon summary

@benjaminhuth benjaminhuth marked this pull request as ready for review January 29, 2025 14:09
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (2)
Examples/Algorithms/TrackFitting/src/KalmanFitterFunction.cpp (1)

70-78: Consider using existing Acts::TrackHelpers::checkPredictedChi2, hmm.

In TrackHelpers.hpp, a similar function exists already. Duplicate code, this is. Use the existing utility, we should.

-struct SimpleOutlierFinder {
-  double chi2Cut = std::numeric_limits<double>::infinity();
-
-  bool isOutlier(
-      Acts::VectorMultiTrajectory::ConstTrackStateProxy trackState) const {
-    double chi2 = Acts::calculatePredictedChi2(trackState);
-    return chi2 > chi2Cut;
-  }
-};
+using SimpleOutlierFinder = Acts::TrackHelpers::OutlierFinder;
Examples/Python/python/acts/examples/reconstruction.py (1)

1307-1307: Hmmmm, wise addition this is!

A new parameter chi2Cut with default value of infinity, added you have. No outliers rejected by default, this ensures. Backward compatibility maintained, this does.

But caution, young padawan! Document the parameter in the function's docstring, you should. Help future Jedi understand its purpose, this will.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e61fa2d and b0611ca.

📒 Files selected for processing (5)
  • Examples/Algorithms/TrackFitting/include/ActsExamples/TrackFitting/TrackFitterFunction.hpp (1 hunks)
  • Examples/Algorithms/TrackFitting/src/KalmanFitterFunction.cpp (5 hunks)
  • Examples/Python/python/acts/examples/reconstruction.py (1 hunks)
  • Examples/Python/src/TrackFitting.cpp (1 hunks)
  • Examples/Scripts/Python/truth_tracking_kalman_refitting.py (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, clang++)
  • GitHub Check: linux_ubuntu_extra (ubuntu2204, 20, g++)
  • GitHub Check: linux_ubuntu
  • GitHub Check: macos
  • GitHub Check: build_debug
  • GitHub Check: missing_includes
🔇 Additional comments (6)
Examples/Algorithms/TrackFitting/src/KalmanFitterFunction.cpp (2)

89-89: Approve the outlier finder integration, I do.

Clean and consistent with existing patterns, this integration is. Well done, young padawan!

Also applies to: 116-117


175-175: Approve the chi2Cut parameter handling, I do.

Properly initialized and passed through, the chi2Cut parameter is. Clear and correct, the implementation is.

Also applies to: 207-207

Examples/Algorithms/TrackFitting/include/ActsExamples/TrackFitting/TrackFitterFunction.hpp (1)

71-71: Approve the function signature update, I do.

Wise choice of default value to infinity, it is. Backward compatibility, this maintains.

Examples/Python/src/TrackFitting.cpp (1)

56-56: Approve the Python binding changes, I do.

Properly exposed to Python, the chi2Cut parameter is. The Force is strong with these bindings.

Also applies to: 60-60, 66-66

Examples/Scripts/Python/truth_tracking_kalman_refitting.py (1)

37-37: Approve the kalmanOptions update, I do.

Consistent with C++ defaults, this change is. Balance to the Force, it brings.

Examples/Python/python/acts/examples/reconstruction.py (1)

Line range hint 1299-1308: Verify the chi-squared cut parameter's journey, we must.

Through the Python bindings to the C++ implementation, flow this parameter must. Check its path, we shall.

Document the parameter in function's docstring, like this you should:

 def addKalmanTracks(
     s: acts.examples.Sequencer,
     trackingGeometry: acts.TrackingGeometry,
     field: acts.MagneticFieldProvider,
     reverseFilteringMomThreshold: float = 0 * u.GeV,
     inputProtoTracks: str = "truth_particle_tracks",
     multipleScattering: bool = True,
     energyLoss: bool = True,
     clusters: str = None,
     calibrator: acts.examples.MeasurementCalibrator = acts.examples.makePassThroughCalibrator(),
+    chi2Cut: float = float("inf"),
     logLevel: Optional[acts.logging.Level] = None,
 ) -> None:
     """This function steers the seeding
     Parameters
     ----------
     s: Sequencer
         the sequencer module to which we add the Seeding steps (returned from addSeeding)
     trackingGeometry : tracking geometry
     field : magnetic field
     reverseFilteringMomThreshold : float
         momentum threshold for reverse filtering
     inputProtoTracks : str
         input proto tracks collection name
     multipleScattering : bool
         include multiple scattering
     energyLoss : bool
         include energy loss
     clusters : str
         input clusters collection name
     calibrator : MeasurementCalibrator
         measurement calibrator instance
+    chi2Cut : float
+        Chi-squared cut value for outlier rejection. Default is infinity (no cut).
     logLevel : Optional[acts.logging.Level]
         logging level
     """
✅ Verification successful

Correct, the chi-squared cut implementation is, young Padawan!

Through the Force, I sense proper flow of the chi-squared cut parameter:

  • From Python realm to C++ implementation it travels
  • In outlier rejection, its purpose it serves
  • Default value of infinity, preserved it remains

Your docstring update suggestion, wisdom it shows. Proceed with it, you should!

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for chi2Cut usage in C++ implementation
echo "Searching for chi2Cut usage in C++ files..."
rg -t cpp "chi2Cut|chi2_cut" 

# Search for related Kalman filter configuration
echo "Searching for Kalman filter configuration..."
rg -t cpp "KalmanFitterFunction|KalmanFitterOptions"

Length of output: 5309

@kodiakhq kodiakhq bot merged commit ec213e9 into acts-project:main Jan 30, 2025
43 checks passed
@acts-project-service
Copy link
Collaborator

🔴 Athena integration test results [ec213e9]

Build job with this PR failed!

Please investigate the build job for the pipeline!

@acts-project-service acts-project-service added the Breaks Athena build This PR breaks the Athena build label Jan 30, 2025
paulgessinger pushed a commit to paulgessinger/acts that referenced this pull request Jan 30, 2025
@paulgessinger paulgessinger modified the milestones: next, v39.0.0 Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Breaks Athena build This PR breaks the Athena build Component - Examples Affects the Examples module Track Fitting
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants