Version: | 1.0.0 |
---|---|
Provider: | PUT |
Name: | PROMETHEE_preference-reinforcedPreference |
SOAP service’s name: | |
PROMETHEE_preference-reinforcedPreference-PUT (see SOAP requests for details) |
Computes aggregated preference indices with reinforced preference effect
This module is an extended version of ‘PrometheePreference’ - it brings the concept of ‘reinforced_preference’, which boils down to the new threshold of the same name and a new input file where the ‘reinforcement factors’ are defined (one for each criterion where ‘reinforced_preference’ threshold is present).
Web page: https://github.com/Yamadads/PrometheeDiviz
Reference: Bernard Roy and Roman Slowinski; Handling effects of reinforced preference and counter-veto in credibility of outranking; European Journal of Operational Research 188(1):185?190; 2008; doi:10.1016/j.ejor.2007.04.005
(For outputs, see below)
Criteria to consider, possibly with ‘preference’, ‘indifference’ and ‘reinforced preference’ thresholds (see also ‘reinforcement_factors’ input below). Each criterion must have a preference direction specified (min or max). It is worth mentioning that this module allows to define thresholds as constants as well as linear functions.
The input value should be a valid XMCDA document whose main tag is <criteria>
.
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>
.
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>
.
Definitions of so-called ‘reinforcement factors’, one per each criterion for which ‘reinforcement threshold’ has been defined. For more regarding these concepts see the paper from ‘Reference’ section.
This input is mandatory, if you don’t need the concept of reinforced preference please use ‘PrometheePreference’.
The input value should be a valid XMCDA document whose main tag is <criteriaValues>
.
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.
The input value should be a valid XMCDA document whose main tag is <methodParameters>
.
It must have the following form:
<methodParameters>
<parameter name="comparison_with">
<value>
<label>%1</label>
</value>
</parameter>
<parameter name="generalised_criterion">
<value>
<label>%2</label>
</value>
</parameter>
</methodParameters>
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-in
: V-Shape with Indifference Criterion, needs both indifference and strict preference thresholds specified in criterion.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 <alternativesComparisons>
.
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 <alternativesComparisons>
.
Messages or errors generated by this module.
The returned value is a XMCDA document whose main tag is <methodMessages>
.