| Version: | 1.0 |
|---|---|
| Provider: | PyXMCDA |
| SOAP service’s name: | |
weightsFromCondorcetAndPreferences-PyXMCDA (see SOAP requests for details) |
|
This web service allows to compute criteria significance weights from pairwise outranking comparisons, taking into account some robust properties. For ordered pairs a decision maker would ensure a strong outranking, the web service grants, if possible, that the outranking remains unchanged when changing the criteria weights, as long as the relative importance between all criteria weights don’t change (a weight greater than another has to stay greater). In addition to weightsFromCondorcetRelation, it allows to model decision-maker’s preferences on criteria, a for example constraints like w1 > w2, w3>w4+w5, w6=3, 2<w7<8, ...
Contact: Veneziano Thomas (thomas.veneziano@uni.lu)
Reference: Bisdorff Raymond, Meyer Patrick, Veneziano Thomas ; Inverse analysis from a Condorcet robustness denotation of valued outranking relations ; ADT 2009 : 1st International Conference on Algorithmic Decision Theory , Lecture Notes in Artificial Intelligence : Springer Verlag, 21-23 october 2009, Venise, Italy, 2009
(For outputs, see below)
Indicates the maximal value a weight can reach
The input value should be a valid XMCDA document whose main tag is <methodParameters>.
It must have the following form:
<methodParameters>
<parameter
name="maxWeight"> <!-- REQUIRED -->
<value>
<integer>%1</integer>
</value>
</parameter>
</methodParameters>
where:
%1 is a parameter named “maxWeight”. This is a int, and the value should conform to the following constraint: The value should be a positive integer.. More formally, the constraint is:
%1 > 0
The input value should be a valid XMCDA document whose main tag is <criteria>.
It must have the following form:
<criteria>
<criterion>
<active>[...]</active>
<thresholds>
<threshold
mcdaConcept="indifference"><!-- REQUIRED, must be indifference, preference or veto -->
<constant><real>[...]</real></constant>
</threshold>
</thresholds>
[...]
</criterion>
[...]
</criteria>
A list of alternatives. Alternatives can be activated or desactivated via the <active> tag (true or false). By default (no <active> tag), alternatives are considered as active.
The input value should be a valid XMCDA document whose main tag is <alternatives>.
It must have the following form:
<alternatives>
<alternative>
<active>[...]</active>
[...]
</alternative>
[...]
</alternatives>
A performance table. The evaluations should be numeric values, i.e. <real>, <integer> or <rational>.
The input value should be a valid XMCDA document whose main tag is <performanceTable>.
The Condorcet denotation for some alternative comparisons. The value associated to each ordered pair (a,b) must be an integer between 3 and -3. Note that all pairs with a value of 3 or -3 will be ignored during the computation phase, as they are trivial constraints.
The input value should be a valid XMCDA document whose main tag is <alternativesComparisons>.
Allows to model criteria weights preferences. For each defined pair in criteriaComparisons, we create a constraint indicating that the sum of the initial criterion (or set of criteria) weights must be greater than those of the terminal criterion (or also set of criteria)
The input value should be a valid XMCDA document whose main tag is <criteriaComparisons>.
It must have the following form:
<criteriaComparisons>
<pair>
<initial><criterionID>[...]</criterionID></initial>
<terminal><criterionID>[...]</criterionID></terminal>
</pair>
<pair>
<initial><criteriaSet>[...]</criteriaSet></initial>
<terminal><criteriaSet>[...]</criteriaSet></terminal>
</pair>
[...]
</criteriaComparisons>
Allows to indicate some criteria lower bounds, i.e. constraints like w(g1) > 3.
The input value should be a valid XMCDA document whose main tag is <criteriaValues>.
It must have the following form:
<criteriaValues>
<criterionValue>
<criterionID>[...]</criterionID>
<value>[...]</value>
</criterionValue>
[...]
</criteriaValues>
Allows to indicate some criteria upper bounds, i.e. constraints like w(g1) < 5. Note that if you want to fix the value of a criteria, just give it some equal lower and upper bounds.
The input value should be a valid XMCDA document whose main tag is <criteriaValues>.
It must have the following form:
<criteriaValues>
<criterionValue>
<criterionID>[...]</criterionID>
<value>[...]</value>
</criterionValue>
[...]
</criteriaValues>
A list of messages generated by the algorithm.
The returned value is a XMCDA document whose main tag is <methodMessages>.
The set of criteria weights generated by the algorithm
The returned value is a XMCDA document whose main tag is <criteriaValues>.