[PWGCF] Add lite track and collision tables to femto framework#17188
Merged
Conversation
|
O2 linter results: ❌ 0 errors, |
ariedel-cern
marked this pull request as ready for review
July 23, 2026 20:09
ariedel-cern
requested review from
alibuild,
dimihayl,
lauraser,
shouqiye,
victor-gonzalez and
wrzesaCERN
as code owners
July 23, 2026 20:09
ariedel-cern
enabled auto-merge (squash)
July 23, 2026 20:09
alibuild
approved these changes
Jul 23, 2026
alibuild
left a comment
alibuild
left a comment
Collaborator
There was a problem hiding this comment.
Auto-approving on behalf of @ariedel-cern.
Collaborator
|
Error while checking build/O2Physics/code-check for 629d2f5 at 2026-07-23 23:02: Full log here. |
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.
In a typical derived data production, the track table accounts for roughly 80% of the total data size. This PR introduces new "lite" tables (FLiteTracks, FLiteCols) that store pt, eta, and phi as binned uint16_t values rather than full-precision floats, reducing the overall derived data size by roughly 20% with no significant loss of kinematic accuracy. The same binning approach is applied to select collision properties (vertex Z, multiplicity, centrality).