-
Notifications
You must be signed in to change notification settings - Fork 6
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
priorsense integration not working #538
Comments
Thanks for the report on this @jonathonmellor we are aware and think it may be related to other R side likelihood integration issues (#479 #476 #526 ) Closing #479 in favour of this issue due to a clear problem statement. |
This is definitely an us problem so good to report. I am looking at this properly next week if I don't get to it by end of day today |
This error:
Is the same as the error with |
The
powerscale_sensitivity(fit, cores = 10) doesn't error but does take all of time (i.e it has been running for 20 minutes) so isn't very practical to use |
This should now work on main but note I am going to take another checking pass at this in #476 as I haven't done extensive testing to make sure the output of priorsense is "correct" (though I am also not aware of any reason why it wouldn't be at the moment`. |
Thanks all for your hard work on this package, it's great!
Describe the bug
epidist
fit
object produces error when passed topriorsense
.To Reproduce
Taking a latent model that is working well otherwise, of the form:
Running (or different permutations of variables or functions):
Produces the error:
Error in
purrr::map_dbl()
:ℹ In index: 1.
Caused by error in
purrr::map_dbl()
:ℹ In index: 1.
Caused by error in
if (is.null(cens) || cens == 0) ...
:! missing value where TRUE/FALSE needed
Run
rlang::last_trace()
to see where the error occurred.Expected behavior
The output should be that of a typical
priorsense
package.Screenshots
Desktop (please complete the following information):
Running on Linux, epidist v0.2, priorsense v1.0.4
Additional context
I appreciate this may not be a problem with
epidist
itself but could bepriorsense
. I note it in part because it looks like it might not be working on the website either (unless outputs aren't intended)The text was updated successfully, but these errors were encountered: