Hi Ofir,
You can also apply constraints with the federov algorithm, however they are specified a little differently. I will use and example from "8.2.2 Constrained designs" in the demonstration project (from the help menu).
Code: Select all
Design
;alts = Alt1, Alt2
;rows = 6
;eff = (mnl, d)
;alg = mfederov
;reject:
Alt1.X1 > Alt2.X3
;model:
U(Alt1) = b1[-0.2] + b2[0.3] * X1[2,4,6](1-3,1-3,1-3) + b3[0.4] * X2[1,3,5](1-3,1-3,1-3) /
U(Alt2) = b2 * X3[2,4,6](1-3,1-3,1-3) + b4[0.3] * X4[1,2,3](1-3,1-3,1-3) $
You can specify a series of reject conditions with the reject property (comma separate them as with the cond property). Any choice set that satisfies the logical rule with not make it into the experimental design. The round brackets after the attribute level specification specify how many times each level can appear. The narrower the range, the harder it will be to find a design. There is also a require property, where the choice set will not enter the experimental design if the logical rule evaluates to false.
So you could add the reject or require conditions to the following syntax:
Code: Select all
Design
;alts = alt1*, alt2*, alt3*
;rows=9
;eff=(mnl,d)
;alg=mfederov
;model:
U(alt1) = a[-0.1]*A[96,114,126,144](1-3,1-3,1-3,1-3) + b[-0.5]*B[25,28,31,34](1-3,1-3,1-3,1-3) + c[0.1]*C[20,40,60,80](1-3,1-3,1-3,1-3)/
U(alt2) = a*A + b*B + c*C/
U(alt3) = a*A + b*B + c*C
$
The problem is coming from a combination of the number of attributes (more attributes will tend to break the dominance situation), the number of levels (more levels makes it easier for an attribute to be better or worse than another attribute in the choices et), and the number of alternatives (more alternatives create more combinations of alternatives, each of which lead to a dominance situation). The advantage of the federov algorithm in this situation is that by not trying to force complete attribute level balance, a larger area of the design space can be examined.