Version: | 1.0.0 |
---|---|
Provider: | PUT |
SOAP service’s name: | |
PROMETHEE-FlowSort-GDSS_assignments-PUT (see SOAP requests for details) |
Computes group class assignment for given data using FlowSortGDSS method.
Contact: Maciej Uniejewski <maciej.uniejewski@gmail.com>
(For outputs, see below)
Criteria to consider.
The input value should be a valid XMCDA document whose main tag is <criteria>
.
Alternatives to consider.
The input value should be a valid XMCDA document whose main tag is <alternatives>
.
Definitions of categories.
The input value should be a valid XMCDA document whose main tag is <categories>
.
The performances of profiles for decision maker 1.
The input value should be a valid XMCDA document whose main tag is <performanceTable>
.
The preference matrix computed for profiles and alternatives given by decision maker 1.
The input value should be a valid XMCDA document whose main tag is <alternativesMatrix>
.
Normalised flows of given alternatives for decision maker 1.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>
.
Definitions of boundary profiles for decision maker 1, which should be used for classes (categories) representation.
The input value should be a valid XMCDA document whose main tag is <categoriesProfiles>
.
The performances of profiles for decision maker 2.
The input value should be a valid XMCDA document whose main tag is <performanceTable>
.
The preference matrix computed for profiles and alternatives given by decision maker 2.
The input value should be a valid XMCDA document whose main tag is <alternativesMatrix>
.
Normalised flows of given alternatives for decision maker 2.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>
.
Definitions of boundary profiles for decision maker 2, which should be used for classes (categories) representation.
The input value should be a valid XMCDA document whose main tag is <categoriesProfiles>
.
The performances of profiles for decision maker 3.
The input value should be a valid XMCDA document whose main tag is <performanceTable>
.
The preference matrix computed for profiles and alternatives given by decision maker 3.
The input value should be a valid XMCDA document whose main tag is <alternativesMatrix>
.
Normalised flows of given alternatives for decision maker 3.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>
.
Definitions of boundary profiles for decision maker 3, which should be used for classes (categories) representation.
The input value should be a valid XMCDA document whose main tag is <categoriesProfiles>
.
The performances of profiles for decision maker 4.
The input value should be a valid XMCDA document whose main tag is <performanceTable>
.
The preference matrix computed for profiles and alternatives given by decision maker 4.
The input value should be a valid XMCDA document whose main tag is <alternativesMatrix>
.
Normalised flows of given alternatives for decision maker 4.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>
.
Definitions of boundary profiles for decision maker 4, which should be used for classes (categories) representation.
The input value should be a valid XMCDA document whose main tag is <categoriesProfiles>
.
The performances of profiles for decision maker 5.
The input value should be a valid XMCDA document whose main tag is <performanceTable>
.
The preference matrix computed for profiles and alternatives given by decision maker 5.
The input value should be a valid XMCDA document whose main tag is <alternativesMatrix>
.
Normalised flows of given alternatives for decision maker 5.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>
.
Definitions of boundary profiles for decision maker 5, which should be used for classes (categories) representation.
The input value should be a valid XMCDA document whose main tag is <categoriesProfiles>
.
The performances of profiles for decision maker 6.
The input value should be a valid XMCDA document whose main tag is <performanceTable>
.
The preference matrix computed for profiles and alternatives given by decision maker 6.
The input value should be a valid XMCDA document whose main tag is <alternativesMatrix>
.
Normalised flows of given alternatives for decision maker 6.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>
.
Definitions of boundary profiles for decision maker 6, which should be used for classes (categories) representation.
The input value should be a valid XMCDA document whose main tag is <categoriesProfiles>
.
The performances of profiles for decision maker 7.
The input value should be a valid XMCDA document whose main tag is <performanceTable>
.
The preference matrix computed for profiles and alternatives given by decision maker 7.
The input value should be a valid XMCDA document whose main tag is <alternativesMatrix>
.
Normalised flows of given alternatives for decision maker 7.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>
.
Definitions of boundary profiles for decision maker 7, which should be used for classes (categories) representation.
The input value should be a valid XMCDA document whose main tag is <categoriesProfiles>
.
The performances of profiles for decision maker 8.
The input value should be a valid XMCDA document whose main tag is <performanceTable>
.
The preference matrix computed for profiles and alternatives given by decision maker 8.
The input value should be a valid XMCDA document whose main tag is <alternativesMatrix>
.
Normalised flows of given alternatives for decision maker 8.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>
.
Definitions of boundary profiles for decision maker 8, which should be used for classes (categories) representation.
The input value should be a valid XMCDA document whose main tag is <categoriesProfiles>
.
The performances of profiles for decision maker 9.
The input value should be a valid XMCDA document whose main tag is <performanceTable>
.
The preference matrix computed for profiles and alternatives given by decision maker 9.
The input value should be a valid XMCDA document whose main tag is <alternativesMatrix>
.
Normalised flows of given alternatives for decision maker 9.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>
.
Definitions of boundary profiles for decision maker 9, which should be used for classes (categories) representation.
The input value should be a valid XMCDA document whose main tag is <categoriesProfiles>
.
The performances of profiles for decision maker 10.
The input value should be a valid XMCDA document whose main tag is <performanceTable>
.
The preference matrix computed for profiles and alternatives given by decision maker 10.
The input value should be a valid XMCDA document whose main tag is <alternativesMatrix>
.
Normalised flows of given alternatives for decision maker 10.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>
.
Definitions of boundary profiles for decision maker 10, which should be used for classes (categories) representation.
The input value should be a valid XMCDA document whose main tag is <categoriesProfiles>
.
Scales of considered criteria.
The input value should be a valid XMCDA document whose main tag is <criteriaScales>
.
Normalised flows of given profiles counted for all decision makers together.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>
.
Scales of considered criteria.
The input value should be a valid XMCDA document whose main tag is <criteriaScales>
.
Normalised flows of given profiles counted for all decision makers together.
The input value should be a valid XMCDA document whose main tag is <alternativesValues>
.
Marks of categories (higher mark means better category). Each category need to have unique mark from 1 to C, where C is a number of categories.
The input value should be a valid XMCDA document whose main tag is <categoriesValues>
.
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:
<programParameters>
<parameter id="comparisonWithProfiles">
<values>
<value>
<label>%1</label>
</value>
</values>
</parameter>
<parameter id="assignToABetterClass">
<values>
<value>
<boolean>%2</boolean>
</value>
</values>
</parameter>
<parameter id="decisionMaker1">
<values>
<value>
<real>%3</real>
</value>
</values>
</parameter>
<parameter id="decisionMaker2">
<values>
<value>
<real>%4</real>
</value>
</values>
</parameter>
<parameter id="decisionMaker3">
<values>
<value>
<real>%5</real>
</value>
</values>
</parameter>
<parameter id="decisionMaker4">
<values>
<value>
<real>%6</real>
</value>
</values>
</parameter>
<parameter id="decisionMaker5">
<values>
<value>
<real>%7</real>
</value>
</values>
</parameter>
<parameter id="decisionMaker6">
<values>
<value>
<real>%8</real>
</value>
</values>
</parameter>
<parameter id="decisionMaker7">
<values>
<value>
<real>%9</real>
</value>
</values>
</parameter>
<parameter id="decisionMaker8">
<values>
<value>
<real>%10</real>
</value>
</values>
</parameter>
<parameter id="decisionMaker9">
<values>
<value>
<real>%11</real>
</value>
</values>
</parameter>
<parameter id="decisionMaker10">
<values>
<value>
<real>%12</real>
</value>
</values>
</parameter>
</programParameters>
where:
%1 is a parameter named “comparison with profiles”. It can have the following values:
central
: central profilesbounding
: boundary profilesThe default value is central.
%2 is a parameter named “assign to a better class”. This is a boolean. The default value is true.
%3 is a parameter named “decision maker 1 weight”. This is a float, and the value should conform to the following constraint: A float value.. More formally, the constraint is:
%3 >= 0
The default value is 0.0.
%4 is a parameter named “decision maker 2 weight:”. This is a float, and the value should conform to the following constraint: A float value.. More formally, the constraint is:
%4 >= 0
The default value is 0.0.
%5 is a parameter named “decision maker 3 weight:”. This is a float, and the value should conform to the following constraint: A float 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 4 weight”. This is a float, and the value should conform to the following constraint: A float 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 5 weight”. This is a float, and the value should conform to the following constraint: A float 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 6 weight”. This is a float, and the value should conform to the following constraint: A float 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 7 weight”. This is a float, and the value should conform to the following constraint: A float 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 8 weight”. This is a float, and the value should conform to the following constraint: A float value. Choose 0.0 when decision maker does not exist.. More formally, the constraint is:
%10 >= 0
The default value is 0.0.
%11 is a parameter named “decision maker 9 weight”. This is a float, and the value should conform to the following constraint: A float value. Choose 0.0 when decision maker does not exist.. More formally, the constraint is:
%11 >= 0
The default value is 0.0.
%12 is a parameter named “decision maker 10 weight”. This is a float, and the value should conform to the following constraint: A float value. Choose 0.0 when decision maker does not exist.. More formally, the constraint is:
%12 >= 0
The default value is 0.0.
Assignments made in a first step of FlowSortGDSS process. They shows for which alternatives decision makers were not able to make an unanimous assignment.
The returned value is a XMCDA document whose main tag is <alternativesAssignments>
.
Final assignments made in a FlowSortGDSS process.
The returned value is a XMCDA document whose main tag is <alternativesAssignments>
.
Messages or errors generated by this module.
The returned value is a XMCDA document whose main tag is <programExecutionResult>
.