Version: | 0.5.5 |
---|---|
Provider: | J-MCDA |
SOAP service’s name: | |
ElectreTriExploitation-J-MCDA (see SOAP requests for details) |
Computes assignments according to the Electre TRI procedure.
Contact: Olivier Cailloux <olivier.cailloux@ecp.fr>
Web page: http://sourceforge.net/projects/j-mcda/
Reference: None
(For outputs, see below)
The alternatives to consider. Set some alternatives as inactive (or remove them) to ignore them.
The input value should be a valid XMCDA document whose main tag is <alternatives>
.
The criteria to consider, possibly with preference, indifference and veto thresholds. Each one must have a preference direction. Set some criteria as inactive (or remove them) to ignore them.
The input value should be a valid XMCDA document whose main tag is <criteria>
.
The criteria to consider, possibly with preference, indifference and veto thresholds. Each one must have a preference direction. Set some criteria as inactive (or remove them) to ignore them.
The input value should be a valid XMCDA document whose main tag is <criteriaScales>
.
The criteria to consider, possibly with preference, indifference and veto thresholds. Each one must have a preference direction. Set some criteria as inactive (or remove them) to ignore them.
The input value should be a valid XMCDA document whose main tag is <criteriaThresholds>
.
The profiles of the categories in which alternatives are to be sorted.
The input value should be a valid XMCDA document whose main tag is <categoriesProfiles>
.
The weights of the criteria to consider.
The input value should be a valid XMCDA document whose main tag is <criteriaValues>
.
The performances of the alternatives.
The input value should be a valid XMCDA document whose main tag is <performanceTable>
.
The performances of the profiles.
The input value should be a valid XMCDA document whose main tag is <performanceTable>
.
The majority threshold specifying where to cut the outranking relation.
The input value should be a valid XMCDA document whose main tag is <programParameters>
.
It must have the following form:
<programParameters>
<programParameter>
<values>
<value>
<real>%1</real>
</value>
</values>
</programParameter>
</programParameters>
where:
The type of sorting to use (optimistic, pessimistic or both).
The input value should be a valid XMCDA document whose main tag is <methodParameters>
.
It must have the following form:
<programParameters>
<programParameter>
<values>
<value>
<label>%1</label>
</value>
</values>
</programParameter>
</programParameters>
where:
%1 is a parameter named “sorting_mode”. It can have the following values:
OPTIMISTIC
: Optimistic sorting.PESSIMISTIC
: Pessimistic sorting.BOTH
: Sorting both optimistic and pessimistic.The default value is item0.
Whether the veto thresholds are considered crisp (or binary). If true, a veto either has full effect (when the performance is low enough for the veto to activate) or no effect at all. Defaults to false, thus the vetoes may have partial effect, as in the original Electre Tri description.
The input value should be a valid XMCDA document whose main tag is <programParameters>
.
It must have the following form:
<programParameters>
<programParameter>
<values>
<value>
<boolean>%1</boolean>
</value>
</values>
</programParameter>
</programParameters>
where:
The affectations of the alternatives computed from the given input data.
The returned value is a XMCDA document whose main tag is <alternativesAffectations>
.
A status message.
The returned value is a XMCDA document whose main tag is <methodMessages>
.