DPL Analysis: introduce binned expression#14174
Conversation
|
REQUEST FOR PRODUCTION RELEASES: This will add The following labels are available |
|
Error while checking build/O2/fullCI_slc9 for 2e8a918 at 2025-04-11 15:30: Full log here. |
|
Error while checking build/O2/fullCI_slc9 for 95f5ecd at 2025-04-12 01:27: Full log here. |
Fix logic: * bins are defined as [lower : upper) * separate "less than lower" node
|
Error while checking build/O2/fullCI_slc9 for 8d2f417 at 2025-04-12 18:00: Full log here. |
|
Error while checking build/O2/fullCI_slc9 for 3b50806 at 2025-04-12 19:09: Full log here. |
|
Feature not used. Unit test added. Merging on @jackal1-66 request. |
Introducing a "binned" expression node that can be used in configurable expression columns. The syntax is the following:
binned(bins_vector, parameters_vector, binned_expression, parametrized_expression, out_of_bounds_expression), wherebins_vectoris afloatordoublevector with bin lower edges and the rightmost upper edge as a final element, containingnbins + 1elements in totalparameters_vectoris a flat vector with parameter values for the parametrized expression, grouped by parameter, meaning that first you have parameter0 for all bins, then parameter1 for all bins, etc. Can be empty.binned_expressiondetermines the quantity that needs to be compared with bin edges. It can be a generic expression or a single column, e.g.aod::track::phiparametrized_experssionis the expression that needs to be computed for all rows of the original table, parameters can be used aspar(<number>), starting frompar(0). The consistency with theparameters_vectoris not checked.out_of_bounds_expressionprovides the value for the binned quantity is outside of the bounds determined by bins vector, it should have the same return type as the parametrized expression but otherwise is a generic expressionThis is equivalent to the following code