Split big data eras into multiple anaTuples#222
Merged
kandrosov merged 4 commits intocms-flaf:mainfrom Feb 3, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR implements the ability to split large data eras into multiple anaTuple output files, addressing scalability issues with very large data eras. The changes introduce a configurable nEventsPerFile parameter that can be set differently for data vs. MC, defaulting to 1,000,000 events for data and 100,000 for MC.
Changes:
- Unified merge strategy creation through a new
CreateMergeStrategywrapper function that dispatches to data or MC-specific strategies - Enhanced
CreateDataMergeStrategyto split data eras into multiple output files based on event count thresholds - Added handling for oversized input files in
CreateMCMergeStrategyto prevent processing failures - Made
nEventsPerFileconfigurable per process group with dictionary-based configuration
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| AnaProd/tasks.py | Updated to use unified CreateMergeStrategy function and enhanced nEventsPerFile configuration to support per-process-group values |
| AnaProd/AnaTupleFileList.py | Added wrapper function CreateMergeStrategy, modified CreateDataMergeStrategy to generate multiple output files per era, and added oversized file handling to CreateMCMergeStrategy |
Contributor
Author
|
@cms-flaf-bot please test |
Collaborator
|
pipeline#13949620 started |
Collaborator
|
pipeline#13949620 passed |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.