Fixed an incorrect half-life for Se-79. Our apologies to users effected.
As always, we encourage users to make requests for radionuclides as well as feature requests. Use the contact link to send us your requests.
RadToolz vers. 3.42 Released
Based on a user request, RadToolz now has additional fission products:
- Added niobium-94 (Nb-94), niobium-95 (Nb-95), and zirconium-95 (Zr-95)
- Confirmed and updated half-lives per reference
Impact of Three Mile Island, Chernobyl and Fukushima Accidents
Imagine the surprise when this Forbes article was published. The article discusses the initial projected deaths from the Fukusima accident, but immediately states the revised estimates based upon the best-available science associated with risk from radiation. The author continues with a comparison of the other two accidents using relevant comparable data from other industrial accidents. Overall, the ariticle is worth a read with a cup of coffee to give a more realistic perspective on these accidents and the nuclear power industry.
Verification of Downloaded File
In order for our users to verify the integrity and authenticity of downloaded binary files, the SHA3-512 hashes for both the 32-bit and 64-bit XLL files has been added to the Installation and Download Verification page.
What is file verification? Directly from the Wikipedia description (https://en.wikipedia.org/wiki/File_verification):
File verification is the process of using an algorithm for verifying the integrity of a computer file. This can be done by comparing two files bit-by-bit, but requires two copies of the same file, and may miss systematic corruptions which might occur to both files. A more popular approach is to also store checksums (hashes) of files, also known as message digests, for later comparison.
File integrity can be compromised, usually referred to as the file becoming corrupted. A file can become corrupted by a variety of ways: faulty storage media, errors in transmission, write errors during copying or moving, software bugs, and so on. Hash-based verification ensures that a file has not been corrupted by comparing the file's hash value to a previously calculated value. If these values match, the file is presumed to be unmodified. Due to the nature of hash functions, hash collisions may result in false positives, but the likelihood of collisions is often negligible with random corruption.
File authenticity is often desirable to verify that a file hasn't been modified in transmission or storage by untrusted parties, for example, to include malicious code such as viruses or backdoors. For this purpose, cryptographic hash functions are employed often.
What is file verification? Directly from the Wikipedia description (https://en.wikipedia.org/wiki/File_verification):
File verification is the process of using an algorithm for verifying the integrity of a computer file. This can be done by comparing two files bit-by-bit, but requires two copies of the same file, and may miss systematic corruptions which might occur to both files. A more popular approach is to also store checksums (hashes) of files, also known as message digests, for later comparison.
File integrity can be compromised, usually referred to as the file becoming corrupted. A file can become corrupted by a variety of ways: faulty storage media, errors in transmission, write errors during copying or moving, software bugs, and so on. Hash-based verification ensures that a file has not been corrupted by comparing the file's hash value to a previously calculated value. If these values match, the file is presumed to be unmodified. Due to the nature of hash functions, hash collisions may result in false positives, but the likelihood of collisions is often negligible with random corruption.
File authenticity is often desirable to verify that a file hasn't been modified in transmission or storage by untrusted parties, for example, to include malicious code such as viruses or backdoors. For this purpose, cryptographic hash functions are employed often.
RadToolz vers. 3.41 Released
The plutonium equivalent curie function (PECi) was revised to be more consistent with the Waste Isolation Pilot Plant (WIPP) methodology described in DOE/WIPP-03-3174, Appendix B and U.S. Department of Energy guidance regarding AMAD for occupational dose conversion factors (ICRP 68). Specifically, the normalization is now done with the dose conversion factor for Pu-239 using lung absorption type M and AMAD of 5 micron (for ICRP 68). The affect of this change is evident when evaluating the PE-Ci for Pu-239 with an AMAD of 1 micron:
=PECi("Pu-239",1,68,"M",5) returns 1
=PECi("Pu-239",1,68,"M",1) returns 1.46875
Previously, the normalization was done with the same lung absorption type and AMAD as the radionuclide of interest. This caused erroneous results for some combinations.
=PECi("Pu-239",1,68,"M",5) returns 1
=PECi("Pu-239",1,68,"M",1) returns 1.46875
Previously, the normalization was done with the same lung absorption type and AMAD as the radionuclide of interest. This caused erroneous results for some combinations.
RadToolz vers. 3.40 Released
Based on a user function request, RadToolz now has one additional function:
As always, we encourage users to make requests for radionuclides as well as feature requests. Use the contact link to send us your requests.
- AValue() - Returns the 10 CFR 71, Appendix A, Table A-1 value for the specified radionuclide in either TBq or Ci
As always, we encourage users to make requests for radionuclides as well as feature requests. Use the contact link to send us your requests.
RadToolz vers. 3.30 Released
Based on a user function request, RadToolz now has one additional function and other improvements:
- FGE() - calculates Pu-239 or U-235 fissile gram equivalents
- Added curium-247 (Cm-247), californium-249 (Cf-249), and californium-251 (Cf-251)
- Improved error messages
- Improved responses for RTZUpdate()
- Updated references to include ANSI/ANS-8.1-2014 and ANSI/ANS-8.15-2014 used for FGE()
- Revised DCF() to report only 1 micron AMAD for ICRP-72 dose conversion factors
Subscribe to:
Posts (Atom)