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

Strategy to partition simulated events according to runs #16

Open
gipert opened this issue Dec 4, 2024 · 0 comments
Open

Strategy to partition simulated events according to runs #16

gipert opened this issue Dec 4, 2024 · 0 comments
Assignees
Labels
discussion Further information is requested

Comments

@gipert
Copy link
Member

gipert commented Dec 4, 2024

We want to partition already at the build-hit stage (since hit parameters like energy resolution vary across partitions. Figuring out which file to open and from which row (step index) to start reading is challenging. We should think about an efficient way to compute a lookup table once per workflow and re-use it, considering that:

  • Geant4 event indices are not linearly increasing in output files with multithreaded remage
  • If we want to merge files from multiple threads (desired because of filesystem reasons), the indices won't be sorted either (unless we do some explicit sorting)
  • The output hit files will need to have an event ID structure that makes it easy to build events later

Let's think about a good solution here

@gipert gipert added the discussion Further information is requested label Dec 4, 2024
@gipert gipert self-assigned this Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant