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
Bug in family$mu_fun()
(or in a call)?
#243
Comments
family$mu_fun()
(or in its calls)?family$mu_fun()
(or in a call)?
I think a basic input check for Lines 182 to 183 in ef3cfc2
newdata is specified.
|
This is indeed a bug, as can be seen from debugging the call to |
Fixed in |
Sorry, I currently don't have the time to create a reprex for this. But an inspection of the code might already be sufficient for confirming whether this is a bug or not.
Consider lines
projpred/R/cv_varsel.R
Lines 413 to 415 in ef3cfc2
family$mu_fun()
inprojpred/R/refmodel.R
Lines 631 to 637 in ef3cfc2
obs
? This could be done either inside offamily$mu_fun()
or in the call to it (for the latter, it would make sense to add an input check tofamily$mu_fun()
which tests in case of!is.null(offset)
whetheroffset
is of length1
ornrow(newdata)
(afternewdata
has been pre-processed)).Compare with lines
projpred/R/summary_funs.R
Lines 7 to 9 in ef3cfc2
family$mu_fun()
) which is intended by projpred.The text was updated successfully, but these errors were encountered: