mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergio Fernández <wik...@apache.org>
Subject Re: backward compatibility of models saved with 1.2.0
Date Tue, 29 May 2018 18:50:17 GMT
Hi Mario,

I can't give you much details. But it looks there is a bug exporting the
parameters' names to a JSON models.

I wonder if anybody else in the community has faced this bug.

Cheers,


On Mon, May 28, 2018 at 5:42 PM, Marco de Abreu <
marco.g.abreu@googlemail.com> wrote:

> Hello Sergio,
>
> you are right. We are following semantic versioning and thus, every model
> produced within the same major version (e.g.1.x) has to be backwards
> compatible.
>
> Could you please provide a small example so we can reproduce this? We
> definitely do not want our users to retrain their model if they update
> MXNet. That's a serious issue and we'd love to follow up.
>
> Best regards,
> Marco
>
> Sergio Fernández <wikier@apache.org> schrieb am Di., 29. Mai 2018, 02:35:
>
> > Hi,
> >
> > I can't find anything related on that in the 1.2.-0-incubating changelog,
> > so I assume models produced by the latest version would be backward
> > compatible with old versions, such as 1.1.0. But we've found that the
> > parameter model produced is very different and doesn't load.
> >
> > Can you point me to any documentation that could help us to load the
> model
> > in 1.1.0 without re-training?
> >
> > Thanks.
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message