| Version: | 1.0 |
|---|---|
| Provider: | PUT |
| SOAP service’s name: | |
HierarchicalDEA-CCR-SMAA_preferenceRelations-PUT (see SOAP requests for details) |
|
Determines dominance relations for the given DMUs (alternatives) using SMAA-D method and CCR Data Envelopment Analysis Model with hierarchical structure of outputs. For given number of samples returns a matrix with alternatives in each row and column. Single cell indicates how many samples of alternative in a row dominates alternative in a column.
(For outputs, see below)
A list of alternatives (DMUs).
The input value should be a valid XMCDA document whose main tag is <alternatives>.
It must have the following form:
<alternatives>
<alternative>
[...]
</alternative>
[...]
</alternatives>
A list of alternatives (DMUs) performances (on leaf hierarchy criteria).
The input value should be a valid XMCDA document whose main tag is <performanceTable>.
It must have the following form:
<performanceTable>
<alternativePerformances>
<alternativeID> [...] </alternativeID>
<performance>
<criterionID>
[...]
</criterionID>
<value>[...]</value>
</performance>
[...]
</alternativePerformances>
[...]
</performanceTable>
The hierarchical structure of criteria.
The input value should be a valid XMCDA document whose main tag is <hierarchy>.
It must have the following form:
<hierarchy>
<node>
<criterionID>[...]</criterionID>
<node>
<criterionID>[...]</criterionID>
<node>
[...]
</node>
[...]
</node>
[...]
</node>
</hierarchy>
A list of hierarchy criteria linear constraints.
The input value should be a valid XMCDA document whose main tag is <criteriaLinearConstraints>.
It must have the following form:
<criteriaLinearConstraints>
<constraint>
<element>
<criterionID> [...] </criterionID>
<coefficient>
[...]
</coefficient>
</element>
[...]
<operator>[...]</operator>
<rhs>
[...]
</rhs>
</constraint>
[...]
</criteriaLinearConstraints>
“number of samples” represents the number of samples to generate; “hierarchy node” is the ID of the hierarchy criterion for which the analysis should be performed.
The input value should be a valid XMCDA document whose main tag is <methodParameters>.
It must have the following form:
<methodParameters>
<parameter id="samplesNb">
<value><integer>%1</integer></value>
</parameter>
<parameter id="hierarchyNode">
<value><label>%3</label></value>
</parameter>
<parameter id="randomSeed">
<value><integer>%4</integer></value>
</parameter>
</methodParameters>
where:
%1 is a parameter named “number of samples”. 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 default value is 100.
%3 is a parameter named “hierarchy node”. This is a string. The default value is root.
%4 is a parameter named “random seed (-1 for default time-based seed)”. This is a int, and the value should conform to the following constraint: The value should be a non-negative integer or -1 if no constant seed required.. More formally, the constraint is:
%4 >= -1
The default value is -1.
A performance table for given alternatives. Single performance consists of attribute criterionID representing dominated alternative, and a value representing ratio of samples dominating this alternative.
The returned value is a XMCDA document whose main tag is <performanceTable>.
It has the following form:
<performanceTable>
<alternativePerformances>
<alternativeID> [...] </alternativeID>
<performance>
<criterionID> geq [...]</criterionID>
<value>
[...]
</value>
</performance>
[...]
</alternativePerformances>
</performanceTable>
A list of messages generated by the algorithm.
The returned value is a XMCDA document whose main tag is <methodMessages>.