You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are isospin values for 195/5511 in 2012 and 205/5625 in 2016.
Currently we just remove them from the line and ignore. We could add a new member to Nuclide, but values exist for such a small fraction of isotopes I'm not sure what we would actually do with it.
The text was updated successfully, but these errors were encountered:
php1ic
changed the title
Extract isospin information
Extract isospin information from NUBASE
Mar 9, 2019
regex and a sub_match with something like "T=.* " may be the way to go, but this is a totally different technique to how the other values are extracted.
The 2012 and 2016 nubase files added isospin, but in a way that can overlap with the spin parity values and the error on half-life.
Two examples are:
and
There are isospin values for 195/5511 in 2012 and 205/5625 in 2016.
Currently we just remove them from the line and ignore. We could add a new member to Nuclide, but values exist for such a small fraction of isotopes I'm not sure what we would actually do with it.
The text was updated successfully, but these errors were encountered: