{{ message }}
Add support for bitmap in ROFRecords#13385
Merged
mconcas merged 1 commit intoAliceO2Group:devfrom Aug 15, 2024
Merged
Conversation
Contributor
Collaborator
|
@mconcas if you want, you can set it first to the vertices rofrecord vector than copy it to track's rofrecords, but only the latter is loaded in the AODProducer. |
Collaborator
Author
Ah true, I would then just keep this logic just to save one extra iteration on the vertices. |
981ace7 to
c5f88c3
Compare
Collaborator
Author
Collaborator
|
Error while checking build/O2/fullCI for c5f88c3 at 2024-08-15 07:27: Full log here. |
shahor02
approved these changes
Aug 15, 2024
chiarazampolli
pushed a commit
that referenced
this pull request
Aug 26, 2024
(cherry picked from commit b8782ae)
Collaborator
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
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.


@shahor02 : I am still testing to see if it actually works.
The logic would be to tag the ROFRecords for seeding vertices in any case with corresponding two bits (first iteration, upc iteration). Then tag the tracks ROFs if we found tracks there.
If you believe, I can tag only the track ones using vertices flags and any filtering can be done on a later analysis.