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: Optimize EDM4hep particle reading #3978

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

paulgessinger
Copy link
Member

@paulgessinger paulgessinger commented Dec 11, 2024

We were previously adding the particles to the particle container (flat_set) one by one, which lead to a ton of copy operations. This now accumulates the particles in vectors, sorts them, and then produces the particle containers.

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

    • Enhanced memory allocation and efficiency for particle collections.
    • Introduced sorting for unordered particle vectors.
  • Bug Fixes

    • Improved error handling for missing particles in the particle map.

Copy link

coderabbitai bot commented Dec 11, 2024

Walkthrough

Changes made to the EDM4hepReader class in EDM4hepReader.cpp involve replacing SimParticleContainer with std::vector<SimParticle>, renaming the variables to particlesGeneratorUnordered and particlesSimulatedUnordered. The memory allocation is optimized using reserve, and the logic for populating these vectors now employs push_back. Sorting is introduced for both vectors, and error handling is improved with checks for particle existence. A future task to order simulated hits by time is noted but not implemented.

Changes

File Change Summary
Examples/Io/EDM4hep/src/EDM4hepReader.cpp - Replaced SimParticleContainer with std::vector<SimParticle> for particle collections.
- Renamed variables to particlesGeneratorUnordered and particlesSimulatedUnordered.
- Added reserve calls for memory optimization.
- Updated logic to use push_back instead of insert.
- Introduced sorting with std::ranges::sort.
- Enhanced error handling for missing particles.
- Commented section for future task on ordering simulated hits by time.

Possibly related PRs

  • fix: Add hit count in root dump reader #3929: The changes in RootAthenaDumpReader.cpp involve handling particles, which is conceptually related to the modifications made in EDM4hepReader.cpp regarding the management of particle collections, even though they focus on different classes.

Suggested labels

automerge

Suggested reviewers

  • andiwand

In code we trust, with vectors we play,
Unordered particles, now sorted away.
Memory reserved, errors checked tight,
A future task waits, for hits to ignite.
With each little change, our system grows bright! 🌟


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. (Experiment)
  • @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 this to the next milestone Dec 11, 2024
@github-actions github-actions bot added the Component - Examples Affects the Examples module label Dec 11, 2024
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

🧹 Outside diff range and nitpick comments (1)
Examples/Io/EDM4hep/src/EDM4hepReader.cpp (1)

Line range hint 244-299: Memory handling for large particle collections, verify we must!

For extremely large particle collections, consider monitoring memory usage you should. Though pre-allocation helps, temporary memory usage during sorting, doubled it is.

Consider these aspects:

  • Monitor peak memory usage during sorting
  • For very large collections, consider batch processing
  • Memory pressure on systems with limited resources, watch for
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 595f2e6 and 12806bd.

📒 Files selected for processing (1)
  • Examples/Io/EDM4hep/src/EDM4hepReader.cpp (3 hunks)
🔇 Additional comments (3)
Examples/Io/EDM4hep/src/EDM4hepReader.cpp (3)

244-247: Wise optimization of memory allocation, this is!

Pre-allocating memory with reserve based on collection size, prevent unnecessary reallocations it does. Performance benefits, this brings.


259-259: Efficient particle accumulation strategy, you have chosen!

Using push_back on pre-allocated vectors, better than individual insertions into flat_set it is. Copy operations, reduced they are.

Also applies to: 289-289


292-299: A single sort operation before container construction, powerful this approach is!

Batch sorting of accumulated particles, followed by single container construction, more efficient than repeated sorting during individual insertions it is. However, verify the impact on particle ordering we must.

✅ Verification successful

Safe and correct, this sorting approach is!

Examined the implementation thoroughly, I have. Clear it is that:

  • Using boost::container::flat_set for SimParticleContainer, ordered by particle ID it remains
  • CompareParticleId comparator, consistent ordering by particleId() it ensures
  • Preserves particle relationships it does, through groupByPrimaryVertex and groupBySecondaryVertex functions

The Force is strong with this implementation. Maintain proper particle ordering it does, while performance benefits from single sort operation it gains.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that particle ordering is preserved after sorting
# Look for any existing tests or assertions about particle ordering

# Search for tests related to particle ordering
rg -l "particle.*order" --type cpp --type hpp

# Search for CompareParticleId usage and implementation
ast-grep --pattern 'struct CompareParticleId {
  $$$
}'

Length of output: 133


Script:

#!/bin/bash
# Search for CompareParticleId implementation with correct file extensions
rg -p "struct.*CompareParticleId" --type cpp --type-add "hpp:*.hpp"

# Search for particle ordering tests with correct file extensions
rg -p "particle.*order" --type cpp --type-add "hpp:*.hpp"

# Find and examine test files related to EDM4hepReader
fd "Test.*EDM4hep.*\.(cpp|hpp)$"

# Look for the implementation details of SimParticleContainer
rg -p "class.*SimParticleContainer" --type cpp --type-add "hpp:*.hpp"

Length of output: 3822


Script:

#!/bin/bash
# Examine the CompareParticleId implementation
cat Examples/Framework/include/ActsExamples/EventData/SimParticle.hpp

# Look for SimParticleContainer definition
rg -p "SimParticleContainer" Examples/Framework/include/ActsExamples/EventData/SimParticle.hpp

Length of output: 9619

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

🧹 Outside diff range and nitpick comments (3)
Examples/Io/EDM4hep/src/EDM4hepReader.cpp (3)

260-260: Enhance error message with particle details, we must!

More context in error messages, helpful it would be. Particle properties in logs, aid debugging they will.

-      ACTS_ERROR("Particle " << inParticle.getObjectID().index
-                             << " not found in particle map");
+      ACTS_ERROR("Particle " << inParticle.getObjectID().index
+                             << " not found in particle map. "
+                             << "PDG: " << inParticle.getPDG()
+                             << ", Status: " << inParticle.getGeneratorStatus());

Also applies to: 290-290


293-299: Move semantics, utilize we should!

Unnecessary copies, avoid we must. More efficient, move semantics are.

-  SimParticleContainer particlesGenerator{particlesGeneratorUnordered.begin(),
-                                          particlesGeneratorUnordered.end()};
-  SimParticleContainer particlesSimulated{particlesSimulatedUnordered.begin(),
-                                          particlesSimulatedUnordered.end()};
+  SimParticleContainer particlesGenerator{
+      std::make_move_iterator(particlesGeneratorUnordered.begin()),
+      std::make_move_iterator(particlesGeneratorUnordered.end())};
+  SimParticleContainer particlesSimulated{
+      std::make_move_iterator(particlesSimulatedUnordered.begin()),
+      std::make_move_iterator(particlesSimulatedUnordered.end())};

377-380: Track the time-based sorting enhancement, we must!

Sorting by geometry ID implemented is, but time-based sorting mentioned in comments it is. Track this enhancement for future implementation, we should.

Would you like me to create a GitHub issue to track the implementation of time-based sorting for SimHits?

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 12806bd and 2b9db42.

📒 Files selected for processing (1)
  • Examples/Io/EDM4hep/src/EDM4hepReader.cpp (5 hunks)
🔇 Additional comments (1)
Examples/Io/EDM4hep/src/EDM4hepReader.cpp (1)

245-248: Wise optimization, this is!

Prevent unnecessary reallocations, reserving capacity does. Memory fragmentation, it reduces. Performance benefits, it brings.

Copy link

📊: Physics performance monitoring for 2b9db42

Full contents

physmon summary

Comment on lines +293 to +294
std::ranges::sort(particlesGeneratorUnordered, detail ::CompareParticleId{});
std::ranges::sort(particlesSimulatedUnordered, detail ::CompareParticleId{});
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
std::ranges::sort(particlesGeneratorUnordered, detail ::CompareParticleId{});
std::ranges::sort(particlesSimulatedUnordered, detail ::CompareParticleId{});
std::ranges::sort(particlesGeneratorUnordered, detail::CompareParticleId{});
std::ranges::sort(particlesSimulatedUnordered, detail::CompareParticleId{});

}
}

std::ranges::sort(simHitsUnordered, detail ::CompareGeometryId{});
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
std::ranges::sort(simHitsUnordered, detail ::CompareGeometryId{});
std::ranges::sort(simHitsUnordered, detail::CompareGeometryId{});

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component - Examples Affects the Examples module
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants