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

[WIP] Update atomic masses to AME2020 #1385

Draft
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

alexmalins
Copy link
Member

Description

The Atomic Mass Data Center (AMDC) released an updated Atomic Mass Evaluation (AME2020) dataset in March. This is a work-in-progress PR to update from the old AME2016 data (#1281).

Motivation and Context

Updates atomic mass unit data.

Changes

AME mass data update.

Behavior

Atomic mass data changes slightly.

Other Information

I think the core source updates are OK - they are a copy of PR #1281's code changes, as well as one regex update due to a format change between AME2016 and AME2020.

However running nuc_data_make --clean 2 --fetch-prebuilt False --make atomic_mass,materials is currently unsuccessful for building the new nuclear data. The issues are described in #1333. The first problem is KAERI data is no longer hosted on data.pyne.io. I got around this by hosting the kaeri.zip on my website and using that link, but then I ran up against the super-heavy elements issue and downloads failing as KAERI's data website is offline.

Once #1333 and pyne/data # 24 are ready, I will return to this PR and complete the second step needed - updating all the tests.

Changelog file

Will fill out changelog once everything is successful.

@alexmalins
Copy link
Member Author

The KAERI data website is back online as of tonight. However the link format PyNE dbgen kaeri.py is using to pull data from (e.g. http://atom.kaeri.re.kr/cgi-bin/nuclide?nuc=K) is 404ing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant