php1ic / inch

The Interactive Nuclear CHart
GNU General Public License v3.0
3 stars 2 forks source link

Extract isospin information from NUBASE #14

Open php1ic opened 5 years ago

php1ic commented 5 years ago

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:

007 0048   7Bei    26750       30     10980      30     RQ                     3/2-    T=3/2 03               p ?;3He ?;A ?
007 0050   7B      27677       25                            570     ys 140    (3/2-)        03 11Ch32t  1967 p=100
008 0020   8He     31609.68     0.09                         119.1   ms 1.2    0+            05          1965 B-=100;B-n=16 1;B-t=0.9 1
008 0030   8Li     20945.80     0.05                         839.40  ms 0.36   2+            05 10Fl01t  1935 B-=100;B-A=100
008 0038   8Lii    31768        5     10822       5     RQ                     0+      T=2   05
008 0040   8Be      4941.67     0.04                          81.9   as 3.7    0+            05          1932 A=100
008 0048W  8Bei    21568        3     16626       3                            2+  frg T=1      04Ti06e  2004 A~100

and

011 0050   11B      8667.9      0.4                          stbl              3/2-          12          1920 IS=80.1 7
011 0058   11Bxi   21228        9     12560       9     RQ              T=3/2  1/2+,(3/2+)   12          1963
011 0060   11C     10650.3      0.9                           20.364  m 0.014  3/2-          12          1934 B+=100
011 0068   11Cxi   22810       40     12160      40     RQ                     1/2+    T=3/2 12 71Wa21d  1971 p=?

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.

php1ic commented 3 years ago

It's not even in a consistent place :facepalm:

010 0048   10Bei   33787       20     21179      20     RQ                     (2-)    T=2   07               n ?;p ?;3H ?
010 0058W  10Bxi   13790.8      0.4    1740.05    0.04                         0+      T=1   07               IT=100
011 0058   11Bxi   21228        9     12560       9     RQ              T=3/2  1/2+,(3/2+)   12          1963
011 0068   11Cxi   22810       40     12160      40     RQ                     1/2+    T=3/2 12 71Wa21d  1971 p=?
012 0058   12Bxi   26088       19     12719      19     RQ                     0+      T=2   00 08Ch28j
012 0068   12Cxi   15108        3     15108       3     RQ                     1+      T=1   00               IT=?;A ?

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.