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
First of all, thanks for the package; it has been very helpful.
In generating designs, I've encounted situations where the same profile combinations are shown within a respondent. This does not seem desirable, as the same respondent will see the exact same question twice (or even more frequently).
See some replicable code below. In this case, obsID 3 and 8 have exactly the same profile combinations. The same with obsID 7 and 10. These are all IDs within the same respondent (respID). Despite generating 12 profile combinations (i.e., questions), only 10 are actually unique.
profiles <- cbc_profiles(
a = c(0, 1),
b = c("Yes", "No"),
c = c("100%", "80%"),
d = c("day", "week")
)
Thanks for point out this issue - this looks like a bug for sure.
The remove_dups function only checks for duplicate alternatives by observation to ensure that no two same alternatives are shown in any one choice question. But it does not check for duplicate choice sets by individual, which it should. I'll have to add a correction to fix this.
First of all, thanks for the package; it has been very helpful.
In generating designs, I've encounted situations where the same profile combinations are shown within a respondent. This does not seem desirable, as the same respondent will see the exact same question twice (or even more frequently).
See some replicable code below. In this case, obsID 3 and 8 have exactly the same profile combinations. The same with obsID 7 and 10. These are all IDs within the same respondent (respID). Despite generating 12 profile combinations (i.e., questions), only 10 are actually unique.
profiles <- cbc_profiles(
a = c(0, 1),
b = c("Yes", "No"),
c = c("100%", "80%"),
d = c("day", "week")
)
set.seed(64)
design <- cbc_design(
profiles = profiles,
n_resp = 4,
n_alts = 2,
n_q = 12,
)
The text was updated successfully, but these errors were encountered: