Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Urgent! ValueError: Bad serialized model or bad model name #193

Closed
1 of 4 tasks
janosh opened this issue Nov 17, 2023 · 4 comments
Closed
1 of 4 tasks

[Bug]: Urgent! ValueError: Bad serialized model or bad model name #193

janosh opened this issue Nov 17, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@janosh
Copy link
Collaborator

janosh commented Nov 17, 2023

Email (Optional)

No response

Version

0.8.5

Which OS(es) are you using?

  • MacOS
  • Windows
  • Linux

What happened?

matgl is holding up the whole MP stack with this error

ValueError: Bad serialized model or bad model name. It is possible that you have an older model cached. Please clear your cache by running python -c "import matgl; matgl.clear_cache()"

/opt/hostedtoolcache/Python/3.11.6/x64/lib/python3.11/site-packages/matgl/utils/io.py:213:

It's affecting pymatgen, atomate2, matcalc, emmet, ...
Please add tests for whatever broke so this doesn't happen again!

Code snippet

No response

Log output

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@janosh janosh added the bug Something isn't working label Nov 17, 2023
@shyuep
Copy link
Contributor

shyuep commented Nov 17, 2023

Erm, I think the error message says it all? @kenko911 You need to change the model number when you make internal changes like the stress computation. Otherwise the loading of the models can be wrong.

@janosh
Copy link
Collaborator Author

janosh commented Nov 17, 2023

How come there's no test that caught this?

@ucarh
Copy link

ucarh commented Feb 7, 2024

I had this error with python 3.12, downgrading it to 3.9 solved the issue.

@shyuep
Copy link
Contributor

shyuep commented Feb 7, 2024

DGL (the underlying dependency) is not even available on py3.12. In general, we would recommend using Py3.10 (or at most one version below the latest Python, which usually has bugs as well as a lot of unsupported dependencies).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants