RORUTADIS-PostFactum-InvestigateValueChange

SOAP service’s name:
Version:	0.3
Provider:	PUT
	`RORUTADIS-PostFactum-InvestigateValueChange-PUT` (see SOAP requests for details)

Description

Robust Ordinal Regression for value-based sorting: RORUTADIS-PostFactum-InvestigateValueChange service calculates missing value of an alternative utility for that alternative to be possibly (or necessarily) assigned to at least some specific class. It is possible to provide an additional optional preference information: example alternatives assignments, assignment pairwise comparisons and desired class cardinalities. Service developed by Krzysztof Ciomek (Poznan University of Technology, under supervision of Milosz Kadzinski).

Contact:: Krzysztof Ciomek (k.ciomek@gmail.com), Milosz Kadzinski (milosz.kadzinski@cs.put.poznan.pl)

Web page: https://github.com/kciomek/rorutadis

Reference: None

Inputs

(For outputs, see below)

criteria

A list of criteria (<criteria> tag) with information about preference direction (<criteriaValues mcdaConcept=”preferenceDirection”>, 0 - gain, 1 - cost) and number of characteristic points (<criteriaValues mcdaConcept=”numberOfCharacteristicPoints”>, 0 for the most general marginal utility function or integer grater or equal to 2) of each criterion.

The input value should be a valid XMCDA document whose main tag is <criteria>. It must have the following form:

<criteria>
        <criterion id="[...]" />
        [...]
</criteria>

<criteriaValues mcdaConcept="preferenceDirection">
        <criterionValue>
                <criterionID>[...]</criterionID>
                <value><integer>[...]</integer></value>
        </criterionValue>
        [...]
</criteriaValues>

<criteriaValues mcdaConcept="numberOfCharacteristicPoints">
        <criterionValue>
                <criterionID>[...]</criterionID>
                <value><integer>[0|integer greater or equal to 2]</integer></value>
        </criterionValue>
        [...]
</criteriaValues>

alternatives

A list of alternatives.

The input value should be a valid XMCDA document whose main tag is <alternatives>. It must have the following form:

                    <alternatives>
    <alternative id="[...]">
        <active>[...]</active>
    </alternative>
    [...]
</alternatives>

performanceTable

The performances of the alternatives.

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

assignmentExamples (optional)

A list of assignment examples of alternatives to intervals of categories (classes) or to a specific category (class).

The input value should be a valid XMCDA document whose main tag is <alternativesAffectations>. It must have the following form:

<alternativesAffectations>
        <alternativeAffectation>
                <alternativeID>[...]</alternativeID>
                <categoryID>[...]</categoryID>
        </alternativeAffectation>
        [...]
        <alternativeAffectation>
                <alternativeID>[...]</alternativeID>
                <categoriesInterval>
                        <lowerBound>
                                <categoryID>[...]</categoryID>
                        </lowerBound>
                        <upperBound>
                                <categoryID>[...]</categoryID>
                        </upperBound>
                </categoriesInterval>
        </alternativeAffectation>
        [...]
        <alternativeAffectation>
                <alternativeID>[...]</alternativeID>
                <categoriesSet>
                        <categoryID>[...]</categoryID>
                        [...]
                </categoriesSet>
        </alternativeAffectation>
        [...]
</alternativesAffectations>

assignmentComparisons (optional)

Two lists of assignment pairwise comparisons. A comparison from list with attribute mcdaConcept=”atLeastAsGoodAs” indicates that some alternative should be assigned to class at least as good as class of some other alternative (k = 0) or at least better by k classes (k > 0). A comparison from list with attribute mcdaConcept=”atMostAsGoodAs” indicates that some alternative should be assigned to class at most better by k classes (k > 0) then some other alternative.

The input value should be a valid XMCDA document whose main tag is <alternativesComparisons>. It must have the following form:

<alternativesComparisons mcdaConcept="atLeastAsGoodAs">
        <pairs>
                <pair>
                        <initial><alternativeID>[...]</alternativeID></initial>
                        <terminal><alternativeID>[...]</alternativeID></terminal>
                        <value><integer>k</integer></value>
                </pair>
                [...]
        </pairs>
</alternativesComparisons>

<alternativesComparisons mcdaConcept="atMostAsGoodAs">
        <pairs>
                [...]
        </pairs>
</alternativesComparisons>

categoriesCardinalities (optional)

A list of category (class) cardinality constraints. It allows to define minimal and/or maximal desired category (class) cardinalities.

The input value should be a valid XMCDA document whose main tag is <categoriesValues>. It must have the following form:

<categoriesValues>
        <categoryValue>
                <categoryID>[...]</categoryID>
                <value>
                        <interval>
                                <lowerBound><integer>[...]</integer></lowerBound>
                                <upperBound><integer>[...]</integer></upperBound>
                        </interval>
                </value>
        </categoryValue>
        [...]
</categoriesValues>

methodParameters

Method parameters.

The input value should be a valid XMCDA document whose main tag is <methodParameters>. It must have the following form:

<methodParameters>
    <parameter name="strictlyMonotonicValueFunctions">
        <value>
            <boolean>%1</boolean>
        </value>
    </parameter>
                            <parameter name="alternative">
                                    <value><label>%2</label></value>
                            </parameter>
    <parameter name="necessary">
        <value>
            <boolean>%3</boolean>
        </value>
    </parameter>
                            <parameter name="atLeastToClass">
                                    <value><label>%4</label></value>
                            </parameter>
</methodParameters>

where:

%1 is a parameter named “strictlyMonotonicValueFunctions”. This is a boolean. The default value is false.
%2 is a parameter named “alternative”. This is a string, and the value should conform to the following constraint: This identifier cannot be empty. More formally, the constraint is:
```
! %2.isEmpty()
```
%3 is a parameter named “necessary”. This is a boolean. The default value is false.
%4 is a parameter named “atLeastToClass”. This is a string, and the value should conform to the following constraint: This identifier cannot be empty. More formally, the constraint is:
```
! %4.isEmpty()
```

Outputs

marginalValueFunctions

Marginal value functions.

The returned value is a XMCDA document whose main tag is <criteria>. It has the following form:

<criteria>
        <criterion id="[...]">
                <criterionFunction>
                        <points>
                                <point>
                                        <abscissa><real>[...]</real></abscissa>
                                        <ordinate><real>[...]</real></ordinate>
                                </point>
                                [...]
                        </points>
                </criterionFunction>
        </criterion>
        [...]
</criteria>

alternativesValuesTable

Marginal utility values of alternatives (for result function where missing utility is the smallest).

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

assignments

Alternative assignments (for result function where missing utility is the smallest).

The returned value is a XMCDA document whose main tag is <alternativesAffectations>. It has the following form:

<alternativesAffectations>
        <alternativeAffectation>
                <alternativeID>[...]</alternativeID>
                <categoryID>[...]</categoryID>
        </alternativeAffectation>
        [...]
        <alternativeAffectation>
                <alternativeID>[...]</alternativeID>
                <categoriesInterval>
                        <lowerBound>
                                <categoryID>[...]</categoryID>
                        </lowerBound>
                        <upperBound>
                                <categoryID>[...]</categoryID>
                        </upperBound>
                </categoriesInterval>
        </alternativeAffectation>
        [...]
        <alternativeAffectation>
                <alternativeID>[...]</alternativeID>
                <categoriesSet>
                        <categoryID>[...]</categoryID>
                        [...]
                </categoriesSet>
        </alternativeAffectation>
        [...]
</alternativesAffectations>

values

Value of missing utility.

The returned value is a XMCDA document whose main tag is <alternativesValues>. It has the following form:

<alternativesValues mcdaConcept="investigationResultValue">
        <alternativeValue>
                <alternativeID>[...]</alternativeID>
                <value>
                        <real>[...]</real>
                </value>
        </alternativeValue>
</alternativesValues>

thresholds

Lower threshold for each category/class (for result function where missing utility is the smallest).

The returned value is a XMCDA document whose main tag is <categoriesValues>. It has the following form:

<categoriesValues mcdaConcept="thresholds">
        <categoryValue>
                <categoryID>[...]</categoryID>
                <value>
                        <real>[...]</real>
                </value>
        </categoryValue>
        [...]
</categoriesValues>

messages

Messages generated by the program.

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

Original xml description

description.xml