Version: | 1.0.0 |
---|---|
Provider: | PUT |
Name: | PROMETHEE_preference-interactions |
SOAP service’s name: | |
PROMETHEE_preference-interactions-PUT (see SOAP requests for details) |
Computes aggregated preference indices with interactions between criteria The key feature of this module is its flexibility in terms of the types of elements allowed to compare, i.e. alternatives vs alternatives, alternatives vs boundary profiles and alternatives vs central (characteristic) profiles. Each criterion can have its own preference function (one of six predefined functions).
(For outputs, see below)
Criteria to consider.
The input value should be a valid XMCDA document whose main tag is <criteria>
.
Criteria sets used to define interactions. Each set requires exactly two criteria.
The input value should be a valid XMCDA document whose main tag is <criteriaSets>
.
It must have the following form:
<criteriaSets>
<criteriaSet id="criteriaSet_generatedID_1">
<element>
<criterionID>c01</criterionID>
</element>
<element>
<criterionID>c02</criterionID>
</element>
</criteriaSet>
</criteriaSets>
Alternatives to consider.
The input value should be a valid XMCDA document whose main tag is <alternatives>
.
The performance of alternatives.
The input value should be a valid XMCDA document whose main tag is <performanceTable>
.
The performance of profiles (boundary or central).
The input value should be a valid XMCDA document whose main tag is <performanceTable>
.
Preference direction (min or max) specified for each criterion.
The input value should be a valid XMCDA document whose main tag is <criteriaScales>
.
Preference, indifference and sigma thresholds for criteria (as constants as well as linear functions). Gaussian function needs inflection point (sigma), rest of functions need preference or indifference thresholds.
The input value should be a valid XMCDA document whose main tag is <criteriaThresholds>
.
Weights of criteria to consider.
The input value should be a valid XMCDA document whose main tag is <criteriaValues>
.
ID number of predefined preference function specified for each criterion.
The input value should be a valid XMCDA document whose main tag is <criteriaValues>
.
Declarations of criteria interactions which should be taken into account. Possible interactions are: “strengthening”, “weakening” and “antagonistic”.
Every such declaration contains an id of criteria set and its numerical value for the interaction coefficient. This value should be negative for “weakening” and positive for “strenghtening” and “antagonistic”. This coefficient should be interpreted as follows: the larger its absolute value, the more important the interaction effect. All interaction coefficients should fulfill positive net balance condition.
The order in which each criterion appears in its interaction definition is significant for antagonistic interactions (it designates the direction in which certain criterion affects the other). For strengthening and weakening order is not important. (Coefficients k_ij = k_ji and only one of this is needed).
There are no limits on the number of interactions that can be declared, but keep in mind that it should be rather small to make sense.
It is possible to declare more than one interactions of the same type, although please note that considering the same pair of criteria involved, the “strengthening” and “weakening” interactions are mutually exclusive.
The input value should be a valid XMCDA document whose main tag is <criteriaSetsValues>
.
It must have the following form:
<criteriaSetsValues mcdaConcept="criteriaInteractions">
<criteriaSetValue mcdaConcept="strengthening">
<criteriaSetID>criteriaSet_generatedID_1</criteriaSetID>
<values>
<value>
<real>1.5</real>
</value>
</values>
</criteriaSetValue>
</criteriaSetsValues>
Definitions of central or boundary profiles connected with classes (categories)
The input value should be a valid XMCDA document whose main tag is <categoriesProfiles>
.
First parameter specifies the type of elements provided for comparison.
Choosing ‘boundary_profiles’ or ‘central_profiles’ requires providing inputs ‘classes_profiles’ and ‘profiles_performance_table’ as well (which are optional by default).
Second parameter specifies the type of function used for comparison of each criterion. Choosing ‘specified’ requires providing inputs “generalised_criterion” which is optional by default. Choosing some of numbers sets same function for all criteria. Third parameter specifies type of Z function in computing criteria interaction effect.
The input value should be a valid XMCDA document whose main tag is <programParameters>
.
It must have the following form:
<programParameters>
<parameter id="comparison_with" name="comparison_with">
<values>
<value>
<label>%1</label>
</value>
</values>
</parameter>
<parameter id="criterion" name="generalised_criterion">
<values>
<value>
<label>%2</label>
</value>
</values>
</parameter>
<parameter name="z_function" id="z_function">
<values>
<value>
<label>%3</label>
</value>
</values>
</parameter>
</programParameters>
where:
%1 is a parameter named “comparison with”. It can have the following values:
alternatives
: alternatives vs alternativesboundary_profiles
: alternatives vs boundary profilescentral_profiles
: alternatives vs central (characteristic) profilesThe default value is item0.
%2 is a parameter named “generalised criterion”. It can have the following values:
specified
: Each criterion needs its own functionusual
: Usual Criterionu-shape
: U-Shape Criterion, needs indifference threshold specified in criterion.v-shape
: V-Shape Criterion, needs threshold of strict preference specified in criterion.level
: Level Criterion, needs both indifference and strict preference thresholds specified in criterion.v-shape-ind
: V-Shape with Indifference Criterion, needs both indifference and strict preference thresholds specified in criterion.gaussian
: Gaussian Criterion, needs the inflection point of the preference function specified in criterion.The default value is item0.
%3 is a parameter named “z function”. It can have the following values:
multiplication
: Z(x, y) = xyminimum
: Z(x, y) = min{x, y}The default value is item0.
Aggregated preference matrix computed from the given data. This matrix aggregates partial preference indices from all criteria into single preference index per pair of alternatives or alternatives/profiles.
The returned value is a XMCDA document whose main tag is <alternativesMatrix>
.
Preference matrix computed from the given data. This matrix contains partial preference indices for all criteria and all pairs of alternatives or alternatives/profiles.
The returned value is a XMCDA document whose main tag is <alternativesMatrix>
.
Messages or errors generated by this module.
The returned value is a XMCDA document whose main tag is <programExecutionResult>
.