-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Symbolic .json file not compatible with .params file generated since MXNet 1.2 #11091
Comments
Using a module to save_checkpoint or gluon’s export would be OK. Getting mixed with Gluon’s save and Symbol’s save is so bad. |
@nswamy please label - "Breaking","Bug", "Gluon" |
One way I think we could fix that issue would be to have by default |
SGTM |
A more in-depth analysis written by @piiswrong about the cause of the issue and possible solutions: Background The change The complaint from user The cause Faults on our part
Solutions
Pros
Cons
2. Issue warnings and error messages to instruct users to move to `export` and `import`, and stop depending on undefined behavior Pros
Cons
For both solutions we can add more documentation and helper API to minimize impact. Current open PRs related to this issue: #11236 #11127 #11210 |
Since
MXNet 1.2.0
one possible way of serializing Gluon models is not working anymore.Reproducible here:
Gives the following error:
Whilst it worked in
1.1.0
.This way of exporting symbol is recommended in this tutorial on the straight dope
The current recommended way, as described in the upcoming tutorial here, is to use the hybridized
.export()
function.this would look like that, and works in
1.1.0
and1.2.0
:This is affecting people who were until now using this method.
@ifeherva reported this issue is affecting his team.
@piiswrong @marcoabreu @szha
The text was updated successfully, but these errors were encountered: