Add ensdf parsing to ignore NN neutron record #1243
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ftessier
force-pushed
the
fix-ensdf-for-nndc
branch
from
045c62c to
718e03f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The NNDC ensdf file for Cf-252 had decays to
NN-6representing neutron nuclei that as far as I can tell is not supported by the ensdf standard. A check for this case has been added, so that these records are ignored. Previously, you would just encounter a crash since NN is not a valid element.The only necessary change is the check for
NN. The other changes I made are just to improve robustness.