Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running time D-optimal design #37

Open
694411 opened this issue Sep 14, 2024 · 3 comments
Open

Running time D-optimal design #37

694411 opened this issue Sep 14, 2024 · 3 comments

Comments

@694411
Copy link

694411 commented Sep 14, 2024

Hi! Thanks for this great package! :) I have a question rather than an issue. I am creating the design using the 'dopt' method. However, I've been waiting for a couple of days now and my code is still running. It probably has to do with the convergence of the Fedorov algorithm. Do you have any experience yourself, in how long the following set-up will take? And if it will eventually converge?

design_1 <- cbc_design( profiles = profiles1, n_resp = 2000, n_alts = 20, n_q = 20, n_blocks = 4, method = "dopt", no_choice = TRUE )

The total number of profiles is 80 in my case. The alternatives have 10 attributes each, varying from 2 to 8 levels. I did use restrictions and furthermore, I randomly sampled 80 alternatives to keep in my profiles. So that is what 'profile1' looks like.

@694411
Copy link
Author

694411 commented Sep 19, 2024

Especially when I increase the number of alternatives per task, the running time increases. To a point that I don't think there will be any output. A design with 4 alternatives in 15 tasks is fine, but 5 alternatives already seems impossible.

@jhelvy
Copy link
Owner

jhelvy commented Sep 19, 2024

Apologies for the late reply. And yes, I have seen examples of this before. I would say that if you don't get a design solution within a relatively short period (e.g., 10 minutes at most), you probably won't find one. This should not requires multiple days to run. The unsatisfying answer is that the particular algorithm probably won't find a good solution, which means you should consider modifying your design. My package relies on others for specific algorithms, and some are better / more robust than others. My plan was to eventually implement my own algorithms for some of these design approaches that are potentially better, but I have not had time to do the implementation. So instead I rely on others, which means for the time being I won't likely have an improvement.

@694411
Copy link
Author

694411 commented Sep 19, 2024

Thanks a lot for responding!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants