Nuclear Data Section
International Atomic Energy Agency
P.O.Box 100, A-1400 Vienna, Austria
Memo CP-D/567
Date:
To:
From:

8 June 2009
Distribution
O. Schwerer, N. Otsuka, S. Dunaeva

Subject:

Conclusions and Actions of the 2009 NRDC meeting

Please find attached the Conclusions and Actions of the 2009 NRDC meeting inVienna.
Please give your feedback about any mistakes or omissions by the end of June. The
complete meeting report, including also a meeting summary, the status reports of thecentres and part of the working papers, will, as usual, then be published as an INDC
report.
Remember also that the status reports, working papers and PowerPoint presentations
presented at the meeting are available from our NRDC web page (http://wwwnds.iaea.org/nrdc/nrdc_2009/ )Distribution:
a.mengoni@iaea.org
blokhin@ippe.ru
chiba@earth.sgu.ac.jp
claes.nordborg@oecd.org
ganesan@barc.gov.in
gezg@ciae.ac.cn
hasegawa@nea.fr
henriksson@near.fr
hongwei@ciae.ac.cn
jhchang@kaeri.re.kr
kaltchenko@kinr.kiev.ua
katakura.junichi@jaea.go.jp
kato@nucl.sci.hokudai.ac.jp
kirarlyb@atomki.hu
l.vrapcenjak@iaea.org
manuel.bossant@oecd.org
manokhin@ippe.ru
mmarina@ippe.ru
mwherman@bnl.gov
nicolas.soppera@oecd.org

nklimova@kinr.kiev.ua
n.otsuka@iaea.org
nrdc@jcprg.org
oblozinsky@bnl.gov
ogritzay@kinr.kiev.ua
otto.schwerer@aon.atsamaev@obninsk.ru
s.babykina@polyn.kiae.su
scyang@kaeri.re.krs.dunaeva@iaea.org
stakacs@atomki.hu
stanislav.hlavac@savba.sk
taova@expd.vniief.ru
tarkanyi@atomki.hu
varlamov@depni.sinp.msu.ru
vlasov@kinr.kiev.ua
vmclane@optonline.net
v.zerkin@iaea.org
yolee@kaeri.re.kr

CONCLUSIONS AND ACTIONS
Conclusions
GeneralC1

The next full NRDC meeting will be held in Sapporo, Japan, 20-23 April 2010.
EXFOR, GeneralC2
C3

C4C5If a title cannot be found for an entry, this entry should be entitled “No title”, and anexplanation should be given as a comment.
It is emphasized that parameters, such as decay data (especially half-lives in activation
measurements), and monitor data, as well as the description of the experimental technique(method, analysis etc.) as used by authors, must be properly compiled. The importance of
this information was confirmed in the follow-up of EXFOR “outliers” found by WPECsubgroup 30.
It is emphasized that the source of numerical data must clearly be specified under STATUS(“Table x”, “Fig. x”, “sent from author”, etc.)
For works published by the n_TOF collaboration, the new institute code 2ZZZNTF, and theabbreviation nTOF to be used under AUTHOR for the majority of authors’ names, shouldbe used.

EXFOR, technical
C6C7C8C9C10C11C12C13C14C15

The proposal on resonance quantities (WP2008-27) is now accepted:
The resonance parameter flag in dictionary 236 is kept only for actual resonance parameters
but not for quantities “at resonance” such as “cross section at resonance”, because for thesequantities a product should be coded in REACTION SF4 (which is not allowed forquantities with the resonance parameter flag). New Reaction Types CSR and CRP are
introduced for “cross section at resonance” and “partial cross section at resonance”.
The proposal of WP2009-14 on coding of natural isotopic abundances is approved:
1. The value of the abundance used by authors may be given in coded form under SAMPLE,
as described in WP2009-14
2. The new modifier RAB is introduced for a cross section times natural isotopic abundance,
divided by abundance of target of the first term of a REACTION sum.
If the location of FACILITY is unknown, this has to be mentioned in free text.
A reference in which only the facility or general method is described should be coded under
REL-REF with new code I or M. However, references describing the specific experimentcontinue to be coded under the keyword REFERENCE even when they contain no data.
All changes of any subentry must be reported in HISTORY of subent 001. If there arechanges in coded information, they must be reported also in the affected subentry.
It is recommended to include DOI number in entries, when available through Internet,
according to WP2009-25
Whenever kT is given to characterize an incident spectrum, the heading KT should be usedinstead of energy, with appropriate numerical value.
Covariance information in AGS format is useful for EXFOR compilation.
It is recommended to give ranges of partial uncertainties as coded information under ERRANALYS (see Memo CP-D/530 Rev.)
It is recommended to describe in free text any additional important information related topartial uncertainties, which cannot be given in coded form.

C16

The REACTION SF9 code EXP is made obsolete, as the data type ‘experimental’ is anyway
the default for all REACTIONs and the use of EXP in some but not all cases is confusing.
EXFOR software

C17
C18

C19

Exfor Editor Workshops are very important for compilers, as they give them an opportunity
to fully test and familiarize them with the program and help in its further development
It is recommended to hold workshops on EXFOR related software every two years inconnection with the technical NRDC meetings. This will enable the participants to gain
practice in the use of different software packages and will facilitate the software exchange
among the centres and the collaboration in its design and development.

Concerning digitizing software, it is recommended to use GSYS for figures withgood quality, and to use Graf_new for figures with bad quality.

Actions
GeneralA1Dunaeva

Add Actions A1 – A5 of last year’s meeting (see WP2009-01) to NRDC
ProtocolEXFOR, GeneralA2All(Standing Action) All Centres should give highest priority to compiling newpublications.
(Continuing Action) Continue to develop sensible means of datacommunication between laboratories and the network via the major journals.
Add link from EXFOR DB website on how to cite EXFOR entry (first author,full reference, EXFOR DB version, Web-address).
(Continuing Action) Give priority to compilation of remaining papers from the2007NICE conference.
(Continuing Action) Make efforts to change all remaining upper case entries tolower and upper case. On retransmission, the old entries must be checked andany other necessary corrections must be done.
(Continuing Action) Further develop EXFOR+ (interpreted/extended EXFORformat).
Add information about JANIS Checker code to “Short Guide for EXFORcompilers”(Continuing Action) Update Dictionaries every three months.

A3NDS

A4Zerkin

A5All

A6All

A7Zerkin

A8CJD

A9Otsuka

A10Zerkin(Continuing Action) Synchronize every three months EXFOR backup-file
distribution with (a) full Dictionary distribution; (b) EXFOR in C4 format; (c)Dictionaries in MS Access.

A11Dunaeva,Zerkin(Continuing Action) Send list of found errors to NRDC after every new
EXFOR/CINDA dictionary transmission.

A12All(Continuing Action) Correct errors within own area (see also list in WP200903); all mistakes from such lists (produced according to Action A11) should becorrected in the next transmission (although mistakes which still remain from2007 may take longer).

A13
A14Zerkin
AllA15Zerkin

A16

NNDC

A17

NNDC,NDS

A18Zerkin

A19Otsuka

A20NDSA21A22All
NEA DB

Include DOI in EXFOR DB as defined in WP2009-25.
If DOI is found through Internet, include DOI in all new entries, starting withsymbol “#” in a new line after the relevant reference(Continuing Action) Introduce on public NRDC webpage the “Currentcompilation” after changing the following labels: “reserved” to “allocated”;“prelim” to “being compiled”; “not reserved” to “not allocated”.
(Continuing Action) For a trial period of one year (2009), NNDC will be fully
responsible only for the compilation of articles from four journals (PR/C, PRL,NSE, CJP) and AIP conference proceedings (see modified WP2008-34).
(Continuing Action) Prepare report for the next full NRDC meeting describing
the advantages and disadvantages of compilation on the basis of full journal
contents (see Action A16).
(Continuing Action) Add hyperlink on the main EXFOR page to the EXFOR
Basics manual.
(Continuing Action) Send list of recognised errors, based on analysis of the list
formulated by OECD-NEA WPEC subgroup 30, to responsible centres.
(Continuing Action) Coordinate compilations according to journal distribution
as agreed at the 2008 NRDC meeting.
Correct all mistakes from WP2009-04 till October 2009
Distribute JANIS –TRANS Checker Log list on every preliminary TRANSfile.

Common EXFOR/CINDA dictionaries
A23NNDC,NDS(Continuing Action) Investigate Dictionary 25 for differences in labels andunits (e.g.: MUB, MU-B and MICRO-B used for ‘μb’), with the aim ofachieving consistency.

CINDA
A24

NEA DB

A25NEA-DB

A26

NEA-DB(Continuing Action) Search for experimental and mixed entries in which thetarget is coded by MNY, and replace with individual isotope/compoundentries as outlined in WP2008-36.
(Continuing Action) Correct errors detected during CINDA loading
procedure, as described in WP2008-36.
(Continuing Action) Correct all CINDA lines, as described in WP2009-30(see Action A45).

EXFOR, technical
A27
A28

AllOtsuka

A29AllA30AllCorrect all mistakes listed in WP2009-18(Continuing Action) Review the various types of gamma spectra in EXFOR,
and the related quantities and units.
(Standing Action) When coming across report codes in Dictionary 6 which
differ significantly from what is shown on the cover, submit additional
explanation to NDS for inclusion.
(Standing Action) Run CHEX in TRANS mode (not DATA mode) when

A31All

A32NDS

A33AllA34Zerkin

A35AllA36All

A37
A38
A39Zerkin
OtsukaOtsuka

A40Otsuka

A41NDS

A42
A43
A44Otsuka
NEA DBNDS

A45
A46

NDS
NEA DB

A47
A48

OtsukaNDS

A49

ZerkinA50

Allchecking new entries or TRANS files, to make sure that all important errors
are found.
(Continuing Action) Check error lists available on the NRDC web page, andcorrect as soon as possible (see also WP2009-02).
(Standing Action) Assess the need for undertaking both trivial and non-trivialcompilation corrections, and inform responsible centres.
(Standing Action) Respond within two months concerning nature ofcorrection (trivial or non-trivial) and whether correction(s) will be carried out
by responsible centre - based on Action A32.
(Continuing Action) Prepare a new database encompassing correction factors
and relevant comments for suspect/erroneous data (X4-evaluated). Specify theformat and issue an appropriate manual.
If data are still not available from authors within three months after
publication, provide full EXFOR compilation of the article without numericaldata.
(Continuing Action) Use alteration flags in col. 11 of ENTRY and SUBENT
lines in re-transmission (also optional for all corrected lines in col. 80).
Check the situation with distribution of dictionaries in MS Access format
Prepare final version of memo “Uncertainty propagation in TOF-data”
Add to Dictionary 34 new quantity modifier RAB (Times natural isotopicabundance, divided by abundance of target of first term of REACTION sum)
Add to Dictionary 236 new combination: SIG,,RAB (Cross section times
natural isotopic abundance, divided by abundance of target of first term ofREACTION sum)
Correct LEXFOR and EXFOR formats manual according to WP2009-17 for
keyword INSTITUTE
Add new codes I and M to REL-REF Dictionary according to WP2009-19
Send list with incorrect authors names and Titles to NRDC participants
Make corrections (trivial) according to the list from Action A43 in agreementwith responsible centre
Update LEXFOR according to proposals from WP2009-21, WP2009-22
Prepare full list of recommendations for spelling of nuclides andmathematical expressions in free text of EXFOR entries
Change flag of EXP (SF9) to Obsolete
Prepare the list of existing entries with “NODATA” and add it to NRDCwebpage
Report about conclusions of discussion about new database encompassing
correction factors and relevant comments for suspect/erroneous data (X4evaluated).
In retransmissions change obsolete code SIG/SUM (Memo 4C-4/175 rev) toSIG

EXFOR software
A51

All centres

A52

Otsuka

A53

All

A54

All

A55

Sarov, NDS(Standing Action) Inform each other about EXFOR-related software being
used and/or developed.
Organise internal NRDC webpage “Tools for compilation” for all softwarethat can be useful to compilers(Standing Action) Provide feedback on the digitizing software GSYS toJCPRG.
(Standing Action) Provide feedback to NDS on the existing CHEX version(on bugs as well as desired refinements)
Continue development and testing of the EXFOR-Editor in cooperation withNDS and other data centres, taking into account compilers’ remarks.

A56
A57

NEA DBAll

Make available JANIS –TRANS Checker code to NRDC community
Provide feedback on the JANIS –TRANS Checker code