| Version: | 1.0.0 |
|---|---|
| Provider: | PUT |
| SOAP service’s name: | |
PROMETHEE-II-GDSS_flows-PUT (see SOAP requests for details) |
|
Module for calculation PROMETHEE group ranking as a weighted sum of flows from every decision maker for each alternative.
Contact: Magdalena Dziecielska <magdalenadziecielska6@gmail.com>
Web page: https://github.com/MagdalenaDziecielska/PrometheeDiviz
Reference: C. Macharis, J.-P. Brans and B. Mareschal, 1998. The GDSS PROMETHEE Procedure. Journal of Decision Systems, Vol. 7-SI/1998, 283-307.
(For outputs, see below)
Alternatives to consider.
The input value should be a valid XMCDA document whose main tag is <alternatives>.
Flows for decision maker 1.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>.
Flows for decision maker 2.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>.
Flows for decision maker 3.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>.
Flows for decision maker 4.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>.
Flows for decision maker 5.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>.
Flows for decision maker 6.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>.
Flows for decision maker 7.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>.
Flows for decision maker 8.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>.
Flows for decision maker 9.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>.
Flows for decision maker 10.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>.
Number of decision makers (2-10)
The input value should be a valid XMCDA document whose main tag is <parameter>.
It must have the following form:
%1
where:
%1 is a parameter named “Number of decision makers”. This is a int, and the value should conform to the following constraint: An integer value between 2 and 10 (inclusive).. More formally, the constraint is:
%1 >= 2 && %1 <= 10
The default value is 2.
A set of parameters provided to tune up the module’s operation.
The input value should be a valid XMCDA document whose main tag is <programParameters>.
It must have the following form:
<parameter id="decisionMaker1">
<value>
<real>%1</real>
</value>
</parameter>
<parameter id="decisionMaker2">
<value>
<real>%2</real>
</value>
</parameter>
<parameter id="decisionMaker3">
<value>
<real>%3</real>
</value>
</parameter>
<parameter id="decisionMaker4">
<value>
<real>%4</real>
</value>
</parameter>
<parameter id="decisionMaker5">
<value>
<real>%5</real>
</value>
</parameter>
<parameter id="decisionMaker6">
<value>
<real>%6</real>
</value>
</parameter>
<parameter id="decisionMaker7">
<value>
<real>%7</real>
</value>
</parameter>
<parameter id="decisionMaker8">
<value>
<real>%8</real>
</value>
</parameter>
<parameter id="decisionMaker9">
<value>
<real>%9</real>
</value>
</parameter>
<parameter id="decisionMaker10">
<value>
<real>%10</real>
</value>
</parameter>
</programParameters>
where:
%1 is a parameter named “decision maker 1 weight”. This is a float, and the value should conform to the following constraint: An integer value.. More formally, the constraint is:
%1 >= 0
The default value is 0.0.
%2 is a parameter named “decision maker 2 weight:”. This is a float, and the value should conform to the following constraint: An integer value.. More formally, the constraint is:
%2 >= 0
The default value is 0.0.
%3 is a parameter named “decision maker 3 weight:”. This is a float, and the value should conform to the following constraint: An integer value. Choose 0.0 when decision maker does not exist.. More formally, the constraint is:
%3 >= 0
The default value is 0.0.
%4 is a parameter named “decision maker 4 weight”. This is a float, and the value should conform to the following constraint: An integer value. Choose 0.0 when decision maker does not exist.. More formally, the constraint is:
%4 >= 0
The default value is 0.0.
%5 is a parameter named “decision maker 5 weight”. This is a float, and the value should conform to the following constraint: An integer value. Choose 0.0 when decision maker does not exist.. More formally, the constraint is:
%5 >= 0
The default value is 0.0.
%6 is a parameter named “decision maker 6 weight”. This is a float, and the value should conform to the following constraint: An integer value. Choose 0.0 when decision maker does not exist.. More formally, the constraint is:
%6 >= 0
The default value is 0.0.
%7 is a parameter named “decision maker 7 weight”. This is a float, and the value should conform to the following constraint: An integer value. Choose 0.0 when decision maker does not exist.. More formally, the constraint is:
%7 >= 0
The default value is 0.0.
%8 is a parameter named “decision maker 8 weight”. This is a float, and the value should conform to the following constraint: An integer value. Choose 0.0 when decision maker does not exist.. More formally, the constraint is:
%8 >= 0
The default value is 0.0.
%9 is a parameter named “decision maker 9 weight”. This is a float, and the value should conform to the following constraint: An integer value. Choose 0.0 when decision maker does not exist.. More formally, the constraint is:
%9 >= 0
The default value is 0.0.
%10 is a parameter named “decision maker 10 weight”. This is a float, and the value should conform to the following constraint: An integer value. Choose 0.0 when decision maker does not exist.. More formally, the constraint is:
%10 >= 0
The default value is 0.0.
Aggregated flows and weights for decision makers.
The returned value is a XMCDA document whose main tag is <alternativesMatrix>.
Final group ranking
The returned value is a XMCDA document whose main tag is <alternativesMatrix>.
Messages or errors generated by this module.
The returned value is a XMCDA document whose main tag is <programExecutionResult>.