Hello MXNet community,
I have put up a design proposal to extend the MXNet model saving and
loading APIs to solve the following 2 problems:
1. Currently, model export/save APIs do not allow you to export the data
transformations as part of the model. By allowing this, we greatly simplify
the user
Hi Sandeep,
In the design doc, you stated that
> Input/Output signature are not part of the model: Saved model missing the
information about the input/output descriptions, like name/shape, making
the saved model unusable out of the box.
Could you elaborate why you think this is the case?
-sz
On
Hi Sheng,
By stating unusable out of the box, I meant, when loading a model for
inference, today, users need to know input name, shape for binding. This
information if part of the model, could have simplified model training to
model deployment path much easier and decoupled.
Best,
Sandeep
On Thu
