There is no way say what a good value for the D-error is. For one study, a D-error of 0.1 is very good, while for another study a D-error of 0.1 can be bad.
This means that you should not really pay much attention to the value of the D-error. A D-efficient design is a design with a relatively low ...
Search found 2055 matches
- Mon Oct 13, 2025 11:00 am
- Forum: Support for Ngene Online
- Topic: Question about utility calculation and validity of using effects coding in D-efficient design
- Replies: 3
- Views: 150
- Fri Oct 10, 2025 9:55 am
- Forum: Support for Ngene Online
- Topic: Question about utility calculation and validity of using effects coding in D-efficient design
- Replies: 3
- Views: 150
Re: Question about utility calculation and validity of using effects coding in D-efficient design
First of all, it does not matter which coding scheme you select for generating an efficient design. Yes, the D-error changes, but D-errors are not comparable across models. So for different utility functions, different priors, different coding schemes, the D-errors are not comparable. So you should ...
- Sun Oct 05, 2025 8:25 am
- Forum: Support for Ngene Desktop (v1.x)
- Topic: Labeled design
- Replies: 1
- Views: 213
Re: Labeled design
Yes this is possible. There are two options.
(1) Include the type of bread as a dummy coded attribute in the utility functions of BreadA and BreadB. Instead of BreadA and BreadB, you can show the type of bread as the label on top. The coefficients of the dummy coded attribute replace the ...
(1) Include the type of bread as a dummy coded attribute in the utility functions of BreadA and BreadB. Instead of BreadA and BreadB, you can show the type of bread as the label on top. The coefficients of the dummy coded attribute replace the ...
- Tue Sep 30, 2025 10:00 am
- Forum: General questions about choice experiments
- Topic: post-pilot parameters
- Replies: 7
- Views: 1568
Re: post-pilot parameters
1. Yes you can use zero priors, that is always a safe option. The further away your priors are from the true parameters, the more efficiency you lose. Note that parameter estimates are often not significant in a pilot study because of the small sample size, and the estimate is still the best guess ...
- Thu Sep 25, 2025 10:14 pm
- Forum: General questions about choice experiments
- Topic: post-pilot parameters
- Replies: 7
- Views: 1568
Re: post-pilot parameters
I see. In your previous screenshot Charger1 and Charger2 are swapped around. So Pref=1 means that the option in the second row is chosen. In that case it may be correct as long as Stata understands that the first charging option (Charger2) is actually the second listed option.
- Tue Sep 23, 2025 9:18 am
- Forum: General questions about choice experiments
- Topic: post-pilot parameters
- Replies: 7
- Views: 1568
Re: post-pilot parameters
Note that this is a model estimation question,not an experimental design question, and I have no familiarity with Stata so it would be best to ask on the Stata forum. The correlations are unlikely to be an issue; even with correlations as high as 0.9 or 0.95 you should typically be able to estimate ...
- Fri Sep 19, 2025 8:17 pm
- Forum: Support for Ngene Desktop (v1.x)
- Topic: Fixed parameters
- Replies: 5
- Views: 1300
Re: Fixed parameters
A better idea may actually be to simply use the full factorial. There exist actually only 20 unique choice tasks based on your specified constraints and also taking into account that B and C are generic (by using ;alts = B*, C*), which means avoiding choice tasks where the profiles of B and C are ...
- Fri Sep 19, 2025 5:10 pm
- Forum: Support for Ngene Desktop (v1.x)
- Topic: Fixed parameters
- Replies: 5
- Views: 1300
Re: Fixed parameters
I do not see an issue with the first choice task.
In your first choice task you have:
A: y0gain = 0, lambda = 1.6, y0loss = 0
B: y0gain = 0, lambda = 1.6, y0loss = -3
Therefore:
U(A) = 0.3 * 0 + 0.3 * 1.6 * 0 = 0
U(B) = 0.3 * 0 + 0.3 * 1.6 * (-3) = -1.44
So this seems correct to me?
The last ...
In your first choice task you have:
A: y0gain = 0, lambda = 1.6, y0loss = 0
B: y0gain = 0, lambda = 1.6, y0loss = -3
Therefore:
U(A) = 0.3 * 0 + 0.3 * 1.6 * 0 = 0
U(B) = 0.3 * 0 + 0.3 * 1.6 * (-3) = -1.44
So this seems correct to me?
The last ...
- Fri Sep 19, 2025 11:32 am
- Forum: Support for Ngene Desktop (v1.x)
- Topic: Fixed parameters
- Replies: 5
- Views: 1300
Re: Fixed parameters
I am not entirely sure what you mean with "t0" and "t3" and I am also unsure what you mean with "fixed parameter". Do you mean a fixed variable?
The syntax .ref is meant to be used for pivot designs in combination with .piv. If you want a variable to have a fixed value, you simply write for example ...
The syntax .ref is meant to be used for pivot designs in combination with .piv. If you want a variable to have a fixed value, you simply write for example ...
- Wed Sep 17, 2025 5:14 pm
- Forum: General questions about choice experiments
- Topic: Query on Interpreting Reference Level in a Constrained DCE Design
- Replies: 1
- Views: 631
Re: Query on Interpreting Reference Level in a Constrained DCE Design
The short answer is: the interpretation is compared to "no endorsement".
The "not applicable" part needs to be dealt with via an interaction effect in the utility function so that the attribute "External endorsement" simply drops out. For example, in model estimation you would essentially estimate ...
The "not applicable" part needs to be dealt with via an interaction effect in the utility function so that the attribute "External endorsement" simply drops out. For example, in model estimation you would essentially estimate ...