Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • A criterion declared in the criteria section of one scope is instantiated for each set of coordinates within the scope. Their names act as keys for coordinates inside their space, thus two criteria at the same coordinates cannot share the same name. This means two mutually exclusive scopes can define the same criterion in two different ways. An example with variables is given in https://pricefx.atlassian.net/wiki/spaces/UDEV/pages/3867312401/Variables+Definition#General-Rules Variables Description.

  • Every parameter can either be set directly inline or through data.

    • In the case of an inline type, the description provides a value. It is the way to provide a hard-coded value or a user-entry value.

    • In the case of a data type, the description provides a field name. The instantiation will seek in the problem table corresponding to the scope, named Problem_<name of the space>_<name of the scope> to get the values, which depend on the coordinates of the criteria.

  • After (and during) an optimization run, a criterion is:

    • SATISFIED if the constraint expressed by the criterion is met.

    • ACCEPTABLE if it is within its acceptable margin of error.

    • UNACCEPTABLE otherwise.

  • You can set priorities for criteria: low, medium, or high.

    • Higher priority unacceptable criteria are treated first in case of conflict, but the system will always try to solve every criterion.

...

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 https://pricefx.atlassian.net/wiki/spaces/UDEV/pages/3867312401/Variables+Definition#Referencing-Other-Spaces 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.

Be aware that, in practice, a multi-variable criterion is a composite criterion: the OE will instantiate several single-variable criteria, applied on hidden computed variables. For instance, for an alignment criterion between A, B, and C, the OE creates two computed variables (A minus B, and B minus C), and applies a threshold to zero to each of them. When looking at the results, the state of a multi-variable criterion is the worst state among its single-variable criteria.

Alignment Criteria

...

It is ⚠️ 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).

For instance, a product price alignment would be described in a [reference: product, following: product] space containing:

  • A computed variable that is the difference between “reference product” price and “following product” price.

  • A threshold criteria on that difference that expresses the desired alignment between both prices.

This way it offers a lot more flexibility than using the built-in alignment criteria.

...

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

...

Appsplus tabs lite macro
data{"theme":"custom","features":["titles","active","border","rounded","ripples","fullscreen"],"padding":10,"height":1350,"tabFont":"Atlassian","tabSize":15,"tabBold":true,"tabItalic":false,"tabUnderline":false,"tabColor":"#ffffff","tabColorBG":"#172b4d","type":"scrollable","opacity":100,"activeColor":"#ffffff","activeColorBG":"#0052cc","borderWidth":1,"borderColor":"#ebecf0","radius":5,"hoverColor":"#ffffff","hoverColorBG":"#0052cc","iconSize":"medium","iconInline":true,"iconPrimary":"#ffffff","iconSecondary":"#172b4d","separatorWidth":1,"separatorColor":"#42526E","indicatorPercent":5,"indicatorColor":"#ff5630","indicatorColorBG":"#0052cc","hide":false,"vertical":false,"preload":true,"animate":false,"uuid":"RunjbCTdw1","isNew":false,"loaded":false,"attachmentId":"att4244799568"}

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.

...