Page Comparison

...

Multi-Variable Criteria Rules

...

⚠️ Multi-variable criteria are deprecated and will be removed from OE v5 onward.

...

A multi-variable criterion applies to a list of variables. They use the same way as computations to refer to the variables to which they apply (see Variables Description to learn how to refer to variables from other spaces). For instance, If the user wants all variables of the same key to be equal, then the equality criterion should be placed in a “global” dimensionless space, using all as on type. If the user wants several variables of different keys to be equal, then the criterion should be in the same space as these variables and use fixed as on type.

...

⚠️ Alignment criteria are deprecated and will be removed from OE v5 onward. The better solution is to explicitly describe alignments, with actual computed variables and threshold criteria, using spaces with dimensions sharing the same categories (see https://pricefx.atlassian.net/wiki/spaces/KB/pages/3867639907/Spaces+and+Scopes+Description#Spaces and https://pricefx.atlassian.net/wiki/spaces/KB/pages/3867312401/Variables+Description#Reference-Disambiguation).

...

• on – The variables it applies to. They can be selected using all or fixed in the same way the inputs of computed variables are selected.

  • group – Defines how to group the selected variables so each group can be ordered.

    • type – The way we decide things are equal (for grouping them); the options are:

      • strict – The standard group by the operation that groups strictly equal things.

        • by – The list of dimensions or data fields to group by.

      • custom – This lets the user define for each feature how to decide if two elements are equal. It is useful to group things that are similar rather than strictly equal. It only works with doubles.

        • by – The list of dimensions or data fields to group by with instructions on how to group them.

          • feature – A dimension that is parsable to a double or a data field that contains a double.

          • type – The type of equality for this feature, either strict or approximate (strict will be used if no type is specified). In the case of approximate, the user has to set the parameter tolerance_as_amount or tolerance_as_rate to define the approximation as needed.

  • comparator – The comparator that defines the order.

    • type – There are three types currently available:

      • inc_natural_order – Increasing natural order over dimension or data field of any type.

      • dec_natural order – Decreasing natural order over strings dimension or data field of any type.

      • explicit – the user explicitly states the order within a list.

        • E.g. if you want to order prices by their color where blue is the lowest and red is the highest, then state the following order: ["blue", "red"].

        • This order can either be defined inline or through data in the alignment’s scope.

          • By using data, you can specify partial orders with a different min_gap for each.

      • Two other types of comparators exist but are deprecated:

        • double_inc_natural_order – Increasing natural order over string-typed dimension or data field that will be cast to double.

        • double_dec_natural_order – Decreasing natural order over string-typed dimension or data field that will be cast to double.

    • over – The feature over which the comparator is applied. It is usually a dimension, but it can be any data field in the scope where the variables are selected.

• The minimum gap between two consecutive variables is required. There are two options:

  • min_gap_as_amount if the gap is expressed as a fixed amount.

    • E.g. applied to A<B<C: A + min_gap_as_amount < B & B + min_gap_as_amount < C

  • min_gap_as_rate if the gap is expressed as a rate of the previous variable in the alignment.

    • E.g. applied to A<B<C: A + A*min_gap_as_rate < B & B + B*min_gap_as_rate < C

  • Each can be defined inline or through data.

• priority – low, medium, or high.

...

Equality

...

⚠️ Equality criteria are deprecated and will be removed from OE v5 onward. The best solution to replace them is to explicitly describe a Standard Deviation computed variable over all the desired input variables and apply a target criterion (equals to zero) to the standard deviation.

...

It is important to keep https://pricefx.atlassian.net/wiki/spaces/KB/pages/3866755214/Criteria+Description#Multi-Variable-Criteria-Rules in mind.

...

• on – The variables it applies to. They can be selected using all or fixed in the same way the inputs of the computed variables are selected.

  • group – Defines the groups within which the variables should be equal. This can be omitted if you want all the selected variables to be equal to each other. Works in the same way as with the Alignment criterion.

• precision – The expected precision of the equality. It should be set with technical or domain-related limitations in mind, it has nothing to do with a user being okay with the criterion not being exactly met.

  • Equality with a precision of 0.1 will be considered satisfied if the difference between the variables is in ]-0.1; 0.1[.

  • Usually, we set the precision to half the smallest relevant amount of change for the variable.

    • E.g. half a cent for a variable in Euros.

• acceptable_delta – The acceptable margin of error. It is related to the end-users' tolerance to error.

  • Equality with an acceptable delta of 0.5 will be considered acceptable (but not satisfied) if the difference between the variables is in [-0.5,-precision[ U ]+precision, +0.5].

• priority – low, medium, or high.

...