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

xt outside of design space when having 0 and using discrete_xt #13

Open
zparra opened this issue Aug 25, 2017 · 1 comment
Open

xt outside of design space when having 0 and using discrete_xt #13

zparra opened this issue Aug 25, 2017 · 1 comment

Comments

@zparra
Copy link

zparra commented Aug 25, 2017

It seems that when you specify a value of 0 as minimum of your design space, it gets replaced by 1e-05

poped.db$design_space$minxt (done with the vignette example)
obs_1 obs_2 obs_3 obs_4 obs_5
grp_1 1e-05 1e-05 1e-05 240 240
grp_2 1e-05 1e-05 1e-05 240 240

However if in your initial design you have a time 0, it does not get replaced

poped.db$design$xt
obs_1 obs_2 obs_3 obs_4 obs_5
grp_1 0 2 8 240 245
grp_2 0 2 8 240 245

Apparently, this is not a problem apparently for a continous space, but if instead you provide a discrete space, you get an error because the obs_1 is out of the design space:

poped.db.discrete <- create.poped.database(poped.db,discrete_xt = list(0:248))
Error in eval(substitute(expr), data, enclos = parent.frame()) :
xt value for group 1 (column 1) is not in the design space

@andrewhooker
Copy link
Owner

andrewhooker commented Aug 25, 2017 via email

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