-
Notifications
You must be signed in to change notification settings - Fork 917
Fix inconsistent "Van der waals radius" and "Metallic radius" in core.periodic_table.json
#4345
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
Conversation
core.periodic_table.json
core.periodic_table.json
I asked ChatGPT to do some validation. See below. Of course, ChatGPT notoriously can hallucinate. So you might want to just quickly check the discrepancies.
|
Hi @shyuep thanks for helping me double check. This PR doesn't intend to validate the data source itself, but to ensure our For example the vdw radius of Ag is 1.72 in the source CSV and YAML, but is 2.11 in the JSON: pymatgen/dev_scripts/radii.csv Line 48 in e301acd
pymatgen/dev_scripts/periodic_table.yaml Line 111 in e301acd
With #4338, we could then validate the radii or whatever other property, as the final JSON generation would have a more explainable/reliable pipeline. |
… in `core.periodic_table.json` (materialsproject#4345)" This reverts commit bdc448f.
…ook (#4372) * add new values that are absent from CSV at all * remove fixed issues * regenerate json and yaml * add Ge vdw radius * remove legacy electron_affinities.yaml * manually recover electron affinities for D for now * reapply update from #2122 * Revert "Fix inconsistent "Van der waals radius" and "Metallic radius" in `core.periodic_table.json` (#4345)" This reverts commit bdc448f. * add note * revert changes to metallic radii * revert change to metallic radii in production json * fix Pa vdw radius
Summary
core.periodic_table.json
Currently some of the radii from JSON is different from our CSV (the YAML is the same):
After this PR:
Script: