Hello Roshani,

interesting document and a good step towards allowing customers and
developers to adopt MXNet faster.

Just one quick question: How would your proposed design handle
compatibility between old and new versions of MXNet as well as other
frameworks? Since serde (import/export) is part of the MXNet source, we
won't be able to update it independently. One example I'm thinking about is
training on the latest version of MXNet and running inference on an older
version. Could this cause issues since the ONNX model could be of a higher
version than the import on the old MXNet version is able to load? Would it
be necessary to have some kind of compatibility mode during the export
process in which you define the target ONNX model version? There might also
be different operator versions etc.

Best regards,

On Fri, Feb 23, 2018 at 1:15 AM, Roshani Nagmote <roshaninagmo...@gmail.com>

> Hi all,
> I wanted to follow up on the proposal I sent before.
> https://cwiki.apache.org/confluence/display/MXNET/
> Proposal%3A+ImportExport+
> module
> It will be great if you can provide your feedback or suggestions.
> Thanks,
> Roshani
> On Thu, Jan 18, 2018 at 4:47 PM, Roshani Nagmote <
> roshaninagmo...@gmail.com>
> wrote:
> > Hello all,
> >
> > I have written an initial design proposal for a `serde`(temporary name)
> > module for importing and exporting different model formats like onnx,
> > coreml to and from MXNet.
> >
> > Please take a look and feel free to provide suggestions in the comment
> > section.
> >
> > https://cwiki.apache.org/confluence/display/MXNET/
> > Proposal%3A+ImportExport+module
> >
> > Note: I will be traveling next week with limited access to emails. So,
> > responses might be delayed.
> >
> > Thanks,
> > Roshani
> >

Reply via email to