-
Notifications
You must be signed in to change notification settings - Fork 653
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
Bug when trying to load multiple engines in DJL #57
Labels
bug
Something isn't working
Comments
Fixed and merged, reference commit id: a8c4bfc |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are a few bugs in DJL right now when you try to use multiple engines.
For example if we use MXNet and TensorFlow engine together. If I set -Dai.djl.default_engine=MXNet, and call a TfEngine or TfModelZoo method, MxEngine and MxModelZoo is actually returned.
TfEngine.getInstance()
will return Default Engine instead of TfEngine.TfModelZoo.RESNET.loadModel()
will return MxModel.RESNET if default engine is MXNet, will return PyModel.RESNET if default engine is Pytorch. But user already specified to use TfModelZooIn
Criteria.builder()
the.optEngine("TensorFlow")
option is not used by ModelZoo during loading model.Right now the 2 ways to work with multiple engines are:
ai.djl.default_engine
back and forthnewInstance
with engineName will return the correct implementation under that engine:Model tfModel = Model.newInstance(Device.defaultDevice(), "TensorFlow")
The text was updated successfully, but these errors were encountered: