Skip to content

Standardize nnet class prediction column names #225

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

Merged
merged 4 commits into from
Nov 1, 2019

Conversation

patr1ckm
Copy link
Contributor

@patr1ckm patr1ckm commented Oct 29, 2019

Fixes a specific issue with nnet class prediction column names discovered in #174.

Fixes #174.

@patr1ckm patr1ckm changed the title standardize nnet predictions Standardize nnet class prediction column names Oct 29, 2019
@patr1ckm
Copy link
Contributor Author

patr1ckm commented Oct 29, 2019

The integration test with predict was failing here because of an unclear dependency issue on travis, so simplified to a unit test instead.

@topepo
Copy link
Member

topepo commented Nov 1, 2019

Thanks!

@topepo topepo merged commit 3fef9c3 into tidymodels:master Nov 1, 2019
@github-actions
Copy link

github-actions bot commented Mar 7, 2021

This pull request 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.

@github-actions github-actions bot locked and limited conversation to collaborators Mar 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

predict() on a mlp with nnet double names the output with .pred_
2 participants