Skip to content
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

Table 1-01-01 radionuclide codes #356

Closed
amilan17 opened this issue Nov 16, 2021 · 5 comments · Fixed by #371
Closed

Table 1-01-01 radionuclide codes #356

amilan17 opened this issue Nov 16, 2021 · 5 comments · Fixed by #371

Comments

@amilan17
Copy link
Member

amilan17 commented Nov 16, 2021

Branch

https://github.com/wmo-im/wmds/blob/issue356/tables_en/1-01-01.csv

Summary and Purpose

Review terms and add to WMDS codes if needed.

The TT for TDCF is proposing two new terms for radionuclides:
• Tellurium 131
• Neodymium 137

wmo-im/CCT#65

Stakeholder(s)

Proposal

name description tags
Tellurium [Te-131] IUPAC: tellurium-131, PubChem CID: 6337051, CAS Number: 14683-12-6 radionuclide
Neodymium [Nd-137] IUPAC: neodymium-137 radionuclide

Reason

To keep alignment with MoC CCT table....

Expected Impact of Change

MEDIUM

Inclusion of new code in OSCAR is uncomplicated.

@amilan17 amilan17 added this to the FT-2022-1 milestone Nov 16, 2021
@amilan17 amilan17 changed the title enter table # and brief summary Table 1-01-01 radionuclide codes Nov 17, 2021
@amilan17
Copy link
Member Author

@gaochen-larc Can you respond to this issue?

@fstuerzl
Copy link
Member

@amilan17, @gaochen-larc, I've created a branch and updated the proposal, so that the variable names and descriptions align with the other radionuclide variables.
As you seem I wasn't able to find a CAS number or a PubChem CID for Nd-137...

@gaochen-larc
Copy link
Contributor

From the information I found, it appears that Nd-137 does not exist in natural environment. This raise a question if this variable should be added. Looking for clarifications...

"In 1970 137Nd was reported in “135mCe and 137mNd: Isomeric States in N = 77 Isotones” by Droste et al. [20].
The Dubna U-300 cyclotron accelerated 18O and 20,22Ne beams which bombarded tellurium and tin targets, respectively. 137Nd was produced in the fusion-evaporation reactions 119Sn(22Ne,4n), 122Sn(20Ne,5n), 122Sn(22Ne,7n), and
126Te(18O,7n). Conversion electron and γ-ray spectrometry was used to identify the isotope. “In all cases, γ-rays of
108, 177, 233 and 285 keV which all decay with the same half-life, T1/2 = 1.60±0.15 s were observed... That the new
activity belongs indeed to the nucleide 137Nd is proved by (i) the energy difference of the K and L electron lines of the
isomeric transition EKL = 37.0±0.8 keV as compared to the value 36.8 keV expected for Z = 60(Nd), and (ii) the shape
of the excitation functions from which the number of evaporated neutrons can be determined” The reported half-life
corresponds to an isomeric state and is currently the accepted value for this state. Previously the 55.0(15) m half-life of
136Nd had incorrectly been assigned to 137Nd [16]. A half-life of 35(5) m corresponding to the ground state was reported
already in 1935 [21], but no mass assignment was made."

https://people.nscl.msu.edu/~thoennes/2009/neodymium-adndt.pdf

@joergklausen
Copy link
Contributor

I believe we need a requirement to be expressed from CTBTO. If this is relevant for them, then we can include it, otherwise I would also not take it. I recommend Michel Mirsch (Michael.Mirsch@dwd.de) be invited to comment. He helped with a previous issue #212.

@joergklausen
Copy link
Contributor

joergklausen commented Dec 7, 2021

Based on the discussion that has taken place under wmo-im/CCT#65, this issue is ready for FT. The branch is valid.

@amilan17 amilan17 linked a pull request Dec 22, 2021 that will close this issue
amilan17 added a commit that referenced this issue Jan 5, 2022
issue #356 
* Update 1-01-01.csv
* Github Action Commit
Co-authored-by: Franziska Stürzl <72029328+fstuerzl@users.noreply.github.com>
Co-authored-by: amilan17 <amilan17@users.noreply.github.com>
@amilan17 amilan17 closed this as completed Apr 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants