| Provider: | UTAR |
|---|---|
| Version: | 1.1 |
-Contact: Boris Leistedt (boris.leistedt@gmail.com)
Computes UTASTAR method and if necessary uses post-optimality analysis among three well-known post-optimality methods
Post-optimality method : if required, please choose between “ac” (analytic center), “mv” (mean value, geometric center), and “md” (utamp, delta maximization).
-Name: Post-optimality method
- -Possible values:
- none : None (none)
- ac : Analytic center (ac)
- mv : Mean value (mv)
- md : Max delta (md)
-Default value: none
A list of alternatives. Alternatives can be activated or desactivated via the <active> tag (true or false). By default (no <active> tag), alternatives are considered as active.
-Tag: alternatives
-Code:
<alternatives> <alternative> <alternativeID> [...] </alternativeID> </alternative> </alternatives>
-Optional: yes, enabled by default
Ranking (preorder) of alternatives, corresponding to pariwize preference and indifference statements
-Tag: alternativesValues
-Code:
<alternativesValues> <alternativeValue> <alternativeID> [...] </alternativeID> <value> <integer> [...] </integer> </value> </alternativeValue> </alternativesValues>
-Optional: yes, enabled by default
Asymmetric part of the preference relation, representing strict preference statements, under the form of paiwise comparisons of alternatives.
-Tag: alternativesValues
-Code:
<alternativesComparisons> <pairs> <pair> <initial> <alternativeID>[...]</alternativeID> </initial> <terminal> <alternativeID>[...]</alternativeID> </terminal> </pair> [...] </pairs> </alternativesComparisons>
-Optional: yes, enabled by default
Symmetric part of the preference relation, representing indifference statements, under the form of paiwise comparisons of alternatives.
-Tag: alternativesValues
-Code:
<alternativesComparisons> <pairs> <pair> <initial> <alternativeID>[...]</alternativeID> </initial> <terminal> <alternativeID>[...]</alternativeID> </terminal> </pair> [...] </pairs> </alternativesComparisons>
A list of criteria. Criteria can be activated or desactivated via the <active> tag (true or false). By default (no <active> tag), criteria are considered as active.
-Tag: criteria
-Code:
<criteria> <criterion> <criterionID>[...] </criterionID> </criterion> </criteria>
Values of criteria for different alternatives. It must contains IDs of both criteria and alternatives described previously.
-Tag: performanceTable
-Code:
<performanceTable> <alternativePerformances> <alternativeID> [...] </alternativeID> <performance> <criterionID> [...] </criterionID> <value> <real> [...] </real> </value> </performance> </alternativePerformances> </performanceTable>
Optimization direction for the selected criteria (min or max).
-Tag: criteriaValues
-Code:
<criteriaValues> <criterionValue> <criterionID> [...] </criterionID> <value> <label> [..] </label> </value> </criterionValue> </criteriaValues>
Number of segments in each value function to be constructed by UTA.
-Tag: criteriaValues
-Code:
<criteriaValues> <criterionValue> <criterionID>[...] </criterionID> <value> <integer> [...] </integer> </value> </criterionValue> </criteriaValues>
Constructed value functions for the selected criteria and the provided rankings, using ACUTA method.
-Tag: criteria
-Code:
<criteria mcdaConcept="criteria"> <criterion> <criterionID>[..]</criterionID> <criterionFunction> <points> <point> <abscissa><real>[...]</real></abscissa> <ordinate><real>[...]</real></ordinate> </point> </points> </criterionFunction> </criterion> </criteria>
logMessage
-Tag: methodMessages
-Code:
<methodMessages mcdaConcept="methodMessage"> <logMessage> <text> [...]</text> </logMessage> <errorMessage> <text> [...]</text> </errorMessage> </methodMessages>
For further technical details on the web service underlying this program, have a look at its documentation here.