choice-metrics.com

Regarding level frequency constraints - this functionality is introduced in the manual (old Ngene 1.4) in an example with the default swapping algorithm (page 151). An this is why I thought it works this way. However, I have just noticed that level frequencies in the design do not match with the ...

Thanks again for your help, Michiel.

I have just flipped through the new manual and it is absolutely great - so much better and easier to follow than the previous one. I love the new chapters e.g. library of designs, auxiliary models, etc. Great work! We will be definitely switching to the new ...

Thanks again. Not all use cases are covered by the manual, and I really appreciate your advices.

1) That would be quite helpful and make coding easier. One last time regarding the difference between dummy and indicator variables. I can introduce binary indicator variables like those in your paper ...

You're right. I am sorry for flooding you with questions that are obviously study-specific and not directly related to Ngene.

Now more concerning Ngene:
(1) Is the trick with two models that you used a few posts ago necessary? You wrote that you "could not do that directly because cannot introduce ...

(1) I followed the syntax provided in the appendix to the paper by Thai et al., and all seems to be working ok. But could you please take a look at this and see if this code makes sense?

Some infos / changes to previous code:
- I did that with just one model (no aux & main as before)
- First and ...

Thanks again, Michiel, this is extremely helpful!

I see the advantages of a labeled design - simpler code, easy to follow alternative-specific coefficients, no multiple interaction terms, etc.

However, there is one problem with labeled design in my specific case. As the final development of my ...

1. Ngene found a design for 660 rows (it still crashes for 3600, but I will test it on a better machine and with only on design stored) for a model with zero priors. As a next step, I wanted to introduce "sign" priors (negative/positive close to zero) for some attributes such as time or cost where I ...

Thank you so much for your help, Michiel.

I modified the code so that the term "is_pt.dummy[x] * fm.dummy[x]" is now multiplied by "mode.dummy[x]" and I have alternative-specific coefficients for fm and lm.

Since I want to create a new design now, not evaluate an external one, I added conditions ...

Michiel,

Thanks again, I would have never come up with this trick myself :shock:

The code you pasted works for me (I get 0.00272), however, I still have some issues:

1. I noticed that in you code in the main model you use b_fm2 for level 2 of fm.dummy, then b_fm3 for level 3 of fm.dummy, and ...

Michiel,

(Re3) thanks, now it is clear.

(Re2) OK, I think I get your point. But, when randomly selecting 10 rows from the design of 100 rows, I need to make sure that each row is selected (without replacement) an equal number of times, right? Which leads essentially to the same result as blocking ...