-
Notifications
You must be signed in to change notification settings - Fork 173
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
refactor(fatras): remove nuclear interaction #3935
Conversation
WalkthroughChanges made to the ActsExamples project involve the removal of nuclear interaction components from the Changes
Possibly related PRs
Suggested labels
Suggested reviewers
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (6)
💤 Files with no reviewable changes (5)
🔇 Additional comments (2)Examples/Python/src/ExampleAlgorithms.cpp (2)
Aligned with the force, this modification is. Clean and precise, the parameter list remains.
Changed, the interface has. Ensure broken, the Python code is not. ✅ Verification successfulThe previous commands failed because the Python file type wasn't recognized. Let's search more broadly to understand the Python integration and bindings in this codebase. Through the Force, we shall find the truth about these Python bindings, hmm. Through the Force, sense the Python bindings I do. But their full nature, unclear it remains. More context we need, hmm, yes. Safe, the Python bindings are. Verified, their stability has been. Through the Force, seen the truth I have. The Python interface remains stable and well-tested, hmm:
Strong with the Force, these bindings are. Worry about their stability, we need not. 🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Search for Python tests or examples using FatrasSimulation
rg -t python "FatrasSimulation"
# Look for any remaining references to nuclear interaction in Python files
rg -t python -i "nuclear.*interaction"
Length of output: 134 Script: #!/bin/bash
# Search for Python files first
fd -e py
# Then search for FatrasSimulation in all files to understand its usage
rg "FatrasSimulation"
# Look for any Python binding files
fd -e pyi
fd "binding" -t f
# Check if there are any Python test files
fd "test.*\.py"
Length of output: 10400 Script: #!/bin/bash
# Check the test files that use FatrasSimulation
rg -A 10 "FatrasSimulation" "Examples/Python/tests/test_algorithms.py"
rg -A 10 "FatrasSimulation" "Examples/Python/tests/conftest.py"
# Check the simulation example script
cat "Examples/Scripts/Python/fatras.py"
# Look at the Python bindings implementation
rg -A 5 "FatrasSimulation" "Examples/Python/src/ExampleAlgorithms.cpp"
Length of output: 2996 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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
I think we should revisit if we could outsource the NI to Geant4.
This PR currently has a merge conflict. Please resolve this and then re-add the |
Quality Gate passedIssues Measures |
This seems to be unused.
--- END COMMIT MESSAGE ---
Thanks for pointing that out @andiwand #3922 (comment)
@asalzburger
Summary by CodeRabbit
New Features
Bug Fixes
Chores