-
Notifications
You must be signed in to change notification settings - Fork 68
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
Element 118 is missing from the data tables #245
Comments
Yes, 118 is missing because we used the periodic table NIST had provided in JSON (and 118 was unlikely to come up in quantum chemistry). Then they discontinued publishing in structured format (see raw_data/nist_data/README). Judging from the coarse changelog, the data is from before Version 9. I see now that there's an ascii format https://physics.nist.gov/cgi-bin/Compositions/stand_alone.pl?ele=&all=all&ascii=ascii2&isotype=all . It'd be good to switch harvesting to that. Thanks for the reminder. |
I tested harvesting the ASCII file and it is OK if not very convenient. The ASE actually has a convenience function that might be useful that points to some type of "hidden" perl script: https://wiki.fysik.dtu.dk/ase/_modules/ase/data/isotopes.html#download_isotope_data I noticed that there is some arbitrariness when it comes to the most common isotope for elements that don't occur naturally (radioactive isotopes). Convention seems to be to take the most stable isotope in terms of half-life, but this rule is also violated in some codes for different purposes (for example mendeleev). I think the old version of the NIST data that you got from the JSON had "erroneous" selections for some of the most stable isotopes judging from their changelog. Current NIST data seems to instead omit the preferred isotope for these elements. Here is a nice compilation of the most stable isotopes Reference data on the most stable isotopes can be found here but I haven't found any machine readable files. |
Element 118 (Oganesson) is absent from the periodic table (and probably other places as well). I would guess this is due to presence of the dummy atom with atomic number 0.
The text was updated successfully, but these errors were encountered: