Provider: | PUT |
---|---|
Version: | 0.3 |
Robust Ordinal Regression for value-based sorting: RORUTADIS-PostFactum-InvestigatePerformanceDeterioration service checks how much an alternative evaluations can be deteriorated so that that alternative would stay possibly (or necessarily) in at least some specific class. Deterioration is based on minimization value of rho in multiplication of an alternative evaluations on selected criteria by rho (where 0 < rho <= 1). Note! This function works for problems with only non-negative alternative evaluations. 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).
(For outputs, see below)
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.
A list of alternatives.
Tag: alternatives
Code:
<alternatives>
<alternative id="[...]">
<active>[...]</active>
</alternative>
[...]
</alternatives>
A list of categories (classes). List must be sorted from the worst category to the best.
Tag: categories
Code:
<categories>
<category id="[...]" />
[...]
</categories>
The performances of the alternatives.
A list of criteria values which denote whether multiplying by rho on corresponding criterion is allowed (value 1) or not (value 0). Values for all criteria have to be provided and at least one criterion has to be available for manipulation.
Tag: criteriaValues
Code:
<criteriaValues>
<criterionValue>
<criterionID>[...]</criterionID>
<value><integer>[...]</integer></value>
</criterionValue>
[...]
</criteriaValues>
Optional: yes, enabled by default
A list of assignment examples of alternatives to intervals of categories (classes) or to a specific category (class).
Tag: alternativesAffectations
Code:
<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>
Optional: yes, enabled by default
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.
Tag: alternativesComparisons
Code:
<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>
Optional: yes, enabled by default
A list of category (class) cardinality constraints. It allows to define minimal and/or maximal desired category (class) cardinalities.
Tag: categoriesValues
Code:
<categoriesValues>
<categoryValue>
<categoryID>[...]</categoryID>
<value>
<interval>
<lowerBound><integer>[...]</integer></lowerBound>
<upperBound><integer>[...]</integer></upperBound>
</interval>
</value>
</categoryValue>
[...]
</categoriesValues>
Method parameters.
Parameter values can be defined via the GUI or the XMCDA file, by default via GUI.
Name: strictlyMonotonicValueFunctions
Whether marginal value functions strictly monotonic or not.
Name: alternative
An identifier of alternative for assignment deterioration.
Name: necessary
Whether necessary or possible assignments to consider.
Name: atLeastToClass
An identifier of category of assignment to investigate.
Tag: methodParameters
Code:
<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>
Deterioration value (value of rho).
Tag: alternativesValues
Code:
<alternativesValues mcdaConcept="deteriorationValue">
<alternativeValue>
<alternativeID>[...]</alternativeID>
<value>
<real>[...]</real>
</value>
</alternativeValue>
</alternativesValues>
Messages generated by the program.
For further technical details on the web service underlying this program, have a look at its documentation here.