choice-metrics.com

In your first syntax, your priors are closer to zero. In the second, the priors are farther from zero. The S estimate is an estimate of the sample size required so when you run the model, the parameters computed are statistically significant. The closer a parameter is to zero, the higher sample you ...

A couple of thoughts from the peanut gallery:

First, your syntax in red doesn't make any sense. You can't be both linear and effects coded at the same time. b3.effects is a single, unified, piece of syntax. b3[].effects should cause an error. Think carefully about your parameter specification in ...

One simple thing you could do is use fixed priors rather than distributions. Yes, your design will pay a price for that uncertainty, but you have a much better chance of getting one at all.

So instead of [(n,-0.0003,0.0001)|(n,-0.0002,0.0001)|(n,-0.0001,0.00005)|(n,0.0001,0.00005)|(n,0.0002,0.0001 ...

Another option that might work is to treat the second parking variable as just a 3-level attribute with values [-50%, -20%, 0%]. I typically effects code these things but you can do whatever you like. And you wouldn't need any constraints at all.

Optionally, you could include an interaction ...

I have a request for the next version. Currently, Ngene is TERRIBLE at blocking. There doesn't seem to be much attention paid to blocks and how they affect results, but I believe for random effects models version effects are large and an important thing to minimize. Ngene could be much better at ...

Seeing no official reply, I'll take a stab at it. I haven't seen any activity on the development front for Ngene in years. I would doubt there is anything pending in the short term.

In other words, don't hold your breath.

Thanks. I didn't realize it was that simple to use ;require. Fingers crossed the mfederov algorithm finds a useful design.

Hi there,

I'm working on a design with a counter constraint (similar in a way to partial profile). there are many attributes but one set of 7 has the following constraint. I can allow 0, 1, 2, or 3 of the 7 binary attributes to be 1.

A snippit of code.

U(A) = ... +
b1.d[0]*att1[0,1] +
b2.d[0 ...

Got it. Makes sense. Thanks.

Thank you!

I think my problem was that my prior was not big enough. A bigger prior would solve my problem.

Paul