| Version: | 1.1 |
|---|---|
| Provider: | PUT |
| SOAP service’s name: | |
RORUTA-PairwiseOutrankingIndicesHierarchical-PUT (see SOAP requests for details) |
|
Procedure finds a set of matrices of the pair-wise outranking indices for a given problem and a given hierarchy of the criteria. Each matrix describes another node of this hierarchy.
Contact: Pawel Rychly (pawelrychly@gmail.com).
(For outputs, see below)
A list of all considered criteria. The input value should be a valid XMCDA document whose main tag is criteria.
The input value should be a valid XMCDA document whose main tag is <criteria>.
It must have the following form:
<criteria>
<criterion id="%1" name="%1"></criterion>
[...]
</criteria>
The list of all considered alternatives. The input value should be a valid XMCDA document whose main tag is alternatives. Each alternative may be described using two attributes: id and name. While the first one denotes a machine readable name, the second represents a human readable name.
The input value should be a valid XMCDA document whose main tag is <alternatives>.
It must have the following form:
<alternatives>
<alternative id="%1" name="%2" />
[...]
</alternatives>
Description of the hierarchical structure of criteria. Each node of this hierarchy needs to have a unique id attribute. The most nested nodes, should contain a set of criteria. The input value should be provided as a valid XMCDA document whose main tag is hierarchy
The input value should be a valid XMCDA document whose main tag is <hierarchy>.
It must have the following form:
<hierarchy>
<node id="nodes">
<node id="nodes1">
<criteriaSet>
<element><criterionID>%1</criterionID></element> [...]
</criteriaSet>
</node>
[...]
</node>
[...]
</hierarchy>
Description of evaluation of alternatives on different criteria. It is required to provide the IDs of both criteria and alternatives described previously. The input value should be provided as a valid XMCDA document whose main tag is performanceTable
The input value should be a valid XMCDA document whose main tag is <performanceTable>.
It must have the following form:
<performanceTable>
<alternativePerformances>
<alternativeID>%1</alternativeID>
<performance>
<criterionID>%2</criterionID>
<value>
<real>%3</real>
</value>
</performance>
[...]
</alternativePerformances>
[...]
</performanceTable>
A set of values associated with the criteria. This input allows to determine what type of value function should be used for the particular criterion. For each criterion that has an associated greater than one value, a piecewise linear value function is used. In this case, the mentioned value denotes a number of characteristic points of this value function. For the criteria that are not listed in this file, or for these for which the provided values are lower than two uses a general value function. The input value should be provided as a valid XMCDA document whose main tag is criteriaValues. Each element should contain both an id of the criterion, and value tag.
The input value should be a valid XMCDA document whose main tag is <criteriaValues>.
It must have the following form:
<criteriaValues>
<criterionValue>
<criterionID>%1</criterionID>
<value>
<integer>%2</integer>
</value>
</criterionValue>
[...]
</criteriaValues>
A set of values associated with criteria that determine their preference direction (0 - gain, 1 - cost).
The input value should be a valid XMCDA document whose main tag is <criteriaValues>.
It must have the following form:
<criteriaValues mcdaConcept="preferenceDirection">
<criterionValue>
<criterionID>%1</criterionID>
<value>
<integer>%2</integer>
</value>
</criterionValue>
[...]
</criteriaValues>
Set of pairwise comparisons of reference alternatives. For a pair of alternatives three types of comparisons are supported. These are the strict preference, weak preference, and indifference. Values linked to pairs indicate ids of nodes in the hierarchy of criteria tree. If value is not given or if it is equal to 0 pairwise comparison is assumed to concern for the whole set of criteria. Otherwise, the preference relation applies only to a particular node. The input value should be provided as a valid XMCDA document whose main tag is alternativesComparisons. For each type of comparison, a separate alternativesComparisons tag should be used. Within these groups a mentioned types are denoted using a comparisonType tag by respectively strict, weak, and indif label. Comparisons should be provided as pairs of alternatives ids.
The input value should be a valid XMCDA document whose main tag is <alternativesComparisons>.
It must have the following form:
<alternativesComparisons>
<comparisonType>
%1<!-- type of preference: strong, weak, or indif -->
</comparisonType>
<pairs>
<pair>
<initial>
<alternativeID>%2</alternativeID>
</initial>
<terminal>
<alternativeID>%3</alternativeID>
</terminal>
<value>
<label>%4</label>
</value>
</pair>
[...]
</pairs>
</alternativesComparisons>
Set of comparisons of intensities of preference. For a pair of preference relations three types of comparisons are supported. These are the strict preference, weak preference, and indifference. Values linked to pairs, determine ids of nodes in the hierarchy of criteria tree. If value is not given or if it is equal to 0 intensity of preference is assumed to concern for the whole set of criteria. Otherwise, the statement applies only to a particular node. The input value should be provided as a valid XMCDA document whose main tag is alternativesComparisons. For each type of comparison, a separate alternativesComparisons tag should be used. Within these groups aforementioned types are denoted using a comparisonType tag by respectively strict, weak, and indif label. Comparisons should be provided as pairs of two elementary sets of alternatives ids. The following form is expected:
The input value should be a valid XMCDA document whose main tag is <alternativesComparisons>.
It must have the following form:
<alternativesComparisons>
<comparisonType>
%1<!-- type of preference: strong, weak, or indif -->
</comparisonType>
<pairs>
<pair>
<initial>
<alternativesSet>
<element>
<alternativeID>%2</alternativeID>
</element>
<element>
<alternativeID>%3</alternativeID>
</element>
</alternativesSet>
</initial>
<terminal>
<alternativesSet>
<element>
<alternativeID>%4</alternativeID>
</element>
<element>
<alternativeID>%5</alternativeID>
</element>
</alternativesSet>
</terminal>
<value>
<label>%6</label>
</value>
</pair>
</pairs>
</alternativesComparisons>
The input value should be a valid XMCDA document whose main tag is <methodParameters>.
It must have the following form:
<methodParameters>
<parameter name="strict">
<value>
<boolean>%1</boolean>
</value>
</parameter>
<parameter name="number-of-samples">
<value>
<integer>%2</integer>
</value>
</parameter>
</methodParameters>
where:
%1 is a parameter named “Use strictly increasing value functions?”. This is a boolean. The default value is false.
%2 is a parameter named “Number of samples that are used to generate a result”. This is a int, and the value should conform to the following constraint: An integer greater than zero value that denotes a number of samples generated by an algorithm.. More formally, the constraint is:
(%2 > 0)
The default value is 100.
A list of all pairwise outranking indices. The returned value is an XMCDA document whose main tag is alternativesComparisons. Each node of the hierarchy should be described by another alternativesComparisons tag. The id of node should be marked in the id attribute of these tag.
The returned value is a XMCDA document whose main tag is <alternativesComparisons>.
It has the following form:
<alternativesComparisons id=%1>
<pairs>
<pair>
<initial>
<alternativeID>[...]</alternativeID>
</initial>
<terminal>
<alternativeID>[...]</alternativeID>
</terminal>
<value>
<real>[...]</real>
</value>
</pair>
[...]
</pairs>
</alternativesComparisons>
A list of messages generated by the algorithm.
The returned value is a XMCDA document whose main tag is <methodMessages>.