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
Refactor prediction #62
Conversation
I'm currently pulling most of the prediction tests into Once tests are passing, I'm planning to go back through and add simple tests not for correctness, but just that model <- fit(model_constructor(...), ...)
output <- predict(model, ...)
modeltests::check_predict_output(model, data, predict_options) (also, this PR should be linked with #41) |
Current status: close to an MVP. What I've done so far:
There's a fair amount of translation that needs to happen that is rather time consuming on the Things I couldn't implement
These models will need I added some tiny tests that should check that at very least This PR has taught me an important lesson: namely, that it is sometimes better to make small incremental changes than to burn everything down and start from scratch. |
Oh, and I also need to add a Update: done. |
Ok this is so out of date I'm going to close and once |
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. |
This is an aggressive refactor to move all prediction code to
safepredict
.safepredict
doesn't have methods for several of the existing models, so definitely don't merge until I've got that done. Plan is to push commits to this PR as an open project.