NEA Data Bank
Le Seine St-Germain
12, boulevard des Iles
92130 Issy-les-Moulineaux
FRANCE
Email: exfor@nea.fr
or cinda@nea.fr

Tel: +33 (0) 1 45 24 10 84
Fax: +33 (0) 1 45 24 11 28

MEMO CP-N/40
DATE:
TO:
FROM:
SUBJECT:

18 Nov 2005
See distribution list below
H. Henriksson
New CINDA manual distribution

I would like to distribute the CINDA manual for the new exchange format, according to theconclusions of the last NRDC meeting.
If you have comments to the manual please inform the network as soon as possible. This format
stated below is to be used from now on when transmitting CINDA data.
I suppose, this will also mean an end to the ‘moratorium’ of CINDA batches that was decided in2003 as I understand it.
Best regards,
Hans Henriksson
Distribution:s.takacs@atomki.hu
tarkanyi@atomki.hu
chiba@earth.sgu.ac.jp
kato@nucl.sci.hokudai.ac.jp
ohbayasi@meme.hokudai.ac.jp
ohnishi@nucl.sci.hokudai.ac.jp
ohtsuka@nucl.sci.hokudai.ac.jp
hongwei@iris.ciae.ac.cn
gezg@iris.ciae.ac.cn
yxzhuang@iris.ciae.ac.cn
chukreev@polyn.kiae.su
blokhin@ippe.obninsk.ru
feliks@polyn.kiae.su
samaev@obninsk.ru

manokhin@ippe.obninsk.ru
mmarina@ippe.obninsk.ru
taova@expd.vniief.ru
varlamov@depni.sinp.msu.ru
ogritzay@kinr.kiev.ua
kaltchenko@kinr.kiev.ua
oblozinsky@bnl.gov
drochman@bnl.gov
S.Dunaeva@iaea.org
a.l.nichols@iaea.org
schwerer@iaeand.iaea.or.at
v.zerkin@iaea.org
henriksson@nea.fr
claes.nordborg@oecd.org

CINDA 2001 Manual

CINDA2001
MANUAL
Prepared by Victoria McLane
National Nuclear Data Center
Preliminary Version
June 2000
Updated by Mark A. Kellett, January 2004
based on June 2003 NRDC meeting decisions.
Revision 3, December 2004
to correct HIERARCHY and REFERENCE codes.
Revision 4, May 2005
changes in the CINDA format hierarchy code, and corrections given in Vienna,
2005.
Revision 5, November 2005
Modifications in the format agreed on
the NRDC meeting, Vienna, 2005.

2

CINDA 2001 Manual

CINDA Bibliographic System
HISTORY
CINDA2001 was designed to replace the CINDA database which was originally designed in
19581 as a Card Index to Neutron Data. CINDA was adopted in the 1970's by the four
Neutron Data Centers as an international index to the neutron data; the compilation scheme
remained essentially unchanged until 1998.
In the meantime, the Nuclear Reaction Data Network had evolved from the original four centers to a group of thirteen centers involved in
the compilation of nuclear reaction data for incident charged particles and photons, in addition to neutrons. The need for an index thatwould allow the inclusion of all reaction data, and the need to update the format for the year 2000 lead to a complete redesign of thebibliographic system.

The new system is more compatible with EXFOR/CSISRS2, and has adopted many of thesame the codes used in this database, thereby eliminating the need for users of nuclear
reaction data to learn different sets of notation when accessing the bibliographic and data files.
INTRODUCTIONCINDA2001 is a computerized bibliographic file containing references to information on
nuclear reactions. Included are references to measurements, calculations, evaluations, andreviews of nuclear reaction and other related data. In the case of experimental or evaluateddata, references to the databases where the actual values may be obtained are also included.
Identical copies of this database are maintained by the four core centers in the Nuclear Data
Center Network. 3 These master files are updated periodically and exchanged among thecenters. Retrievals from CINDA2001, as well as the experimental and evaluated databases,
are available through the Internet using World Wide Web or by direct access using TCP/IP’s
4
TELNET command.

1

CINDA was designed by Herbert Goldstein, a professor in the Department Of Applied Physics andEngineering at Columbia University, see Nuclear Development Corporation of America report NDA 2-80
(1958).
2

For a description, see the "EXFOR exchange Formats Manual", V. McLane, IAEA-NDS-207 (2004)
These core centers are: the US National Nuclear Data Center, the NEA Data Bank, the IAEA Nuclear Data
Section, and the Russian Nuclear Data Center at Obninsk. See Appendix A for complete information on the
Nuclear Reaction Data Centers.
4
See Appendix A for access to your nearest data center.
3

3

CINDA 2001 Manual

The information in the CINDA2001 Database is obtained from scanning the available
literature, both published and unpublished. Coverage is “complete” for neutron data from1935 to the present. Coverage for charged-particle data is nearly complete from 1980 to thepresent, and less complete before 1980. Coverage for photon-induced data is taken from
Photonuclear Data5 which covers the period 1976 to the present.
This manual is intended to be a complete guide to the indexing of information in the
CINDA2001 system.

CINDA2001 EXCHANGE FORMATThe CINDA2001 exchange file consists of a series of records plus a header record, which
gives information about the attached file. The format of the header record is:Columns
Content
1-5 ID
6 (blank)
7-15 Type of file16-22 Exchange number
23-33

Date of exchange

34-44

Number of records on file

Use
CINDA
READER or EXCHANGE; left-adjusted
Area code, number of exchange for area; rightadjusted.
8-digit right-adjusted integer: year, month, day(YYYYMMDD)
Right-adjusted integer

Files transmitted will be either exchange files or reader files. The format of these files is thesame, but the content will differ slightly; the differences are noted under the sections on theappropriate fields.
Exchange files consist of records produced for transmitting entries from a center’s own areaof responsibility.
Reader files contain records produced by the transmitting center for an area outside its
responsibility and transmitted to the responsible center for addition to its database. After the
update of its database, the records will be transmitted by the responsible center to all othercenters.
Empty lines may be inserted in both types of CINDA files, as well as comment lines for thecompiler or for the loading of the CINDA data base. The comment lines should start with thesymbol '#'.

5

V. V. Varlamov, V. V. Sapuchenko, M. E. Stepanov, Photonuclear Data 1976-1995, Photonuclear
Experimental Data Center, Moscow University (1996).
4

CINDA 2001 Manual

The fields given in the CINDA2001 exchange format are as follows.

Columns
1
2-8
9-23
24-27
28-34
35-39
40-43
44
45
46-47
48-61
62-90

Contents
Operation code
Z,A
Reaction
Quantity
Laboratory
Block #
Sequence #Hierarchy code
Work type
Reader code
Energy range
Reference anddate

Formats
A1
I3,I3*, A1
A15
A4
A7
A1,I4
I4
I1
A1
A2
2(E7.1)*
A23,I6

91-128129-136

Comment
Modification
date
Old CINDA
quantity
Lab or product
code

A38
I8

137-139140-395

A3
StringExampleAs in CINDA
Target Z, A, isomeric state: (ZZZAAAM)
Generally, EXFOR REACTION SF2-SF3
From DANIEL Dictionary 13.
EXFOR code with area code
Area code, followed by center assigned block #Sequence within block
Hierarchy for references (0-6)
As in CINDA6
At discretion of center (blanks allowed)7
Min + max in format: +n.n+ee
Type: as in CINDA (A1),
Reference code: as in EXFOR (A22),
Date: year and month (YYYYMM)
As in CINDA
Date of compilation/loading: year/month/day(YYYYMMDD)(Not compulsory) Quantity code as stated in the
old CINDA format
Possibility to add multiple labs or products, e.g.
;LAB=2ZZZGEL,1USABNL;PROD=12-C-14* The fields for Atomic mass, A, and Energy range can contain character codes, see below.

Updates to the formats must be agreed upon by the four core centers.
Any codes to be used in CINDA2001 are included in dictionaries contained in the DANIEL
dictionary database. Updates to the dictionaries must be submitted before any code not givenin these dictionaries may be used on a CINDA2001 exchange file.
Details for the coding and content of each of the above fields are given on the following
pages.

6

With the exception that the mixed mode codes will be eliminated. For example, entries for theoretical
calculations will be separated from experimental data.

7

That is, centers may choose not to use a reader code.
5

CINDA 2001 Manual

OPERATION CODE (Column 1)
The operation code is a signal to the database update code as to what operation must be
performed. The following list contains the legal operation code and their use.

CodeA

Meaning
Add record

D

Delete record

M

Modify record

Exchange Use
Block number and sequencenumber must be specified
Block number and sequencenumber must be specified
Block number and sequencenumber must be specified

Reader Use
Block number may be specified;sequence number must be blank.
Block number and sequencenumber must be specified.
Block number and sequencenumber must be specified

The remainder of the record must be complete for both reader and exchange format.

TARGET NUCLEUS (Columns 2-8)
The target nucleus is given as 2 three-digit integers (Z and A), both right-adjusted in theirfield, plus an isomeric state code. All legal Z, A codes are found in DANIEL Dictionary 227.
The isomeric state code is blank for a nucleus in the ground state, and consists of themetastable state number for metastable states (e.g. 1, 2… and not M as stated in the
dictionary).
For compound nucleus properties, e.g., resonance parameters, the nucleus entered is thetarget for the reaction(s) analyzed.
For a theoretical work giving systematic trends over many nuclei, the code MNY may be usedin the A field; use Z equal to zero. The code MNY may be used either in place of, or in
addition to, separate entries for the individual nuclei.
Naturally occurring elements
For naturally occurring elements that contain a mixture of isotopes, a zero is entered in the Anumber field. For monoisotopic elements, the Z and A of the isotope are given. For nearlymonisotopic elements, i.e., for elements where the principal isotope is more than 99% of thenatural isotopic mixture, the Z,A of that isotope may be given if the contribution from otherisotopes to the reaction given is negligible.

6

CINDA 2001 Manual

Compounds and Mixtures
For compounds and mixtures, a 3-character compound code is given instead of the A number
and is left adjusted in the field. Single element compounds, e.g., molecular hydrogen, should
not be coded as compounds. If information is deduced for a constituent element of acompound or mixture, it should be entered under that element.
The general code zzzCMP, where zzz is the major component of the compound, may be used
if the compound is not given specifically in the dictionary. The name of the compoundshould be given in the comment. If more than one element may be considered a major
component, choose the element with the highest Z number.
For data given for mixed fission products, i.e., an aggregate of those fission products
produced in a given fission reaction, the code FPR is given in place of the A value; use Z
equal to zero.

REACTION (Columns 9-23)
The code for reaction is given as two fields: incident and outgoing. For complete evaluations
covering many reactions, and given over a defined energy range, this field may be left blank.
The incident field contains one of the following:
1. A particle code from DANIEL Dictionary 33 which contains a non-blank character in thethird position of the Allowed Subfield field, e.g., P or HE3.
2.

A chemical symbol and A-number (SS-AAAM) from DANIEL Dictionary 227; for anucleus in a metastable state the code is followed by an M, e.g., CL- 35 or AM-242M.

The outgoing field contains one of the following.
1.

A particle code from DANIEL Dictionary 33 which contains a non-blank character in the
fourth position of the Allowed Subfield field, e.g., P or HE3.

2.

A nuclide code, i.e., chemical symbol and A-number (SS-AAA) taken from DANIEL
Dictionary 227; for a nuclide in the metastable state the code is followed by the code M,e.g., CL- 35 or AM-242M;

3.

A process code taken from DANIEL Dictionary 30, e.g., TOT or EL;

4.

A combination of the above with the codes separated by a “+”.
The order of codes is: particles ordered from lightest to heaviest,8 followed by nuclide
codes ordered from lightest to heaviest, followed by process codes in alphabetical order.
The exception to this rule is: when the order in which the reaction proceeds is given
explicitly, the codes are given in that order.

8

Lightest to heaviest is defined as in order of lightest Z, then in order of A.
7

CINDA 2001 Manual5.

For complex reactions with many outgoing particles, the code CMPLX may be used in thisfield in place of all other codes.

QUANTITY (Columns 24-27)
The legal quantity codes are given in DANIEL Dictionary 45 (partly from the old dictionary13). These codes are listed in Appendix D. For complete evaluations, covering many
reactions and quantities, this field contains the code EVL. A Quantity code with a ‘$’ sign infront means that the code was inserted automatically by converting EXFOR entries to
CINDA, but without correspondence in Dictionary 236 and/or in dictionary 45.

INSTITUTE (Columns 28-34)
The institute is given as a single integer for the area code followed by the six-character code
consisting of a country code followed by an institute code. These codes are found in
DANIEL Dictionary 3, CINDA Code field.
If more than one institute is involved in the work, the main institute is given. The main
institute is defined as the institute at which the principal investigator resides, or the institute at
which the work was done. Links to the other institutes are given on Institute Cross Reference
Records (work type 9, see Work Type). An entry is made for each institute containing atleast one reference.

BLOCK NUMBER (Columns 35-39)
The block number consists of the area code for the responsible center, followed by a four
digit block number, e.g., L1982. The area codes to be used are those assigned for EXFOR, e.g.
area 1 is USA and Canada, area 2 is OECD member countries (excluding USA and Canada)etc. No area code is allowed (e.g. for old CINDA records, where block number was alreadyassigned).
The block number is assigned only by the center responsible for the entry. Before blocking
CINDA lines together, compilers must be fully certain that the lines do belong with eachother. The blocks are based on the same isotope (Z, A, and state), reaction, lab andexperiment, based on for example the same people involved in the presented work in thearticles during a limited time period.

SEQUENCE NUMBER (Columns 40-43)
The Sequence Number is a 4-digit, right-adjusted integer denoting the sequence within a
block. It is assigned only by the center responsible for the entry.

HIERARCHY CODE (Column 44)
8

CINDA 2001 Manual

The one-digit Hierarchy code is used to distinguish between different types of records, or todenote the importance of a reference. Valid hierarchy codes are defined in the following
table.
Code
1
2
3
4
5
6
0

1.

Use
Main publication. Assigned only to a publication known to be the definitive
publication.
Published reference (journal or conference proceeding).
Other major reference, such as, complete laboratory report or a thesis.
Translation for reference with hierarchy 1-3.
Minor reference, such as, a progress report, a meeting abstract, or a private
communication.
EXFOR or Evaluated Data index entry. A reference to an entry in a datalibrary which gives the numerical data referenced in the block.
EXFOR data index line where accession number is not yet assigned, i.e.
EXFOR compilation of the work is still in progress.

Hierarchy codes 0 and/or 6 for EXFOR data:
Column 43
0 or 6
Columns 60-66 4,EXFOR
Columns 67-71 EXFOR Accession number (e.g. 11754)
or 00000, if unassigned, when hierarchy code = 0
Column 72
full stop (.)
Column 73-75 EXFOR Sub-accession number, e.g. 002, 045, etc.
or 000, if unassigned, when hierarchy code = 0

WORK TYPE (Column 45)
The one-character Work Type code gives the type of work referenced, e.g., experimental,
evaluated. For a reference containing more than one type of work, a separate block should beentered for each type, for example, an experimental work in which extensive 9 model
calculations were done.

READER CODE (Column 46-47)
A two-character Reader Code may be used, at the discretion of the entering center, to identify
the compiler of the entry. This field may be left blank. A list of current and formerly used
Reader Codes is given in Appendix B.
ENERGY RANGE (Columns 48-61)
9By extensive is meant that each work is extensive enough to warrant publication on its own. For example, acomparison of measured angular distributions with optical model calculations is not regarded as fulfilling thiscriterion. This comparison should be noted in the comment for the experimental data.
9

CINDA 2001 Manual

The energy range field consists of two floating-point numbers (2E7.1) which give theminimum and maximum energies for the data referenced. If the data is presented only at one
energy, it is given in the first field; the second field is blank. If an upper limit only is known,
it is given in the second field; the first field is blank.
If only the approximate range is known, only the exponents are entered.
A four-character code is used to define the energy for spectrum-averaged values. A list of alllegal codes is given in Dictionary 48, e.g. MAXW, SPON, THR (see also old CINDA
Readers manual, Part II.9). If the reference covers two or more distinct energy ranges that
may be viewed as separate experiments or calculations, separate entries should be made.
Example: a measurement at thermal energy of Maxwellian-averaged cross section and aseparate measurement over the energy range 5 eV to 6 keV.
If no information on the energy is given, the code NDG (no data given) is used.
For quantities for which an incident energy is meaningless, i.e., nuclear quantities,
spontaneous fission and so on, both fields are left blank.

REFERENCE (Columns 62-90)
The reference consists of three fields: reference type, reference code, and reference date. The
format of the reference field depends on the reference type.
Reference Type (Column 62)
The Reference Type consists of a one-character code which is:either taken from DANIEL Dictionary 4,
or 4 for EXFOR data,or 3 for Evaluated data libraries.
If Reference Type and Reference Code are present, column 61 should contain a comma (,).
Reference Code (Columns 64-84)
In general, references are coded as for EXFOR and use the same dictionaries and codes. See
the EXFOR Manual for coding rules, and Dictionaries 5-7, 207 for document codes.
1. Reference Code for EXFOR data:
columns 64-68 EXFOR
columns 69-73 EXFOR Accession number (e.g. 11754)
or 00000, if unassigned, when hierarchy code = 0
column 74
full stop (.)
column 75-77
EXFOR Sub-accession number
or 000, if unassigned, when hierarchy code = 0
10

CINDA 2001 Manuale.g. 4,EXFOR12345.123 (for hierarchy code = 6) or 4,EXFOR00000.000 (forhierarchy code = 0).
2.

Reference Code for Evaluated data libraries:
columns 64-69 evaluated file name (see DANIEL Dictionary 44)
columns 70-84 version number, data set or material number,e.g. 3,JENDL-3.2 4725 where in this example 4725 is the material number ofthe coded target 47-AG-107.

Reference Date (Columns 85-90)
The reference date is given as a 6-digit integer: 4-digit year, 2 digit month (YYYYMM). If themonth is not known, it may be omitted. (Note that for conference proceedings the date of theconference is entered and not the date of issue of the proceedings.)

COMMENTS (Columns 91-128)
Comments for reference records should start with the first author’s last name, terminated witha full stop (.) for a single author or a plus sign (+) for multiple authors. If no author is known,
column 87 should contain a full stop.
The author’s name is followed by additional, abbreviated information about the work.
The comment should contain information on whether and how the data is presented in thereference as in the previous CINDA.
Examples: NDG (no data given)
GRPH (graphs)
TBL (table)
For allowable character set and translation of Cyrillic characters, see EXFOR Manual,
Chapter 1.
Comments for the data index lines should contain:
for EXFOR, the number of data lines, and type of data;
for evaluations, the evaluator.

11

CINDA 2001 Manual

MODIFICATION DATE (Columns 129-136)
The modification date is assigned by the compiler as the date of compilation. This may be
updated by the compiling center as the date at which the entry is entered into the database.
The modification date is given as an 8-digit integer: 4-digit year, 2 digit month, 2 digit day(YYYYMMDD).
Old CINDA quantity (Columns 137-139)
The quantity used in the old CINDA format can be stated here. This may be used to searchfor old CINDA lines where the new reaction string is missing.
The quantity is given as 3 characters (QQQ).
Additional information (Columns 140-395 (255 characters as max length))
This space is reserved for multiple labs and products.
Possibility to add multiple labs or products, e.g.
;LAB=2ZZZGEL,1USABNL;PROD=12-C-13/14,27-CO-55/56
Additional keywords for other information can be added after approval of NRDC.

12

CINDA 2001 Manual

Appendix A
Nuclear Reaction Data Centers
This appendix contains a list of the members of the Nuclear Data Center Network, along withinformation on how to contact them. Also list are the entry series for which each of the data centers is
responsible.

Principal Centers and their services areas.10
United States and Canada
Center codes: 1, C, L, P, T
Telephone: +1 631-344-2902
Fax: +1 631-344-2806
Email: nndc@bnl.gov
or nndcnn@bnl.gov11
www.nndc.bnl.gov

National Nuclear Data Center,
Bldg. 197D
Brookhaven National Laboratory
Upton, NY, 11973-5000 U.S.A.

O. E. C. D. Nuclear Energy Agency Member Countries
Center codes: 2, O
NEA Data Bank
Telephone: +33 (1) 4524 1084
12, boulevard des Iles
Fax: +33 (1) 4524 1128
92130 Issy-les-Moulineaux,
Email:nea@nea.fr
FRANCEor name@nea.fr
www.nea.fr
Countries of the former Soviet Union
Center codes: 4, Q
Telephone: +7 084-399-8982
Fax: +7 095-883-3112
Email: name@ippe.obninsk.ru
rndc.ippe.obninsk.ru

Federal Research Center IPPE
Centr Yadernykh Dannykh
Ploschad Bondarenko
249 020 Obninsk, Kaluga Region,
RUSSIA
Remaining countries

Center codes: 3, D, G, V.
Telephone: +43 (1) 2360 1709
Fax: +43 (1) 234 564
Email: name@iaeand.iaea.or.at
www-nds.iaea.or.at

IAEA Nuclear Data Section
Wagramerstr. 5, P.O.Box 100
A-1400 Vienna, AUSTRIA

10 The four principal centers are responsible for maintaining customer services for the area given.
11 nn = first and last initial of person to be contacted, e.g., NNDCCD@BNL.GOV.
13

CINDA 2001 Manual

Other participating centers.
National Scientific Research Center
Kurchatov InstituteRussia Nuclear Center
46 Ulitsa Kurchatova
123 182 Moscow, RUSSIA
Institute of Nuclear Physics
Moskovskiy Gos. Universitet
Vorob'evy Gory
119 899 Moscow, RUSSIA
China Nuclear Data Center
China Institute of Atomic Energy
P.O. BOX 275 (41)
Beijing 102413, CHINA
Japan Charged Particle Nuclear Reaction DataGroup
Division of Physics
Hokkaido University
Kita-10 Nisha-8, Kita-ku
Sapporo 060-0810, JAPANDr. F. T. Tárkányi
Cyclotron Application Department
ATOMKI, Institute of Nuclear Research
Bem Tér 18/c, P. O. Box 51
H-4001 Debrecen, HUNGARY
Russian Federal Center - VNIIEF
Sarov, Nizhni Novgorod Region
607 190 pr. Mira 37, RUSSIA

14

Center codes: A, B
Email: Chukreev@cajad.kiae.su
Feliks@polyn.kiae.su

Center code: M
Email: varlamov@cdfe.npi.msu.su

Center code: S
Email: cndc@mipsa.ciae.ac.cn

Center code: E, R
Email: kato@nucl.sci.hokudai.ac.jp
www.jcprg.org

Contributes data under center code D
Email: tarkanyi@atomki.hu

Center code: F
Email: dunaeva@expd.vniief.ru

CINDA 2001 Manual

Appendix B
CINDA Reader Codes
ReaderCountry

Code
0
2
3
4
5
6
7
8
9
B
E
F
L
N

O
S
W

Y
Z
(
+
$
&
?

IAEA Nuclear Data Section: corrections
NEA Data Bank
I.L. Nitteberg
A. Ventura
H. Bruneder
F. Hijerup
NEA Data BankNEA Data Bank
E. Ramstrom
F. Poortmans
C. BastianF. Wasastjerna
F. Manero
T. Nakagawa (JAERI, Tokai),T. Fukahori (JAERI, Tokai),S. Chiba (JAERI, Tokai),O. Iwamoto (JAERI, Tokai),
H. Kitazawa (National Defense Academy, Tokyo),
M. Kawai (KEK,Tsukuba),
T. Ohsaki (Tokyo Institute of Technology, Tokyo)
Russian Nuclear Center, Obninsk
K. Junker
M.F. James
J.S. Storey
M. Moxon
J. Frèhaut
H. Behrens
H.A.J. Van der Kamp
National Nuclear Data Center
IAEA Nuclear Data Section
Other than NNDCNEA Data Bank: automatic or semi-automatic generation of
entries

15

NorwayItaly
Austria
Denmark

SwedenBelgium
Euratom
Finland
Spain
Japan

RussiaSwitzerland
United Kingdom

FranceGermany
The Netherlands
U.S.A.
U.S.A.

tit
Ref -type

Seq. #

L b~BlockID(unique)

Hierarchy
Work -type
ReaderCINDA 2001 Manual
Example of the CINDA2001 Exchange format

Old

E-min
E-max
Date-ref
Reference
Reaction
Comment
Misc info: multiple labs, products...
Date-modI3 I3AA15
A3A6
A5 I4 IA
A7
A7
A
A23
I6
A38
A8
1-.-.-.-10.-.-.-.-20.-.-.-.-30.-.-.-.-40.-.-.-.-50.-.-.-.-60.-.-.-.-70.-.-.-.-80.-.-.-.-90.-.-.-.100.-.-.-.110.-.-.-.120.-.-.-.130.-.-.-.140.-.-.-.150
123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.123456789.12
A 0 1 N,TOT
CS 1USAPTN17730
13EC 7.0+08 3.6+09J,PR/D,8,136
197307Devlin+ MOM = 0.7-3.6 GEV/C.
19900117TOT
A 0 1 N,TOT
CS 1USAPTN17730
26EC 7.0+08 3.6+094,EXFOR10365.005
198304.26 PTS. SIGMA.
19900117TOT;LAB=1USABNL,1USALAS
A 0 1 N,TOT
CS 1USAPTN17730
36EC 7.0+08 3.6+094,EXFOR10365.004
198304.26 PTS. SIGMA. N-P + N-N.
19900117TOT;LAB=2FR ILL,2GERJUL,2GERKFKA 0 1 N,TOT
CS 1USALRL17000
15T+
6.0+07R,DOE-NDC-47,86
198804Brown+ NDG.
19900117TOT
A 0 1 N,EL
DA 1USAUI 17000
13T+ 5.0+07 2.0+08J,PR/C,36,2221
198712Schiavilla+ GRPHS.CORREL.BORN APPROX 19900117DEL
A 0 1 N,EL
DA 1USALRL17000
15T+
6.0+07R,DOE-NDC-47,86
198804Brown+ NDG.
19900117DEL
A 1 1 N,X
EVL 1USAYAL10010
13D8
1.0+07J,ARN,2,365
195300Breit+SCATT LENGTH- SEE PAGE 384
19900117EVL
A 1 1 N,X
EVL 1USAUNC10010
13DC 2.5-02 1.0+07R,NDA-57-27
195609Monroe+.TOT,ABS.TABLE+CURVE
19900117EVL
A 1 1 N,X
EVL 1USAGEN10010
13D8 3.2-02 1.0+07R,APEX-467
195806Tralli+.18GROUPS ABS
19900117EVL
A 1 1 N,X
EVL 1USAGEN10020
13D8 Maxw
R,APEX-467
195806Tralli+.ONLY 2.23 MEV LINE FOR SNG
19900117EVL
A 1 1 N,X
EVL 1USAPCT11500
13D+ 2.5-02 1.4+07R,NP-8216
195810Lamarsh+ ALL DATA
19900117EVL
A 1 1 N,X
EVL 1USAUNC10020
13D8 4.1-02 1.8+07R,TID-21294
196303Goldstein.TOT SEL
19900117EVL
A 1 1 N,X
EVL 1USAAI 10030
13DC 1.0-03 1.0+07R,NAA-SR-M-8904
196308Alter+.TOT SCT NG
19900117EVL
A 1 1 N,X
EVL 1USAAI 10030
23DC 1.0+04 1.4+07R,NAA-SR-TDR-,6545
196106Alter.TABULATED TOT,SEL,SIN
19900117EVL
A 1 1 N,X
EVL 1USAAI 10030
33DC 1.0+00 1.0+07R,NAA-SR-TDR-,5861
196011Alter.TABULATED TOT,SEL,SIN.MTECARLO 19900117EVL
A 1 1 N,TOT
CS 1USACOL10010
13E2 Maxw
J,PR,48,265
193508Dunning+ IONCH,TRANS,SIG SLOW+FAST N 19900117TOTA 1 1 N,TOT
CS 1USACOL10010
26EC Maxw
4,EXFOR12634.002
198403.1 PT. SIGMA.
19900117TOTA 1 1 N,TOT
CS 1USAPTN10010
12E2 2.4+06
J,PR,52,911
193711Ladenburg+ TRANSMISSION, D-D NEUTS
19900117TOTA 1 1 N,TOT
CS 1USAPTN10010
23EC 2.4+06
J,PR,52,1255
193712.FURTHER ANALYSIS
19900117TOTA 1 1 N,TOT
CS 1USAPTN10010
36E+ 2.4+06
4,EXFOR13790.002
200208.1 PT. SIGMA.
20020812TOT
A 1 1 N,TOT
CS 1USABRK10010
13E2 Maxw
2.5-02J,PR,55,339
193902Libby+ ORTHO+P-HYDROGEN, GAS TRANS
19900117TOTA 1 1 N,TOT
CS 1USABRK10010
26E+ 2.5-02
4,EXFOR13789.002
200208.1 PT. SIGMA.
20020812TOT##---Block from EXFOR=O0901 Z=15 A=CMP S= R=P,X Q=TT: Institute="2SF HLS" RS=15-P-CMP(P,X)0-NN-1,,TTY
A 15CMP P,X
TT 2SF HLSO0901
12Ex
J,NIM/B,28,199
198701Raisanen+
X4A 20051017
A 15CMP P,X
TT 2SF HLSO0901
26Ex
4,EXFORO0901.076
200405.2pt
PR=NN-1
X4A 20051017##---Block from EXFOR=22108 Z=73 A=181 S= R=N,P Q=CS: Institute="2ZZZGEL" RS=73-TA-181(N,P)72-HF-181,,SIG
A 73181 N,P
CS 2ZZZGEL22108
12Ex 1.3+07 2.0+07J,ARI,39,(5),407
198801Woelfle+
X4A 20051017
A 73181 N,P
CS 2ZZZGEL22108
26Ex 1.3+07 2.0+074,EXFOR22108.006
198902.15pt
PR=Hf-181
X4A 20051017;PROD=72-HF-181## New block:A 99255 0,F
FY 3INDTRM34190
13R$ Spon
J,PRM,33,109
198907Prakash. GRPH:SCHEMATIC A-DIST,CFD
19900516NFY;PROD=23-V-66,24-CR-68/69/70
A 99255 N,0
RP 4CCPFEI44130
13TO 2.0+06 4.0+06J,YF,39,281
198402Kupriyanov+ SYSTEMATCS.TBL AVG WN/WF 19850319RES
A 99255 N,0
RP 4CCPFEI44130
24T$ 2.0+06 4.0+06J,SNP,39,176
198402.ENGLISH OF YF 39 281
19850319RES

16

CINDA 2001 Manual17