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

8 September 2010
Distribution
N. Otsuka, S. Dunaeva

Subject:

Updates of four NRDC manuals and documents

We are now working for updates of four NRDC manuals (EXFOR Formats Manualand LEXFOR) and documents (NRDC Protocol and Network Document). The latest
versions of these manuals and documents now become available as WS2010-01rev toWS2010-04rev on the Workshop website (http://www-nds.iaea.org/nrdc/wksp_2010/).
EXFOR Formats Manual and LEXFORThey were revised based on discussion in the EXFOR Workshop. These drafts arestill open for your comments until the end of September as proposed in Memo CPD/662. Approval of these two manuals will be asked in the next NRDC meeting(2011).
NRDC Protocol and Network Documents
They have been already approved in the NRDC 2010 Meeting, and open for yourcomments on editorial mistakes only by the end of September. The revised NetworkDocument will be printed and signed by Centre Heads in the next full NRDC meeting(2012).
Revisions asked by the NRDC 2010 meeting
The NRDC 2010 meeting also asks corrections to the NRDC Protocol in Action 2“Add all standing actions to the NRDC Protocol.” Accordingly all standing actions(and also one continuing action) from the meeting were analyzed for revision.
1. A4 (All), A11 (All), A57 (All):
These are suitable for addition to the NRDC Protocol.
2. A24 (Dupont), A42 (NDS), A60(Sarov):
These are tasks assigned to the specific centres, and suitable for addition to“Unique responsibilities within the Network” of the Network Document. NEA
Data Bank and CNPD agree with this proposal.
3. A58 (All), A59 (All), A62 (All):
These actions recommend all centres to provide feedback to the centres
maintaining four codes (GSYS, ZCHEX, JANIS-TRANS Checker). Because
there has been the following sentence in the NRDC Protocol:
Each Centre using one of these programs is invited to contribute suggestions
for updates to the program. The originating Centre will inform other Centres

about codes being used or developed, and also coordinate all program
updates.
, addition of these code names under “Unique responsibilities within theNetwork” of the Network Document” as a definition of “originating Centre”
for each code is suitable. JCPRG and NEA Data Bank agree with thisproposal.
4. A34 (All), A39(All), A44 (Otsuka):
They are relevant to revision of LEXFOR and EXFOR Formats Manual. They
are considered in the last drafts of these two manuals.
5. A40 (All)This is more relevant to Short Guide for EXFOR Compilers maintained byCJD. It was added in to the latest version of the Guide by M. Mikhaylyukova.
All these corrections are summarized below.

1

A4All

2A11All

3

A24Dupont

4A34AllAction (NRDC2010)(Standing Action)
All Centres should givehighest priority tocompiling newpublications.
(Standing Action)
Scan national journals
and send results to NDS.
See also first proposal ofWP2010-14.
(Standing Action)
Distribute JANIS–TRANS Checker Log liston every preliminary
TRANS-file.

(Standing Action)
Create “dummy”
EXFOR file if it is
impossible to findexperimental data.

will be substituted by
NRDC Protocol - EXFOR
Protocol – Data Compilation
Responsibility:“A first priority is given to compile
recently published data.”
NRDC Protocol - EXFOR
Protocol – Journal Scanning
Responsibility:(See end of the memo.)
Network Document Unique responsibilities within theNetwork (NEA DB):“Distribution of comments on new
EXFOR exchange files based oncodes developed by the NEA DataBank.”
It has been already mentioned inLEXFOR – Status as follows:“Unobtainable Data
In the case where a centre is awarethat data exist, but the centre isunable to obtain the data, an entry
may be made in EXFOR to informthe other centres (and their users) ofthe status of the data; this will
eliminate many repeated requests
for the same data and needless
bookkeeping concerning data which
will be entered into the system withextensive delays or not at all.”

5A39

All

(Standing Action)
When coming acrossreport codes in
Dictionary 6, which
differ significantly fromwhat is shown on thereport cover, submit
additional explanation toNDS for inclusion.

6A40

All

7A42NDS

8A44

Otsuka9A57

All(Standing Action)
Run CHEX in TRANS
mode (not DATA mode)
when checking new
entries or TRANS files,
to make sure that allimportant errors arefound.
(Standing Action)
Assess the need forundertaking both trivial
and non-trivial
compilation corrections,and inform responsibleCentres.
(Standing Action)
Add this action toEXFOR Manual: ”Usealteration flags in col. 11of ENTRY and SUBENT
lines in re-transmission(also optional for all
corrected lines in col.
80)”.
(Standing Action)
Inform each other about
EXFOR-related software
being used and/ordeveloped.

EXFOR Formats - Manual
Chapter 7 – REFERENCE - Typeof Reference = P or R or S:
Progress Reports / Reports /Conference Reports. (as afootnote)“When coming across report codes
in Dictionary 6, which differ
significantly from what is shown on
the report cover, submit anexplanation by a memo for inclusion
to the dictionary.”
Short Guide for EXFOR
compilers“Use CHEX code in TRANS modeto detect format and coding errors.”

Network Document Unique responsibilities within theNetwork (NDS):“Assessment of the need forundertaking both trivial and nontrivial compilation corrections, andnotification to responsible Centres.”
EXFOR Formats - Manual
Chapter 8:“Alteration flags in retransmitted
entries/subentries must be given on
the entry/subentry level, i.e. in col.
11 of the ENTRY and SUBENT
records.”(Similar sentence has been in thischapter.)
NRDC Protocol - EXFOR
Processing and Retrieval Codes:“The originating Centre will inform
other Centres about codes being
used or developed, and also
coordinate all programs updates.”(which substitutes the current
sentence:“The originating Centre will
coordinate all program updates.”)

10 A58

All(Standing Action)
Provide feedback on thedigitizing software
GSYS to JCPRG.

11 A59

All(Standing Action)
Provide feedback toNDS on the existing
CHEX version (on bugs
as well as desiredadditions)

12 A60Sarov

13 A62

All(Continuing Action)
Continue development
and testing of the
EXFOR-Editor incooperation with NDS
and other data Centres,
taking into accountcompilers’ remarks.
(Continuing Action)
Provide feedback on theJANIS-TRANS Checker
code to NEA DB.

Network Document Unique responsibilities within theNetwork (JCPRG):“Development, maintenance anddistribution of the Japanesedigitizing code (GSYS).”
Network Document Unique responsibilities within theNetwork (NDS):“Development, maintenance anddistribution of the EXFOR
exchange file checking code(ZCHEX).”.
Network Document Activities within Network.
“Development, maintenance anddistribution of the Russian EXFOR
input system (EXFOR-Editor).”
CNPD agrees.

Network Document Unique responsibilities within theNetwork (NEA DB):
“Development, maintenance anddistribution of the JANIS-TRANS
Checker code for EXFOR exchange
file checking.”

Journal Scanning Responsibility (WP2010-14, addition to NRDC Protocol)
NDS will assign areas of responsibility for journal scanning. Each centre will report
the list of publications containing data belong to the category A regularly. The
currently assigned scanning responsibilities are given in Appendix B of this Protocol.
Appendix B : Scanning Responsibility
Centre
NNDC
NEA-DB
NDS
CJD
CAJaD
CDFE
CNDC
JCPRG
JAEA
ATOMKI

Responsibility
PR/C, PRL, NSE
ANE, RCA
ARI, CNP, NP/A, PL/B, NIM/A, NIM/B
YK
YF, EPJ/A
CST, PHE, HFH, NTC, CPL, CNDP,
CNST, ASI, CPH
JPJ, PTP, NST, JNRSJAEA-C
AHP, JRN, JRN/LUkrNDC
CNPD
BARC
KAERI

UFZ, VAT/I
IPADistribution:
blokhin@ippe.ru
cgc@ciae.ac.cn
chiba@earth.sgu.ac.jp
claes.nordborg@oecd.org
emmeric.dupont@oecd.org
ganesan@barc.gov.in
gezg@ciae.ac.cn
hongwei@ciae.ac.cn
jhchang@kaeri.re.kr
j.roberts@iaea.org
kaltchenko@kinr.kiev.ua
katakura.junichi@jaea.go.jp
kato@nucl.sci.hokudai.ac.jp
kiralyb@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.at
pronyaev@ippe.ru
r.forrest@iaea.org
samaev@obninsk.ru
s.babykina@polyn.kiae.su
scyang@kaeri.re.krs.dunaeva@iaea.org
s.simakov@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
zhuangyx@ciae.ac.cn