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

Tuning panel needs improvement #81

Closed
florianfendt opened this issue Jan 25, 2017 · 0 comments
Closed

Tuning panel needs improvement #81

florianfendt opened this issue Jan 25, 2017 · 0 comments

Comments

@florianfendt
Copy link
Contributor

florianfendt commented Jan 25, 2017

We need exception / input handling when tuning fails.
Example where already 2 things fail:
iris-task, randomForest (with predict responses), gridSearch, logos, parallel tuning, tune mtry and ntree.
If you don't set upper there's the raw error code that assertion on upper failed.
If you do you get the error code because logloss needs predict.type "prob"
Also it seems that some inputs don't update after tuning. E.g: I tried to set parallel to "no" after I ran into the above error. When I hit tune again I still get the same error code, so it seems we still use the parallel mode.
Update:
Yes parallel mode needs to be switched off after use. I'm still running on 2 cores if I close the app and restart in same R-Session

Coorsaa added a commit that referenced this issue Jan 31, 2017
closes #81 added checks for tuning
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant