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

Remove training capabilities from out of scope (shortly: add training capabilities to scope :-) ) #6

Closed
DanielMazurkiewicz opened this issue Jan 12, 2019 · 2 comments

Comments

@DanielMazurkiewicz
Copy link

Back-propagation is a fairy simple training algorithm and if provided only for basic operation blocks ("core1" domain as I mentioned in phasing issue ) then it shouldn't require significant effort to implement and test it on vendors site.

Benefits seems sort of obvious, but lets briefly list what comes to my mind quickly:

  • lower entrance barrier to ML world for JS developers (just enough to get familiar with API and they could quickly jump on into ML)
  • easier phasing and quicker standard shipment - no need to cover all possible operation blocks from different ML environments, enough is just a small basic subset of blocks
  • possibility to train or adjust NNs "on the fly", for example in gaming industry
@DanielMazurkiewicz DanielMazurkiewicz changed the title Remove training capabilities from out of scope (shortly: add training capabilities :-) ) Remove training capabilities from out of scope (shortly: add training capabilities to scope :-) ) Jan 12, 2019
@anssiko
Copy link
Member

anssiko commented Jan 16, 2019

Thanks for your input @DanielMazurkiewicz. Since there's an existing charter issue #3 to discuss training capabilities, I'd suggest you add your comment there to avoid forking the discussion over multiple issues to make it easier to follow and contribute. Thanks!

@DanielMazurkiewicz
Copy link
Author

Ok, moving to: #3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants