-
Notifications
You must be signed in to change notification settings - Fork 9
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
templ_enum.cif: explicitly provide the data source for data in the length_neutron save frame #390
Comments
Also, scattering lengths are isotope-specific. Can/should we give a listing for all isotopes? Can we even denote isotopes in the current atom symbol notation? . For completeness, these are the values that TOPAS uses:
|
I will see if I can find the original source of these numbers. Note that the neutron scattering length table is not actually used by the main dictionary (yet). |
Thank you. In case the data for other save frames was also provided in the same place, it would also be useful to get the references for the atomic radii and mass values. |
The values in the tables agree with my 1992 ITVC edition, table 4.4.4.1. Well, at least the Mo discrepancy noted above by @vaitkus doesn't exist. The remaining issues are still present, of course. So I think we can conclude that 1992 ITVC table 4.4.4.1 is the source, plus some other source for Bk. My neutron "blue book" doesn't even have Bk. We should obviously update the tables to properly include imaginary parts and isotopes from the latest IT tabulation. |
The
length_neutron
save frame seemingly contains the bound coherent neutron scattering lengths of elements. However, it is not clear where this data were originally taken from. I have compared it with data from Table 4.4.4.1 in ITC Vol. C (2004) and there are some significant differences:templ_enum.cif
all values are given as real numbers (e.g. values for Sm are given as "0.80(2) - 1.65(2)i" and "4.2" respectively).templ_enum.cif
(e.g. for Po, At, Rn, Fr).templ_enum.cif
(e.g. for Bk and Cf).Since these values are (probably) intended to be used as defaults, it is quite important to track down the data source and explicitly record it in the
temp_enum.cif
file. This could be done by adding the_description.text
attribute or introducing a new attribute altogether (e.g._description.data_source
).The text was updated successfully, but these errors were encountered: