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.

Sign up for GitHub

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

Jump to bottom

.predict should take in model_id first, then features #13

Open
ClimbsRocks opened this issue Jan 18, 2018 · 0 comments
Open

.predict should take in model_id first, then features #13

ClimbsRocks opened this issue Jan 18, 2018 · 0 comments

Comments

@ClimbsRocks
Copy link
Owner

i think that seems more intuitive, and more closely aligns with current ways of doing things (model_name.predict(features) becomes concord.predict(model_name, features) ).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ClimbsRocks