Nuclear Data Section
International Atomic Energy Agency
P.O.Box 100, A-1400 Vienna, Austria

Memo CP-D/463

Date:
To:
From:

11 May 2006
Distribution
O. Schwerer

Subject:

Checking and corrections of some report codes and old EXFOR entries

Reference:

Actions A6, A7, A16, A17 of last NRDC meeting

1. Report codes (Dictionary 6) - Actions A6, A7
Some report codes occurring in the files but not in the dictionary need to be confirmed by theresponsible neutron data centres so that necessary corrections in the EXFOR/CINDA reportdictionary 6 can be introduced. Actions A6 and A7 were reminders to memo CP-D/347 = WP
2003-8 because several of these questions are still open.
On the following pages I reproduce WP 2003-8 (with the parts relevant for this exercise inbigger font) with comments about the required actions added. (Sections 1 through 3 of WP
2003-8 are not affected by this exercise and are reproduced in small font.) This is to assist
NNDC, NEA-DB and CJD to fulfill these two actions from the NRDC meeting. Simple
corrections of the report coding in CINDA (Section 7 of WP 2003-8) will be done centrally byNDS.

2. Some pending EXFOR retransmissions - Actions A16, A17
Action A16 was a reminder to retransmit some EXFOR entries mentioned on a list distributed
by V. McLane at the 2001 NRDC meeting, and Action A17 was on NDS to redistribute this list.
However, after checking all electronic and paper files, we found that we have only the list ofretransmissions requested from NDS. It is likely that a general list containing theretransmission requests from all centres was never distributed, but only individual lists in asingle paper copy to each responsible centre (as had been done at earlier meetings). Therefore
we can only ask all centres to check whether their individual list still exists and to make all
pending corrections requested therein.

Distribution:
oblozinsky@bnl.gov
vml@bnl.gov
drochman@bnl.gov
nordborg@nea.fr
manokhin@ippe.obninsk.ru
samaev@obninsk.ru
mmarina@ippe.ru
blokhin@ippe.obninsk.ru
feliks@polyn.kiae.su
chukreev@polyn.kiae.su
S.Dunaeva@iaea.org
taova@expd.vniief.ru
varlamov@depni.sinp.msu.ru
chiba@earth.sgu.ac.jp
kato@nucl.sci.hokudai.ac.jp
ohnishi@nucl.sci.hokudai.ac.jp
ohbayasi@meme.hokudai.ac.jp
yxzhuang@iris.ciae.ac.cn

gezg@iris.ciae.ac.cn
hongwei@iris.ciae.ac.cn
tarkanyi@atomki.hu
stakacs@atomki.hu
katakura.junichi@jaea.go.jp
vlasov@kinr.kiev.ua
kaltchenko@kinr.kiev.ua
ogritzay@kinr.kiev.ua
nklimova@kinr.kiev.ua
yolee@kaeri.re.kr
jhchang@kaeri.re.kr
ohtsuka@nucl.sci.hokudai.ac.jp
A.Mengoni@iaea.org
m.wirtz@iaea.org
schwerer@iaeand.iaea.org
v.zerkin@iaea.org
henriksson@nea.fr
exfor@nea.fr

(WP 2003-8)(Memo CP-D/347)
Date:
To:
From:
Subject:

15 November 2002
Distribution
M. Lammer
Report codes

During his conversion of the old CINDA file into the new CINDA 2001 format, Viktor Zerkinhas produced a list of all reference codes found in CINDA and compared them to the EXFOR
dictionaries. I have looked into all those report codes, which had no corresponding EXFOR
codes. The results are presented here.
1) Restriction of code length in CINDA 2001
An addition to Memo CP-D/246: the need to insert a blank before the report number if the code is shorter than 4characters, can be dropped (obviously also blanks required for journal codes before the volume number). Also,
longer codes can be accepted (cf. item (7) below: “…. simple corrections”).
2) Proposal for presentation of code in EXFOR Dictionary 6
As a requirement of coding rules, some of the codes in EXFOR dictionary 6 are so different from the codes
printed on the cover of reports, that I propose to add in all such cases (not just a few like CEC- or INR-) theactual code on the cover in the text of the expansion or somewhere thereafter. This should avoid a number ofcoding errors (see part on coding errors in (6) and (7) below) by compilers or related problems. Example:
EXFOR: PNR/SETR-R-25
code on cover:
PNR/SETR
on 2 lines
R.0253) New codes (confirmed) for inclusion in EXFOR Dictionary 6
The “confirmed” codes, I have either found on actual reports or in INIS (in a retrieval or the book IAEA-INIS-6:
the INIS authority list for “report number prefixes”).
AES-2SWDAEAktiebolaget Atomenergi, Studsvik, reports

BNWL-TR-(same expansion as BNWL-)

CEA-CONF-

2FR FR

Commissariat a L’Energie Atomique (NOTE: not confined to a lab,includes publications by BRC,CEL,CAD,GRE,SAC,…)

GSI-J-2GERGSI(same expansion as GSI-)KAERI/GP-

3KORKAE

Korean Atomic Research Institute reports

JINR-D6JINR-E4JINR-P12JINR-P14(same as other JINR- reports)

OKTAV-C-

2JPNOSA(same expansion as OKTAV-A-) Note: why not use full name
OKTAVIAN-? (see comment (1) above)

PNR/SETR-

2FR CAD(same expansion as PNR/SETR-R-) code on report cover e.g.: PNR/SETR
65.010, to be coded as PNR/SETR-65-10;

RD/B/N-

2UK CEG(same expansion as RD/B/M-)

TIB/FICS-

2ITYITY

ENEA Dipmt. Tecnologie Intersettorali di Base/Div. FIsica e Calcolo
Scientifico reports; code on cover: TIB/FICS (83) 4(“ENEA” expanded: Comitato Nazionale Ricerca e Sviluppo Energia
Nucleare e Energia Alternativa)

4) New codes (unconfirmed) for possible inclusion in EXFOR Dictionary 6!! Note to NNDC and NEA-DB: This section is on reports from areas 1 and 2.
Please confirm the codes and/or their origin, for addition to dictionary 6.
These codes, found in CINDA, I could not confirm via the sources mentioned above. They
will have to be checked and confirmed by the responsible center, as well as the proposedlabcode and expansion, which are only my assumptions.
AD-A-

1USADOD origin: 1 entry in CINDA coded as AD-A009563, with
lab=4CCPLEB, comment indicates translation from book
LEB; INIS-6: “Defense Documentation Center, Alexandria,VA, USA, (assigned to unclassified documents …)”.

AE-RFT-

2SWDAEAERE-NP/PR-

2 entries, both with lab 2UK ALD; code not found anywhere; could be
miss-spelt, or confused with AERE- PR/NP- or AERE-NP/R-: to be checked.

ANL-AJD-

1USAANL probably same as ANL-

FOA4-D-

2SWDFOA probably same as FOA4-A- and FOA4-C-

GA-B-?1USAGA suggests same as GA- (GA-A- and GA-C- found in INIS-6, butnot GA-B-), but lab in CINDA entry is 1CANCRC???

MON-C-

1USAUSA probably expansion as MON-N-;

UNC-PH/M-

1USAUNC found (libraries, INIS-6) only code UNC-, probably same.

(all entries have lab=2SWDAE, probably expansion as AE-)

5) Proposed or possible corrections for EXFOR Dictionary 6!! See remarks below
AFWL-TDR-

does not occur in CINDA nor in EXFOR, but several entries in both withcode AFWL-TR-; neither code could be confirmed; to be checked by
NNDC (see EXFOR# 10022 and 12069).

!! Propose to add AFWL-TR- instead, unless NNDC says otherwise
AWRE-CNR/PR change to AWRE-CNR/PR- (add dash at end of code);!!Done
CEA-, CEA-N-, CEA-R-: according to INIS-6, published by different CEA labs (as item (3)above: CEA-CONF-) => propose to change lab to 2FR FR (or introduce
code for CEA).
!! Propose to change lab to 2FR FR unless NEA-DB says otherwise
IPNO-THchange to IPNO-TH- (add dash at end of code);!!DoneNIIAR-P1-needs clarification (see also item (6) below): entry EXFOR40469 contains
NIIAR-P1-335, the corresponding CINDA entry contains NIIAR-P-335(possibly because of limited space); INIS sources contain only NIIAR-P-;

conclusion: NIIAR may have part -P1,-P2, etc. similar to JINR-, which
may have been partially omitted; has to be checked and clarified by CJD.
!! CJD is asked to check what NIIAR- reports are needed in dictionary 6. At
present, we have NIIAR- and NIIAR-P1- but not NIIAR-P-. Remember that for thedictionary, the first hyphen followed by a digit or an opening parenthesis, is theseparator between the "code field" and the "number field" and therefore
determines which codes must be entered in the dictionary.

6) Obvious coding errors in CINDA
Several more such errors I could correct easily without checking the original reference.
EANDC(U)76U175

CINDA entry for Mo-97 RES, lab=2FR SAC: check and correct;!!DoneINDC(EUR)14374

this number does not exist (several entries);!!Was changed to INDC(EUR)-14374 but this is still nonexisting number. NEADB to check and correct (Lab = 2ZZZGEL, REACTION = Cr53(n,g)
NEANDC(E)-GE/R

CINDA entry for U-238 TOT 2ZZZGEL: check and correct;!! NEA-DB to check and correct
NIIAR-

several ways of coding that are inconsistent and partially do notconform with coding rules; some have to be corrected:
NIIAR-P-335
NIIAR-P22(356)
NIIAR-1(360)
NIIAR-2(361)
NIIAR-P-5,
NIIAR-52

The different ways of coding NIIAR- reports support my proposal to include in the EXFOR
dictionary, in some doubtful cases, the codes printed on the report cover.
!! See item 5 above (CJD to check NIIAR report subseries)7) Coding errors in CINDA requiring simple corrections!! The corrections listed in the following table will be done centrally at NDS.
The following coding errors can easily be identified and corrected by a small computer
program. In particular could corrections be implemented during conversion to CINDA 2001,
also because for some of the errors, the correct coding would exceed the field length foreseenin the old system, and hence cannot be corrected there. In most cases listed below, “no”
stands for report number and “yy” for year.
wrong coding

correct coding

comment

AAEC/AP-PR1986
AAEC/AP/PR-1986 correct coding exceeds field length;
AAECAP-PR-1986
total of 7 entries!! AAEC/APPR-1986 (3AULAUA) occurs in several (N,F) entries. To be correctedAERE-PR/NPno

AERE-PR/NP-no675 wrong entries (only 1 correct)!! To be corrected (2UK HAR)
AWRE-CNRPR/10

AWRE-CNR/PR-10

correct coding exceeds field length; 58 wrongentries!! To be corrected (2UK ALD). Code length is no problem now
CEC(yy)-noCEC-(yy)-no266 wrong entries; code on report: CEC(yy)no!! To be corrected (2ITYBOL)EANDC(E)noEANDC(E)-noover 1500 wrong entries!! Seems okay now; but in some cases no separator before page number
EANDC(J)22

EANDC(J)-22

5 wrong entries

EANDC(OR)-no85 wrong entries!! Seems okay now
EANDC(OR)no!! Seems okay now; but in some cases no separator before page number
EANDC(UK)151

EANDC(UK)-151

3 wrong entries!! Seems okay now
EANDC(UK) 151

73 wrong entries!! Seems okay now
FOA4-Ano

FOA4-A-no!! To be corrected (2SWDFOA)
FOA4-Cno
FOA4-C-no

total of 22 wrong entries
code on report (example): FOA 4 Rapport!! To be corrected (2SWDFOA)
FOA4-Dno

FOA4-D-no(printed on 2 lines)

A 4410-411!!

To be corrected (2SWDFOA). FOA-4-D- to be added to dict.6
HEDL-TMEyy-no

HEDL-TME-yy-no

5 entries; on report: HEDL-TME yy-no

To be corrected (1USAHED)
INDC(EUR)noINDC(EUR)-no264 wrong entries!! Seems okay now
JAERI- no
JAERI-no
JAERI-C- no
JAERI-C-no
JAERI-D- no
JAERI-D-no
JAERI-M- no
JAERI-M-no
JAERI-R- no
JAERI-R-no!! All JAERI- entries seem okay now

total of 357 wrong entries

JUELSPEZ-no

5 wrong entries

JUEL-SPEZ-noTo be corrected (2GERJUL and 2FR ILL); 2 wrong entries remaining

NAA-SR-TDRno

NAA-SR-TDR-no

24 wrong entries

NEANDC(E)-no18 wrong entries

NEANDC(J)-no24 wrong entries!! Seems okay now
NEANDC(E)no!! Seems okay now
NEANDC(J)no!! Seems okay now
NEANDC-J-no
NEANDC(J)-no
NEANDC-Jno!! Both to be corrected

total of 69 wrong entries

NEANDC(UK) no

NEANDC(UK)-no4 wrong entries

PNR/SETR-yy-no

24 wrong entries; code on report: see (3);!! Seems okay now
PNR/SETRyy-no!! To be corrected (2FR CAD). Code length is no problem now
UKNDC(75)P71

UKNDC-(75)P71!! To be corrected to UKNDC-(75)-P71

or UKNDC-(75)-P71, or? code on report:
UKNDC (75) P71