-
Notifications
You must be signed in to change notification settings - Fork 93
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
Binding Examples [Discussion] #97
Comments
I think it's a nice idea. Since the examples repo is not restricted to models, It would be a good idea to showcase various features of mlpack including the bindings. |
I agree, it would be really nice. For now we just have the quickstart examples, but perhaps those could be additionally moved here and then expanded on. Some of the (very old) mlpack tutorials also have binding usage examples, but they aren't always great examples. |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions! 👍 |
Yeah when writing that example with R binding I tried to expand on the quick start example and fit it into a standard machine learning workflow. I think for newcomers to mlpack having an example with how to use a binding in data science workflow is helpful. I think it's a solid idea. |
@birm do you think there is anything else to do for this issue? It seems like everyone is agreed that binding examples would definitely be a good idea. :) |
Should I edit this issue to include subtasks for each binding then? |
@birm up to you; if you want to keep it open until we have examples of each binding, that sounds good to me. Or, it might be easier to open a new issue for it and tag it with |
I'm not confident if this is a good idea, but it would be interesting to have a simple example for each of the bindings. This could double as a more robust binding test, as well as a demonstration. It may, however, add unneeded complexity.
I'm not sure. Thoughts?
The text was updated successfully, but these errors were encountered: