You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In ordinal elicitation, allow multiple answers to the elicitation question (which means indifference between those choices). The preferences translate as follows:
Say c1 > (c2 ~ c3) > c4, then add c1 > c2, c1 > c3, c2 > c4, c3 > c4 as constraints.
Ratio bound elicitation becomes slightly more complex. These cases must be taken into account:
(c2 ~ c3) specifies an indifference class. Within this class, the weight rations w2/w3 must include 1. This means that two separate questions must be asked to obtain the upper and lower bounds for the ratio, otherwise the slider would need to go outside the range where the PVFs are defined.
If c1 > (c2 ~ c3), then we could ask ratio questions about w1/w2 or w1/w3, neither contain exactly the same information; should this choice be made arbitrarily, or should all questions be asked?
Within a larger indifference class (e.g. c1 ~ c2 ~ c3), n(n-1)/2 questions can be asked, and again there is no "natural" ordering to the questions.
Some of these could be solved by the entropy-minimization approach, but that is not finished.
The text was updated successfully, but these errors were encountered:
chinook25
pushed a commit
to chinook25/mcda-elicitation-web
that referenced
this issue
Jun 3, 2019
# This is the 1st commit message:
remove obsolete properties from data sources
# This is the commit message drugis#2:
let workspaces work with the new schema; some refactoring
# This is the commit message drugis#3:
some refactoring
# This is the commit message drugis#4:
wip
# This is the commit message drugis#5:
wip rewriting inputknowledgeservice
In ordinal elicitation, allow multiple answers to the elicitation question (which means indifference between those choices). The preferences translate as follows:
Ratio bound elicitation becomes slightly more complex. These cases must be taken into account:
Some of these could be solved by the entropy-minimization approach, but that is not finished.
The text was updated successfully, but these errors were encountered: