Closed GabeAl closed 5 years ago
y <- c(0, 1)
is.numeric(factor(y))
Done. That fixed it.
Going to open a new feature request to auto-cast variables to whatever format it internally expects -- inevitably I'm going to run into more just like before with the int/numeric thing and the big.matrix thing (although at least the latter is in the vignettes).
Thanks again!
I have run biglasso on a similar dataset as reported previously (mostly sparse, other whole numbers cast as numeric). I made sure nothing was NA, infinite, or NaN and type was numeric (I remember the integer bug from before).
Is this expected? I have never been able to get bigLasso to work on real problems for me like glmnet -- maybe my use cases are too unconventional?
Glmnet runs fine. Other fields within the output, glm.trained, are populated, such as $y (with 0's and 1's that line up reasonably well with the actual classes), center and scale, and the coefficient matrix looks like it has numbers in it (quite sparse, as expected).
Thanks for any insight. I can try to finagle a minimal reproducible example if the problem isn't obvious with my command and the error messages!