Version: 1.3.1 (using KDE 3.4.2, Gentoo) Compiler: gcc version 3.3.5-20050130 (Gentoo 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1) OS: Linux (i686) release 2.6.11.11 Some isotope rates don't add up to 100%: Helium: 99.99993% Neon: 99.97000% Sulfur: 100.05600% Potassium: 99.98810% Krypton: 99.69000% Mercury: 6.87000% (??) Probably more, didn't check all of them.
J
Sorry, can't provide any data. I was just browsing kalzium and for all I know, percentages should add upp to 100%, especially mercury falls quite short. I'd suggest to round the available percentages to one significant digit (instead of 5 digits for some elements). If there are isotopes whose percentages are less than 0.1, indicate this by using "< 0.1%" (as e.g. done in statistical software packages if they can't determine a more accurate value). I wouldn't expect anyone to object if some percentages are rounded or just chopped of. in my eyes, it's more obvious if the overall count doesn't sum up to 100% than that the percentage of isotope XY is actually 34.335 instead of 34.3 ...
This is what Jörg Buchwald posted on the kalzium-mailinglist (kalzium@kde.org). If you have question, tips or suggestions for Kalzium just mail it to that mailinglist. From Jörg: > Mercury: 6.87000% (??) I get 100.006 percent. The reason is that there are different data in literature, so theese are statistic values, which can't determined exactly. In some individual cases it could be that some nuclides are missing. But i'll check it soon.
The list of isotopes of mercury as displayed in 1.3.1: Weight Neutrons Percentage 195.97 116 0.15 203.97 124 6.72 From kalziumrc: Isotopes=116:195,97:0,15;124:203,97:6,72
Can't this bug be closed? We moved the isotope-data to Blueobelisk.org anyway... Jörg?
> Can't this bug be closed? We moved the isotope-data to Blueobelisk.org > anyway... Yes, but the old data still remain in the 3.5 serie...
> Yes, but the old data still remain in the 3.5 serie... Correct. Jörg: It would be possible to convert the improved data in BlueObelsik back to Kalzium, right? We would just need a xml-3.5-writer, the reader of the BO-Obelisk is already in trunk. The xml-3.5-writer could be a quick hack. That way, we would just do one huge commit to the database of KDE 3.5.
I resolved this "fixed" because it is fixed in 4.x and will never be fixed in 3.x as it would introduce quite some new code there.