Texas A&M University US Nuclear Data Program Evaluation Issues

Texas A&M University US Nuclear Data Program TAMU NSDD CENTER Miscellanea of an ENSDF evaluator (evaluation issues) N. Nica

Miscellanea of an ENSDF evaluator There There are every every day while while some the the policy policy level needs needs good good policies are numerous numerous evaluation day evaluators evaluators life some are are not not so level and and some policies. . Here evaluation problems life. . Some Some of of them so much, much, which which means some maybe maybe not Here we we present present some problems that them are means that not. . However However good some of of these that need need attention are more more important that some some may may trigger good governance these: : attention in in important trigger governance A Suggestion for A Suggestion for BrIcc NuDat NuDat v.s v.s ENSDF 0 vs. 0.0 0 vs. 0.0 ENSDF ENSDF Analysis and Utility Programs Analysis and Utility Programs Version Keeping track of Analysis and Utility Programs BrIcc ENSDF Version

1. Suggestion for BrIcc Standard Standard BrIcc BrIcc comment: comment: 147GD 147GD CG 147GD2CG 147GD2CG MR=1.00 FOR MR=1.00 FOR E3 CG MR$IF MR$IF NO VALUE GIVEN IT WAS ASSUMED MR=1.00 FOR NO VALUE GIVEN IT WAS ASSUMED MR=1.00 FOR E2 E3/ /M2 M2 AND MR=0.10 FOR THE OTHER MULTIPOLARITIES AND MR=0.10 FOR THE OTHER MULTIPOLARITIES E2/ /M1 M1, , However, However, in in many multipolarity multipolarity and almost almost always always forget review review (resulting (resulting from PROPOSAL: Could BrIcc detect automatically when this comment is applicable, and insert it only in such cases? many situations situations there and the the comment comment is is not forget to to delete from running running BrIcc there is is none not applicable applicable. . For delete these these comments comments even BrIcc up up to to the none of of transitions transitions is is M For most even at at the the post post- -review M2 2 or these situations situations I I the editorial editorial level review correction correction stage) or E E3 3 or or higher higher most of of these level of of stage). .

2. NuDat vs. ENSDF Frequent reviewer s comment: Frequent reviewer s comment: 90% of users get data (only) through 90% of users get data (only) through NuDat The The evaluator evaluator is is advised advised to of of data data users users using using NuDat NuDat ( (NNDC comment comment blind blind However in many evaluator s decisions comment is irreplaceable! However in many evaluator s decisions comment is irreplaceable! PROPOSAL: 1. Advise NuDat and LiveChart users on the opening page to go to ENSDF for a more thorough view of the piece of data they need 2. Try to educate data users about the architecture of data evaluation: that ENSDF is the primary site (built from particular datasets making the adopted, where things are explained); then data is taken by the data only environments NuDat will not see any comment will not see any comment tune the the particular particular situation situation for NNDC) ) or or LiveChart LiveChart (IAEA) to tune for the that are the bulk bulk are (IAEA) that

3. 0 vs. 0.0 G G. .s s. . is is usually I I do do not not remember missed missed it) it) Tom Tom Burrows Burrows recommended However However I I found found many It It might might be be that that for for for g g. .s s. . However However it it might might be gammas gammas, , where where level signify signify that that while while the But But is is that that true? true? PROPOSAL: Make a general rule for the g.s. 0.0 vs. 0 usually adopted adopted as remember a a policy as 0 0. .0 0 policy item item in in this this respect respect (if (if it it does does exist, exist, I I might might simply simply recommended me many situations situations in in ENSDF for some some evaluators evaluators there me to to adopt ENSDF when there is is no adopt ALWAYS ALWAYS 0 0. .0 0 for when the no difference difference in in between for g g. .s s. . given as between 0 0. .0 0 and the g g. .s s. . is is given as 0 0 (even (even 0 0. .) ) and 0 0 be that that for level energies energies usually the lowest lowest found for others others the usually have found state, the use have larger state, this this could use of of 0 0 is is for larger unc s could be for reaction reaction datasets unc s so so perhaps be not not the the g g. .s s. ., , which datasets with perhaps 0 0 might which is is 0 0. .0 0 with no might no

4. ENSDF Analysis and Utility Programs Version Distributed Distributed by ( (https https: ://www The The more more familiar ( (https https: ://www //www- -nds The The old old page page gives Both Both pages pages have like like more more work Many Many times, times, e e. .g g. . when that that I I use use the the latest Jun Jun- -2020 2020) ) as PROPOSAL: - Can be good that Version/Date should be posted in full by the distribution pages: not only 2020/08 date, or Version 2 instead of Version 2.3e - Alternatively this info can be given in the name of the .exe code, like e.g.: BrIcc_v2.3e_17-Jun-2020.exe (Jun already put the date in the name) by the the NSDD //www- -nds nds. .iaea familiar distribution nds. .iaea gives some have some some information work should should be when asking latest version, version, we as it it appears appears when NSDD GitHub GitHub Repository iaea. .org org/public/ /public/ensdf_pgm distribution page page still iaea. .org org/public/ /public/ensdf_pgm some details details about about the information about be done done asking the the programmer we need need the when running running the Repository page ensdf_pgm/ /) ) still available available ensdf_pgm/ /index_old the version version of about the the last page NEW! NEW! index_old. .htm of the the codes last version/date version/date of htm) ) codes (not (not all) of the the code all) code but but it it looks looks programmer of the exact exact version the core core of the the code version of code about about it, of a a code, code, e e. .g g. . BrIcc it, or or simply simply checking BrIcc v v2 2. .3 3e e ( (17 checking 17- -

5.Keeping track of Analysis and Utility Programs An An evaluation evaluation can entering entering ENSDF I I typically typically spent codes codes can can change More More generally generally we codes codes and and after problems problems emerged There There are are codes the the initial initial programmer programmer has However However keeping keeping track PROPOSAL: - One can keep track of the codes by making them place a d comment in the dataset about version & date each time we run the code. - This is a way to prompt an evaluator to check for the currency of the codes for each mass chain. can stay stay many many years years in in the the evaluation evaluation pipe pipe before before being being published published and and ENSDF. . spent several change. . we do after several emerged. . codes (Ruler, several years years on on a a mass mass chain chain in in the the evaluation evaluation pipe pipe during during which which the the do not not keep several years keep track years it it is is difficult track of of the difficult to the versions versions and to see see what and sub what code sub- -versions versions of of our code was was used our evaluation evaluation used in in case case some some (Ruler, Gabs) has changed track of of the Gabs) that changed the the codes codes remains that were were used the program remains unclear used for program was unclear for many many years was re re- -written years with written of of refurbished refurbished. . with some some bugs bugs and and after after