-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Supporting custom frameworks in SageMaker?? #3
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
Comments
@everpeace thanks for your interest in SageMaker! Adding more frameworks and clearer support for user-defined frameworks is definitely on our roadmap for the near future. We are also considering open-sourcing the container-side code, and we will take your feedback into account as we do so. |
@jesterhazy Thanks for quick reply :-) Wow, that's a good news. I'm looking forward to it! So, I'm closing this issue for now. If you would make this issue feedback-tracking issue, please re-open this. |
we use DarkNet for video analysis and pyAudioanalysis for audio model training. I'm looking forward how we can integrate these framework into SageMaker. |
Uh oh!
There was an error while loading. Please reload this page.
Thank you for shipping this great product!!!
After reading the documents, I understood SageMaker is fully extensible by docker container. And scikit_bring_your_own example clearly shows users how custom python codes can be applied to SageMaker.
However, when I wanted to support custom framework (like torch, chainer, etc.), how to do that effectively?? To achieve this, they possibly need to write notebook side and container side implementations.
On notebook side, I think mxnet support in sagemaker-python-sdk can be really helpful reference.
However, on container side, I couldn't find such reference. But, there would need a lot of common codes for example:
I imagined these codes might exist in MXNet, tensorflow support, too. Then, I found
SageMakerContainerSupport
package insagemaker-mxnet-py2-cpu:1.0
container. This package defines very useful abstract classes to support custom frameworks for everybody who wants to do it.Of course, I can write similar codes by myself, however, in OSS nature, I'm really happy if you could open this package to the public. Did you have such plan??
The text was updated successfully, but these errors were encountered: