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 Thu, Feb 21, 2019 at 11:11 AM sandeep krishnamurthy < [email protected]> wrote: > 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 experience during inference across all language bindings and also > we see a good performance gains. > 2. Currently, model export/save APIs do not save input/output signature > like input data names, shapes etc.. By saving it as part of the model, we > simplify again the inference and model deployment logic. > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=103090063 > > Thanks to our fellow community members (Zhi, Naveen, Pinar and Jake) for > their initial feedback. I request the community to review and provide > feedback on the proposal. > > -- > Sandeep Krishnamurthy >
