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

10 August 2009
Distribution
O. Schwerer, N. Otsuka, S. Dunaeva

Subject:

Conclusions and Actions of the 2009 NRDC meeting

Please find attached the revised Conclusions and Actions of the 2009 NRDC meetingin Vienna. Feedbacks to the first version (Memo CP-D/567) are taken into account inthis version.
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:
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.uan.otsuka@iaea.org
nrdc@jcprg.org
oblozinsky@bnl.gov
ogritzay@kinr.kiev.ua
otto.schwerer@aon.atr.forrest@iaea.org
samaev@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.pronyaev@iaea.org
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, GeneralC2C3C4C5If 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 inactivation measurements), and monitor data, as well as the description of theexperimental technique (method, analysis etc.) as used by authors, must be properlycompiled. The importance of this information was confirmed in the follow-up ofEXFOR “outliers” found by WPEC subgroup 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 the abbreviation nTOF to be used under AUTHOR for the majority of authors’names, should be used.

EXFOR, technical
C6C7C8C9C10C11The proposal on resonance quantities (WP2008-27) is now accepted:
The resonance parameter flag in dictionary 236 is kept only for actual resonanceparameters but not for quantities “at resonance” such as “cross section atresonance”, because for these quantities a product should be coded in REACTION
SF4 (which is not allowed for quantities 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 underSAMPLE, 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.
The first proposal on institutes coded in INSTITUTE (WP2009-17) is approved:
The keyword INSTITUTE will contain only the laboratories, institutes, oruniversities with which all authors are affiliated.
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 thespecific experiment continue to be coded under the keyword REFERENCE evenwhen they contain no data.
All changes of any subentry must be reported in HISTORY of subent 001. If there
are changes in coded information, they must be reported also in the affected

C12C13C14C15C16C17subentry.
It is recommended to include DOI number in entries, when available throughInternet, according to WP2009-25
Whenever kT is given to characterize an incident spectrum, the heading KT should
be used instead 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 underERR-ANALYS (see Memo CP-D/530 Rev.)
It is recommended to describe in free text any additional important information
related to partial uncertainties, which cannot be given in coded form.
The REACTION SF9 code EXP is made obsolete, as the data type ‘experimental’ isanyway the default for all REACTIONs and the use of EXP in some but not all cases
is confusing.
EXFOR software

C18C19C20
C21

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 furtherdevelopment
It is recommended to hold workshops on EXFOR related software every two years
in connection with the technical NRDC meetings. This will enable the participants
to gain practice in the use of different software packages and will facilitate thesoftware exchange among the centres and the collaboration in its design anddevelopment.
Concerning digitizing software, it is recommended to use GSYS for figures withgood quality, and to use Graf_new for figures with bad quality.
NDS will assist programmers from Sarov when they need expertise ofEXFOR/CINDA dictionary designing the Exfor-Wizard application.
Actions
GeneralA1Dunaeva

Add Actions A1 – A5 of last year’s meeting (see WP2009-01) to NRDCProtocol

EXFOR, General
A2

All

A3NDS

A4Zerkin

A5All

A6All(Standing Action) All Centres should give highest priority to compilingnew publications.
(Continuing Action) Continue to develop sensible means of data
communication between laboratories and the network via the majorjournals.
Add link from EXFOR DB website on how to cite EXFOR entry (firstauthor, full reference, EXFOR DB version, Web-address).
(Continuing Action) Give priority to compilation of remaining papers
from the 2007NICE conference.
(Continuing Action) Make efforts to change all remaining upper caseentries to lower and upper case. On retransmission, the old entries mustbe checked and any other necessary corrections must be done.
(Continuing Action) Further develop EXFOR+ (interpreted/extendedEXFOR format).
Add information about JANIS Checker code to “Short Guide for
EXFOR compilers”(Continuing Action) Update Dictionaries every three months.

A7Zerkin

A8CJD

A9Otsuka

A10Zerkin(Continuing Action) Synchronize every three months EXFOR backupfile distribution with (a) full Dictionary distribution; (b) EXFOR in C4format; (c) Dictionaries in MS Access.

A11A12Dunaeva,Zerkin
All(Continuing Action) Send list of found errors to NRDC after every new
EXFOR/CINDA dictionary transmission.
(Continuing Action) Correct errors within own area (see also list inWP2009-03); all mistakes from such lists (produced according to ActionA11) should be corrected in the next transmission (although mistakes
which still remain from 2007 may take longer).

A13
A14

ZerkinAllA15Zerkin

A16

NNDC

A17

NNDC,NDS

A18Zerkin

A19Otsuka

A20NDS

A21A22All
NEA DB

Include DOI in EXFOR DB as defined in WP2009-25.
If DOI is found through Internet, include DOI in all new entries, startingwith symbol “#” 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 “notallocated”.
(Continuing Action) For a trial period of one year (2009), NNDC will befully responsible only for the compilation of articles from four journals(PR/C, PRL, NSE, CJP) and AIP conference proceedings (see modifiedWP2008-34).
(Continuing Action) Prepare report for the next full NRDC meeting
describing the advantages and disadvantages of compilation on the basisof full journal contents (see Action A16).
(Continuing Action) Add hyperlink on the main EXFOR page to theEXFOR Basics manual.
(Continuing Action) Send list of recognised errors, based on analysis ofthe list formulated by OECD-NEA WPEC subgroup 30, to responsiblecentres.
(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 preliminaryTRANS-file.

Common EXFOR/CINDA dictionaries
A23

NNDC,NDS(Continuing Action) Investigate Dictionary 25 for differences in labels
and units (e.g.: MUB, MU-B and MICRO-B used for ‘μb’), with theaim of achieving consistency.

CINDAA24

NEA DB

A25NEA-DB

A26

NEA-DB(Continuing Action) Search for experimental and mixed entries inwhich the target is coded by MNY, and replace with individualisotope/compound entries 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 WP200833 (see Action A45).

EXFOR, technical
A27
A28

All
OtsukaA29All

A30

All

A31AllA32

NDSA33All

A34Zerkin

A35AllA36AllA37Zerkin

A38
A39Otsuka
Otsuka

A40Otsuka

A41NDSA42Otsuka

Correct 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 checking new entries or TRANS files, to make sure that allimportant errors are found.
(Continuing Action) Check error lists available on the NRDC web
page, and correct as soon as possible (see also WP2009-02).
(Standing Action) Assess the need for undertaking both trivial and nontrivial compilation 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 (X4evaluated). Specify the format and issue an appropriate manual.
If data are still not available from authors within three months afterpublication, provide full EXFOR compilation of the article without
numerical data.
(Continuing Action) Use alteration flags in col. 11 of ENTRY andSUBENT lines in re-transmission (also optional for all corrected lines
in col. 80).
Check the situation with distribution of dictionaries in MS AccessformatPrepare final version of memo “Uncertainty propagation in TOF-data”
Add to Dictionary 34 new quantity modifier RAB (Times natural
isotopic abundance, divided by abundance of target of first term ofREACTION sum)
Add to Dictionary 236 new combination: SIG,,RAB (Cross section
times natural isotopic abundance, divided by abundance of target offirst term of REACTION sum)
Correct LEXFOR and EXFOR formats manual according to WP200917 for keyword INSTITUTE
Add new codes I and M to REL-REF Dictionary according toA43
A44

NEA DB
NDS

A45

NDS

A46

NEA DB

A47
A48

OtsukaNDS

A49

Zerkin

A50

All

A51

Otsuka

WP2009-19
Send list with incorrect authors names and Titles to NRDC participants
Make corrections (trivial) according to the list from Action A43 inagreement with responsible centre
Update LEXFOR according to proposals from WP2009-21, WP200922
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 toNRDC webpage
Report about conclusions of discussion about new databaseencompassing correction factors and relevant comments for
suspect/erroneous data (X4-evaluated).
In retransmissions change obsolete code SIG/SUM (Memo 4C-4/175
rev) to SIG
Update LEXFOR according to the first proposal from WP2009-17

EXFOR software
A52All centres

A53

Otsuka

A54

All

A55

All

A56

Sarov,NDS

A57
A58

NEA DBAll(Standing Action) Inform each other about EXFOR-related software
being used and/or developed.
Organise internal NRDC webpage “Tools for compilation” for all
software that can be useful to compilers(Standing Action) Provide feedback on the digitizing software GSYS toJCPRG.
(Standing Action) Provide feedback to NDS on the existing CHEXversion (on bugs as well as desired refinements)
Continue development and testing of the EXFOR-Editor in cooperation
with NDS and other data centres, taking into account compilers’remarks.
Make available JANIS –TRANS Checker code to NRDC community
Provide feedback on the JANIS –TRANS Checker code