PROMETHEE-FlowSort-GDSS_assignments

Version:1.0.0
Provider:PUT
SOAP service’s name:
 PROMETHEE-FlowSort-GDSS_assignments-PUT (see SOAP requests for details)

Description

Computes group class assignment for given data using FlowSortGDSS method.

Contact: Maciej Uniejewski <maciej.uniejewski@gmail.com>

Web page: https://github.com/maciej7777/PrometheeDiviz

Inputs

(For outputs, see below)

criteria

Criteria to consider and their scales

The input value should be a valid XMCDA document whose main tag is <criteria>.

alternatives

Alternatives to consider.

The input value should be a valid XMCDA document whose main tag is <alternatives>.

categories

Definitions of categories.

The input value should be a valid XMCDA document whose main tag is <categories>.

performance_table1

The performances of profiles for decision maker 1.

The input value should be a valid XMCDA document whose main tag is <performanceTable>.

preferences1

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 <alternativesComparisons>.

flows1

Normalised flows of given alternatives for decision maker 1.

The input value should be a valid XMCDA document whose main tag is <alternativesValues>.

categories_profiles1

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>.

performance_table2

The performances of profiles for decision maker 2.

The input value should be a valid XMCDA document whose main tag is <performanceTable>.

preferences2

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 <alternativesComparisons>.

flows2

Normalised flows of given alternatives for decision maker 2.

The input value should be a valid XMCDA document whose main tag is <alternativesValues>.

categories_profiles2

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>.

performance_table3 (optional)

The performances of profiles for decision maker 3.

The input value should be a valid XMCDA document whose main tag is <performanceTable>.

preferences3 (optional)

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 <alternativesComparisons>.

flows3 (optional)

Normalised flows of given alternatives for decision maker 3.

The input value should be a valid XMCDA document whose main tag is <alternativesValues>.

categories_profiles3 (optional)

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>.

performance_table4 (optional)

The performances of profiles for decision maker 4.

The input value should be a valid XMCDA document whose main tag is <performanceTable>.

preferences4 (optional)

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 <alternativesComparisons>.

flows4 (optional)

Normalised flows of given alternatives for decision maker 4.

The input value should be a valid XMCDA document whose main tag is <alternativesValues>.

categories_profiles4 (optional)

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>.

performance_table5 (optional)

The performances of profiles for decision maker 5.

The input value should be a valid XMCDA document whose main tag is <performanceTable>.

preferences5 (optional)

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 <alternativesComparisons>.

flows5 (optional)

Normalised flows of given alternatives for decision maker 5.

The input value should be a valid XMCDA document whose main tag is <alternativesValues>.

categories_profiles5 (optional)

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>.

performance_table6 (optional)

The performances of profiles for decision maker 6.

The input value should be a valid XMCDA document whose main tag is <performanceTable>.

preferences6 (optional)

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 <alternativesComparisons>.

flows6 (optional)

Normalised flows of given alternatives for decision maker 6.

The input value should be a valid XMCDA document whose main tag is <alternativesValues>.

categories_profiles6 (optional)

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>.

performance_table7 (optional)

The performances of profiles for decision maker 7.

The input value should be a valid XMCDA document whose main tag is <performanceTable>.

preferences7 (optional)

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 <alternativesComparisons>.

flows7 (optional)

Normalised flows of given alternatives for decision maker 7.

The input value should be a valid XMCDA document whose main tag is <alternativesValues>.

categories_profiles7 (optional)

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>.

performance_table8 (optional)

The performances of profiles for decision maker 8.

The input value should be a valid XMCDA document whose main tag is <performanceTable>.

preferences8 (optional)

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 <alternativesComparisons>.

flows8 (optional)

Normalised flows of given alternatives for decision maker 8.

The input value should be a valid XMCDA document whose main tag is <alternativesValues>.

categories_profiles8 (optional)

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>.

performance_table9 (optional)

The performances of profiles for decision maker 9.

The input value should be a valid XMCDA document whose main tag is <performanceTable>.

preferences9 (optional)

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 <alternativesComparisons>.

flows9 (optional)

Normalised flows of given alternatives for decision maker 9.

The input value should be a valid XMCDA document whose main tag is <alternativesValues>.

categories_profiles9 (optional)

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>.

performance_table10 (optional)

The performances of profiles for decision maker 10.

The input value should be a valid XMCDA document whose main tag is <performanceTable>.

preferences10 (optional)

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 <alternativesComparisons>.

flows10 (optional)

Normalised flows of given alternatives for decision maker 10.

The input value should be a valid XMCDA document whose main tag is <alternativesValues>.

categories_profiles10 (optional)

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>.

profiles_flows

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>.

categories_values

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>.

method_parameters

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 <methodParameters>. It must have the following form:

<methodParameters>
    %1
    %2
    %3
    %4
    %5
    %6
    %7
    %8
    %9
    %10
</methodParameters>

where:

  • %1 is a parameter named “comparison with profiles”. It can have the following values:

    • central: central profiles
    • bounding: boundary profiles

    The 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.

Outputs

first_step_assignments

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 <alternativesAffectations>.

final_assignments

Final assignments made in a FlowSortGDSS process.

The returned value is a XMCDA document whose main tag is <alternativesAffectations>.

messages

Messages or errors generated by this module.

The returned value is a XMCDA document whose main tag is <methodMessages>.

Original xml description