DPL Analysis: add configurable expression columns #14141
Merged
+310
−99
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.
Introducing configurable expression columns.
A special expression column defined with
DECLARE_SOA_CONFIGURABLE_EXPRESSION_COLUMN(Name, getter, type, "label")A special extended table defined with
DECLARE_SOA_CONFIGURABLE_EXTENDED_TABLE(Name, BaseTable, "DESC", ext::column2, ext::column2, ...)that can only contain configurable expression columnsDefines<Name> d;template that can be added to an analysis task, indicating that it will define and produce this special extended tableThe actual expressions can be set inside
init()function of the analysis task, usingd.projectorsarray using the same order of columns as in the table declarationThe expressions can use configurables from the task, as they are already set before
init()is calledThe aim is to be able to set the expressions from external sources, i.e. CCDB, task configuration JSON, etc.
Improved Gandiva projector caching behavior for
SpawnsandDefinesAdded a test for the new functionality
The corresponding example in O2Physics will be updated after this is merged.