build: Only install python files for enabled components

[paulgessinger]

--- 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

• Chores
  • Updated CMake configuration for Python file installation
  • Improved file installation process to preserve directory structure
  • Removed symbolic link creation for Python files

[coderabbitai]

Walkthrough

Hmm, changes to CMakeLists.txt, I see. A transformation of Python file installation method, this is. Gone are the symbolic links, replaced by direct file installation with preserved directory structure. The CMake configuration now ensures files land in their rightful subdirectories, maintaining the path integrity they once knew.

Changes

File	Change Summary
Examples/Python/CMakeLists.txt	Replaced symbolic link creation with direct file installation, preserving original directory hierarchy

Poem

In paths of code, wisdom flows
🐍 Python files, no longer in rows
Directories dance, structure preserved
CMake's magic, carefully observed
Links symbolic, now fade away 🌟
Paths true and clear, code's new way

Chuckles softly in Yoda-speak

---

📜 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 ff60049 and 0c6de55.

📒 Files selected for processing (1)

• Examples/Python/CMakeLists.txt (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (19)

• GitHub Check: merge-sentinel
• GitHub Check: unused_files
• GitHub Check: macos
• GitHub Check: missing_includes
• GitHub Check: CI Bridge / lcg_106a: [alma9, clang16]
• GitHub Check: CI Bridge / lcg_106a: [alma9, gcc14]
• GitHub Check: linux_ubuntu_extra (ubuntu2204_clang, 20)
• GitHub Check: CI Bridge / lcg_106a: [alma9, gcc13]
• GitHub Check: CI Bridge / lcg_105: [alma9, gcc13]
• GitHub Check: CI Bridge / lcg_105: [alma9, clang16]
• GitHub Check: CI Bridge / linux_ubuntu_2204
• GitHub Check: CI Bridge / linux_ubuntu_2204_clang
• GitHub Check: linux_ubuntu_extra (ubuntu2204, 20)
• GitHub Check: CI Bridge / build_linux_ubuntu
• GitHub Check: CI Bridge / build_exatrkx
• GitHub Check: CI Bridge / build_exatrkx_cpu
• GitHub Check: CI Bridge / clang_tidy
• GitHub Check: linux_ubuntu
• GitHub Check: build_debug

🔇 Additional comments (2)

Examples/Python/CMakeLists.txt (2)

272-277: Hmmmm, wise changes these are, approve them I do!

A more elegant solution this is, young padawan. Direct file installation with preserved directory structure, better than symbolic links it is. The Force flows stronger through this implementation, yes.

Verify the path handling we must. Run this command, we shall:

✅ Verification successful

Safe and sound, the path structure is! Hmmmm.

Through the Force, I sense no disturbance in the Python paths. One relative import only, in __init__.py it lives, and preserved perfectly the directory structure shall be. Strong with the CMake, this solution is!

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any potential path issues in Python files

# Search for relative imports that might break with the new structure
rg -g '*.py' -A 3 'from \.\.' python/acts/

Length of output: 97

---

Script:

#!/bin/bash
# First, find all Python files
echo "=== Python Files Structure ==="
fd -e py . Examples/Python

# Then examine their imports
echo -e "\n=== Import Statements ==="
fd -e py . Examples/Python --exec rg -l "from \.\.|from \."

# Check the directory structure
echo -e "\n=== Directory Structure ==="
fd . Examples/Python/python/acts -t d

Length of output: 2037

---

274-277: Mindful of plugins, we must be!

A path to wisdom this change is, but careful with plugin files we must remain. Each plugin's Python files, installed correctly they must be.

Check plugin paths we shall:

✅ Verification successful

Correct and wise, the path structure is!

Through the Force, I see the Python files organized well they are. Under Examples/Python/python/acts/examples/, all plugin files reside, and the installation path ${_python_install_dir}/${_rel} preserves this structure it does. No conflicts in the paths, there are.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify plugin Python files installation paths

# List all Python files from plugins
echo "=== Plugin Python files ==="
fd -e py . python/acts/examples/

# Check for potential path conflicts
echo "=== Checking for path conflicts ==="
fd -e py . python/acts/ -x dirname {} | sort | uniq -d

Length of output: 448

---

Script:

#!/bin/bash
# First, find all Python files to understand the structure
echo "=== All Python files ==="
fd -e py

# Then look for CMake files that might handle plugins
echo -e "\n=== CMake files mentioning Python plugins ==="
rg -l "python" --type cmake

# Finally, check the actual plugin structure
echo -e "\n=== Plugin-related directories ==="
fd "plugin|examples" -t d

Length of output: 9741

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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]

📊: Physics performance monitoring for 6f5800d

Full contents

physmon summary

• ✅ Particles fatras
• ✅ Particles geant4
• ✅ Particles ttbar
• ✅ Vertices ttbar
• ✅ Truth tracking (KF)
• ✅ Truth tracking (GSF)
• ✅ Truth tracking (GX2F)
• ✅ Truth tracking (KF refit)
• ✅ Truth tracking (GSF refit)
• ✅ CKF finding performance | trackfinding | single muon | truth smeared seeding
• ✅ CKF fitting performance | trackfinding | single muon | truth smeared seeding
• ✅ CKF track summary | trackfinding | single muon | truth smeared seeding
• ✅ Seeding trackfinding | single muon | truth estimated seeding
• ✅ CKF finding performance | trackfinding | single muon | truth estimated seeding
• ✅ CKF fitting performance | trackfinding | single muon | truth estimated seeding
• ✅ CKF track summary | trackfinding | single muon | truth estimated seeding
• ✅ Seeding trackfinding | single muon | default seeding
• ✅ CKF finding performance | trackfinding | single muon | default seeding
• ✅ CKF fitting performance | trackfinding | single muon | default seeding
• ✅ CKF track summary | trackfinding | single muon | default seeding
• ✅ Seeding trackfinding | single muon | orthogonal seeding
• ✅ CKF finding performance | trackfinding | single muon | orthogonal seeding
• ✅ CKF fitting performance | trackfinding | single muon | orthogonal seeding
• ✅ CKF track summary | trackfinding | single muon | orthogonal seeding
• ✅ Seeding trackfinding | 4 muon x 50 vertices | default seeding
• ✅ CKF finding performance | trackfinding | 4 muon x 50 vertices | default seeding
• ✅ CKF fitting performance | trackfinding | 4 muon x 50 vertices | default seeding
• ✅ CKF track summary | trackfinding | 4 muon x 50 vertices | default seeding
• ✅ Ambisolver finding performance | trackfinding | 4 muon x 50 vertices | default seeding
• ✅ IVF notime | trackfinding | 4 muon x 50 vertices | default seeding
• ✅ AMVF gauss notime | trackfinding | 4 muon x 50 vertices | default seeding
• ✅ AMVF grid time | trackfinding | 4 muon x 50 vertices | default seeding
• ✅ Seeding trackfinding | ttbar with 200 pileup | default seeding
• ✅ CKF finding performance | trackfinding | ttbar with 200 pileup | default seeding
• ✅ CKF fitting performance | trackfinding | ttbar with 200 pileup | default seeding
• ✅ CKF track summary | trackfinding | ttbar with 200 pileup | default seeding
• ✅ Ambisolver finding performance | trackfinding | ttbar with 200 pileup | default seeding
• ✅ ML Ambisolver | trackfinding | ttbar with 200 pileup | default seeding
• ✅ AMVF gauss notime | trackfinding | ttbar with 200 pileup | default seeding
• ✅ AMVF grid time | trackfinding | ttbar with 200 pileup | default seeding

[goetzgaycken]

looks good and solves the issue that python bindings for geant4 examples used to be installed also if geant4 support was disabled.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[acts-project-service]

🔴 Athena integration test results [ba5a781]

🔴 Some tests have failed!

Please investigate the pipeline!

status	job	report
🟢	report_pull_request
🟡	run_workflow_tests_run4_mc
🟢	run_workflow_tests_run2_mc
🟢	run_workflow_tests_run2_data
🟢	run_workflow_tests_run3_mc
🟢	run_workflow_tests_run3_data
🟢	test_ActsDumpGeometryIdentifiers
🔴	test_ActsCheckObjectCountsWorkflowHgtd
🔴	test_ActsCheckObjectCountsCachedWorkflow
🔴	test_ActsCheckObjectCountsWorkflow
🟢	test_ActsEFTrackFit
🟢	test_ActsPersistifySeeds
🔴	test_ActsBenchmarkWithSpot
🟢	test_ActsAnalogueClustering
🟢	test_ActsWorkflowHeavyIons
🟢	test_ActsWorkflowFastTracking
🟢	test_ActsWorkflowCached
🔴	test_ActsWorkflow
🟢	test_ActsValidateAmbiguityResolution
🟢	test_ActsValidateResolvedTracks
🟢	test_ActsValidateTracks
🟢	test_ActsValidateActsCoreSpacePoints
🟢	test_ActsValidateActsSpacePoints
🟢	test_ActsValidateSeeds
🟢	test_ActsValidateOrthogonalSeeds
🟢	test_ActsValidateClusters
🟢	test_ActsPersistifyEDM
🔴	test_ActsGx2fRefitting
🟢	test_ActsGSFRefitting
🟢	test_ActsKfRefitting
🟢	test_ActsExtrapolationAlgTest
🟢	test_ActsITkTest