-
Notifications
You must be signed in to change notification settings - Fork 88
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
Consistent behavior for fit classification when the response isn't a factor #115
Comments
EmilHvitfeldt
changed the title
Consistent behavoir when for fit classification when the response isn't a factor
Consistent behavior for fit classification when the response isn't a factor
Dec 14, 2018
I don't mind trying to fix it if you deem it necessary. |
(sorry @EmilHvitfeldt I didn't see your comment to volunteer until I started) |
No problem, I'm just happy it is being handled! |
topepo
added a commit
that referenced
this issue
Mar 3, 2019
For classification problems, an error is thrown if the outcome is not a factor: ``` Error: For classification models, the outcome should be a factor. ``` There are a lot of travis related changes too: * To get travis to run tests, the modeling packages have to be formal dependencies so a bunch were added to Suggests. This _may_ be temporary; I may decide to remove these for the version sent to CRAN. `rstanarm` was excluded because compiling it (and its dependencies) exceeded the time allowed by travis. * A variety of changes were made to the tests related to r-devel. It looks like any function directly accessed in the tests now need to be formal dependencies (not the case before). There is still some weirdness about this though and I've attributed it to being _devel_. Hopefully this will get smoothed out.
Merged
topepo
added a commit
that referenced
this issue
Mar 17, 2019
* changes to #115 * testing out adding modeling pacakges to suggests * first attempt at getting around CXX14 travis issues * second attempt at getting around CXX14 travis issues * third attempt at getting around CXX14 travis issues (xenial) * fourth attempt at getting around CXX14 travis issues * fifth attempt at getting around CXX14 travis issues * sizth attempt at getting around CXX14 travis issues * abandoning rstanarm on travis * cleaned the travis house to see what runs and fails * no rstanarm and back to trusty * trying to avoid travis failures for devtools ``` * installing *source* package ‘devtools’ ... ** package ‘devtools’ successfully unpacked and MD5 sums checked ** R ** inst ** byte-compile and prepare package for lazy loading Error in loadNamespace(j <- i[[1L]], c(lib.loc, .libPaths()), versionCheck = vI[[j]]) : there is no package called ‘magrittr’ ERROR: lazy loading failed for package ‘devtools’ * removing ‘/home/travis/R/Library/devtools’ * restoring previous ‘/home/travis/R/Library/devtools’ The downloaded source packages are in ‘/tmp/RtmpUhu1j4/downloaded_packages’ Warning message: In install.packages(c("devtools")) : installation of package ‘devtools’ had non-zero exit status ``` * back to original travis file * reformatting * R-devel complains about calling by namespace without loading * seventh attempt at getting around CXX14 travis issues * eigth attempt at getting around CXX14 travis issues * bad backtick! * moved makevars stuff to before_install * adding C50 and rstanarm back into travis builds * get binaries for stan packages * CXX14FLAGS for rstan * more binaries * no stan * no stan (I mean it this time) * one last library call * fixed test case * more changes for r-devel * removed specific top-level stan calls * remove ancillary files * avodi returning multiple logicals * back to computing probability results * added library calls * namespace the predict function
This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For whatever reason you might accidentally specify your response as something other then a factor. This gives rather informative error messages.
Created on 2018-12-13 by the reprex package (v0.2.1)
When response is logical we manage to fit, but
predict_class
fails. And when the response is numeric and character it fails to fit in both.I propose we check inside fit.model_spec that the response is of type factor when doing classification.
The text was updated successfully, but these errors were encountered: