Appendix B

Information Identifier Keywords

This appendix provides a listing of all information-identifier keywords, along with details about their use. The keywords appear in alphabetical order.

ADD-RES.  Gives information about any additional results obtained in the experiment, 
	but which are not compiled in the data tables. Codes are given in Dictionary 20.
	Example:	ADD-RES		(RANGE) Range of recoils measured.


ANALYSIS.  Gives information as to how the experimental results have been analyzed 
	to obtain the values given under the heading DATA which actually represent 
	the results of the analysis. Codes are found in Dictionary 23.
	Example:	ANALYSIS	(MLA) Breit-Wigner multilevel analysis


ASSUMED.  Gives information about values assumed in the analysis of the data, 
	and about COMMON or DATA fields headed by ASSUM or its derivatives. 
	The format of the code is: (heading,reaction,quantity)
	Heading field:  data heading to be defined.
	Reaction field and quantity field: coded as under the keyword REACTION.
	Example:	ASSUMED		(ASSUM,6-C-12(N,TOT),,SIG)


AUTHOR.  Gives the authors of the work reported.
	Example:	AUTHOR	(R.W.McNally Jr,A.B.JONES)


COMMENT.  Gives pertinent information which cannot logically be entered under 
	any other of the keywords available.


CORRECTION.  Gives information about corrections applied to the data in order 
	to obtain the values given under DATA.  See also LEXFOR, Correction.


COVARIANCE.  Gives covariance information provided by the experimentalist, 
	or to flag the existence of a covariance data file.  
	See Appendix D for covariance file format.
	Example:  COVARIANCE	(COVAR) COVARIANCE FILE EXISTS AND MAY BE OBTAINED ON REQUEST.


CRITIQUE.  Gives comments on the quality of the data presented in the data table.


DECAY-DATA.  Gives the decay data for any nuclide occurring in the reaction 
	measured as assumed or measured by the author for obtaining the data given (see note-1). 
	The general format of the coding string consists of three major fields 
	which may be preceded by a decay flag:  
		((decay flag)nuclide,half-life,radiation).

Flag.  A fixed-point number that also appears in the data section under the data 
heading DECAY-FLAG.  If the flag may be omitted, its parentheses are also omitted.

Nuclide field.  A nuclide code. 

Half-life field.  The half-life of the nuclide specified, coded as a floating-point 
number, followed by a unit code with the dimensions of TIME.

Radiation field.  Consists of three subfields: (type of radiation, energy, abundance)  
This field may be omitted, or repeated (each radiation field being separated by a comma).  
The absence of any subfield is indicated by a comma; trailing commas are not included.

	SF1.  Type-of-radiation.  A code from Dictionary 13. Where two or more different decay modes are possible and are not distinguished in the measurement, two or more codes are given; each separated by a slash.  (See Example b, following).

	SF2.  Energy.  The energy of the radiation in keV, coded as a floating-point number.  In the case of two or more unresolved decays, two or more energies, or a lower and upper energy limit, are given, each separated by a slash.  (See Example e).

	SF3.  Abundance.  The abundance of the observed per decay, coded as a floating-point number.

	Examples
	a) DECAY-DATA	(60-ND-140,3.3D)	(radiation field omitted)
	b) DECAY-DATA	(59-PR-140,,B+/EC,,0.500)	(half-life and decay energy omitted)
	c) DECAY-DATA	(25-MN-50-G,0.286SEC,B+,6610.)	(abundance omitted)
	d) DECAY-DATA 	((1.)60-ND-138,5.04HR,DG,328.,0.065)	(decay flag, all fields present)
	e) DECAY-DATA	(60-ND-139-M,5.5HR,DG,708./738.,0.64)	(the abundance given is the total abundance of both ( rays)
	f) DECAY-DATA 	(60-ND-139-G,30.0MIN,B+,,0.257,
						DG,405.,0.055)
			(60-ND-139-M,5.5HR,	DG,738.,0.37,
						DG,982.,0.29,
						DG,708.,0.27,
						DG,403.,0.03,
						B+,,0.006)

DECAY-MON.  Gives the decay data assumed by the author for any nuclide occurring 
	in the monitor reaction used.  The coding rules are the same as those 
	for DECAY-DATA, except that there is no flag field.

DETECTOR.  Gives information about the detector(s) used in the experiment. 
	Codes are found in Dictionary 22.  If the code COIN is used, then the codes 
	for the detectors used in coincidence follow within the same parenthesis;
	Example:	DETECTOR	(COIN,NAICR,NAICR)

EMS-SEC.  Gives information about secondary squared effective mass of a particle 
	or particle system, and to define secondary-mass fields given in the data table.  
	The format of the coded information is:   (heading, particle).

	Heading Field contains the data heading or the root (see note-2) of the data heading to be defined. 
	Particle Field contains the particle or nuclide to which the data heading refers.  
	The code is:
		either	a particle code from Dictionary 13.
		or 	a nuclide code.
	Example:	EMS-SEC	(EMS1,N)
			(EMS2,P+D)

EN-SEC.  Gives information about secondary energies, and to define 
	secondary-energy fields given in the data table.  
	The format of the coded information is:  (heading,particle).

	Heading Field.  Contains the data heading or the root of the data heading to be defined.
	Particle Field.  Contains the particle or nuclide to which the data heading refers.  The code is:
		either	a particle code from Dictionary 13.
		or	a nuclide code.
	Example:	EN-SEC	(E1,G)
			(E2,N)
			(E-EXC,3-LI-7

ERR-ANALYS.  Explains the sources of uncertainties and the values given in 
	the COMMON or DATA sections under data headings of the type ERR- or -ERR.  
	The general code format is    (heading,correlation factor) free text

	Heading Field.  Contains the data heading or the root (see note-3) of the data heading to be defined.  
	Correlation Factor Field contains the correlation factor, coded as a floating point number.

	Example:	
	BIB
	...
	ERR-ANALYS	(EN-ERR) followed by explanation of energy error
			(ERR-T)  followed by explanation of total uncertainty
 			(ERR-S)  followed by explanation of statistical uncertainty

EXP-YEAR.  Defines the year in which the experiment was performed when it 
	differs significantly from the data of the references given 
	(e.g., classified data published years later).
	Example:	EXP-YEAR	(1965)

FACILITY.  Defines the main apparatus used in the experiment.  The facility 
	code from Dictionary 18 may be followed by an institute code from 
	Dictionary 3, which specifies the location of the facility.
	Example:	FACILITY	(CHOPF,1USACOL)
					(SPECC,1USABNL)

FLAG.  Provides information to specific lines in a data table.  See also LEXFOR, Flags.
	Example:
	BIB
	...
	FLAG	(1.) Data averaged from 2 runs
 		(2.) Modified detector used at this energy
 	ENDBIB
	...
	DATA
	EN	DATA	FLAG
 	KEV	MB	NO-DIM
	1.2	123.	1.
	2.3	234.
	3.4	456.	2.
 	ENDDATA



HALF-LIFE.  Gives information about half-life values and defines half-life fields 
	given in the data table.  The general coding format is:  (heading,nuclide)
	Example:	HALF-LIFE	(HL1,41-NB-94-G)
					(HL2,41-NB-94-M)

HISTORY.  Documents the handling of an entry or subentry.  The general format 
	of the code is:  (yyyymmddX), where yyyymmdd is the date (year,month,day) 
	and X is a code from Dictionary 15.
	Example:	HISTORY	(19940312C)
				(19960711A) Data units corrected.

INC-SOURCE.  Gives information on the source of the incident particle beam 
	used in the experiment.  Codes are found in Dictionary 19.  
	Example:	INC-SOURCE	(POLNS,D-T)
			INC-SOURCE	(MPH=13-AL-27(N,A)11-NA-24)

INC-SPECT.  Provides free text information on the characteristics and resolution 
	of the incident-projectile beam.

INSTITUTE.  Designates the laboratory, institute, or university at which the 
	experiment was performed, or with which the authors are affiliated.  Codes are given in Dictionary 3.
	Examples:	INSTITUTE	(1USAGA, 1USALAS)
			INSTITUTE	(2FR SAC)

LEVEL-PROP.  Gives information on the spin and parity of excited states. 
	The general format of the code is ((flag) nuclide, level identification, lever properties)

	Flag.  Coded as a fixed-point number that appears in the data section under 
	the data heading LVL-FLAG.  When the flag is omitted, its parentheses are also omitted.

	Nuclide.  Coded is a nuclide, except that the use of the extension G is optional.

	Level identification.  Identification of the level whose properties are specified, 
	given as either a level energy or level number.  If the field omitted, 
	its separating comma is omitted.

	Level Energy.  The field identifier E-LVL= followed by the excited state 
	energy in MeV,  coded as a floating-point number which also appears in 
	the data section under the data heading E-LVL.

	Level Number.  The field identifier LVL-NUMB= followed by the level number 
	of the excited state, coded as a fixed-point number which also appears in 
	the data section under the data heading LVL-NUMB.

	Level properties.  Properties for the excited state, each preceded by a 
	subfield identification.  At least one of the fields must be present.  
	If the field is omitted, its separating comma is omitted.

	Spin.  The field identifier SPIN=, followed by the level spin coded as a 
	floating point number.  For an uncertain spin assignment, two or more spins 
	may be given, each separated by a slash.

	Parity.  The field identifier PARITY=, followed by the level parity, 
	coded as e.g., +1. or -1.

	Examples:
		LEVEL-PROP	(82-PB-206,E-LVL=0.,SPIN=0./1.,PARITY=+1.)
				(82-PB-206,E-LVL-1.34,SPIN+3.,PARITY=+1.)
		LEVEL-PROP	((1.)82-PB-206,,SPIN=0./1.,PARITY=+1.)  
				((2.)82-PB-206,,SPIN=3.,PARITY=+1.) 
		LEVEL-PROP	(82-PB-207,LVL-NUMB=2.,SPIN=1.5,PARITY=-1)

METHOD.  Describes the experimental technique(s) employed in the experiment.  
	Codes are found in Dictionary 21.
	Example:	METHOD	(RCHEM) Radiochemical separation

MISC-COL.  Defines fields in the COMMON or DATA sections headed by MISC and it derivatives.
	Example:	MISC-COL	(MISC1) 	Free text describing 1st miscellaneous field
					(MISC2) 	Free text describing 2nd miscellaneous field

MOM-SEC.  Gives information about secondary linear momentum, and defines 
	secondary-momentum fields given in the data table.  The general code 
	format is: (heading,particle)

	Heading Field: the data heading or root (see note-4) of the data heading to be defined.  

	Particle Field:  the particle or nuclide to which the data heading refers. The code is:
		either 	a particle code from Dictionary 13. 
		or	a nuclide code.
	Example:	MOM-SEC	(MOM-SEC1,26-FE-56)
				(MOM-SEC2,26-FE-57)

MONITOR.  Gives information about the standard reference data (standard, monitor) 
	used in the experiment and defines information coded in the COMMON and DATA 
	sections under the data heading MONIT, etc. The general coding 
	format is ((heading) reaction)

	Heading Field.  Contains the data heading of the field in which the monitor 
	value is given.  If the heading is omitted, its parenthesis is omitted.

	Reaction Field.  The coding rules are identical to those for REACTION, 
	except that subfields 5 to 9 may be omitted if the reaction is known.

	Example:	
	REACTION	1 (AAAAA)
			2 (BBBBB)
	MONITOR		1 (CCCCC)
			2 (DDDDD)
	...
	DATA
	EN		DATA 1	DATA 2	MONIT 1		MONIT 2
	...


MONIT-REF.  Gives information about the source reference for the standard 
	(or monitor) data used in the experiment.
The general code format is ((heading)subaccession#,author,reference)

	Heading Field:  Data heading of the field in which the standard value is given.  
	If the heading is omitted, its parentheses are also omitted.

	Subaccession Number Field:  Subaccession number for the monitor data, 
	if the data is given in an EXFOR entry.  Cnnnn001 refers to the 
	entire  entry; Cnnnn000 refers to a yet unknown subentry.

	Author Field.  The first author, followed by "+" when more than one author exists.

	Reference Field. May contain up to 6 subfields, coded as under REFERENCE.

	Example:	
	MONIT-REF 	((MONIT1)BOO17005,J.GOSHAL,J,PR,80,939,1950)
			((MONIT2),A.G.PANONTIN+,J,JIN,30,2017,1968)


PART-DET.  Gives information about the particles detected directly in the experiment.  
	Particles detected in a standard/monitor reaction are not coded under this keyword.  
	The code is either a code from Dictionary 13, or, for particles heavier 
	than ( particles, a nuclide code. Particles detected pertaining to different 
	reaction units within a reaction combination are coded on separate records 
	in the same order as the corresponding reaction units. 
	Example:	PART-DET	(A)
			PART-DET	(3-LI-6)

RAD-DET.  Gives information about the decay radiations (or particles) and nuclides 
	observed in the reaction measured.  The general format of the code 
	is ((flag)nuclide, radiation).

	Flag is a fixed-point number which appears in the data section under the 
	data heading DECAY-FLAG.  If the field is omitted, its parentheses are also omitted.

	Nuclide contains a nuclide code.

	Radiation contains one or more codes from Dictionary 33, each separated by a comma.

	Examples:
	RAD-DET	(25-MN-52-M,DG,B+)
	RAD-DET	(48-CD-115-G,B-)
		(49-IN-115-M,DG)
	RAD-DET	((1.)48-CD-115-G,B-)
		((2.)49-IN-115-M,DG)

REACTION.  Specifies the data presented in the DATA section in fields 
	headed by DATA (see note-5).  The general format of the code is (reaction, quantity, data-type).

Reaction field.  The reaction field consists of 4 subfields.

SF1. Target nucleus.  Contains either:
a) a nuclide code.
	A = 0 denotes natural isotopic abundance.
b) a compound code.
c) a variable nucleus code ELEM and/or MASS
	Example:  (ELEM/MASS(0,B-),,PN)

SF2. Incident projectile.  Contains one of the following:
a) a particle code from Dictionary 28.
b) for particles heavier than an (, a nuclide code.

SF3. Process.  Contains one of the following:
a) a process code from Dictionary 30, e.g., TOT.
b) a particle code from Dictionary 29 which may be preceded by a multiplicity factor, 
	whose value may be 2->99. (see note-6), e.g., 4A.
c) for particles heavier than (, a nuclide code.
	Examples:	8-O-16
			8-O-16+8-O-16
d) combinations of a), b) and c), with the codes connected by '+'.
	Examples:	HE3+8-0-16
			A+XN+YP

If SF5 contains the branch code UND (see note-7) (undefined), the particle codes given in SF3 
represent only the sum of emitted nucleons, implying that the product nucleus coded 
in SF4 has been formed via different reaction channels.  The code (DEF) in SF5 
denotes that it is not evident from the publication whether the reaction channel 
is undefined or defined.

SF4. Reaction Product.  In general, the heaviest of the products is defined as the 
reaction product (also called residual nucleus).  In the case of two reaction 
products with equal mass, the one with the larger Z is considered as the heavier 
product.  Exceptions or special cases are:

* 	If SF5 contains the code SEQ, indicating that the sequence of several outgoing 
	particles and/or processes coded in SF3 is meaningful, the nuclide to be 
	coded in SF4 is the heaviest of the final products.
	Example:	(5-B-10(N,A+T)2-HE-4,SEQ,SIG)

* 	Where emission cross sections, production cross sections, product yields, etc., 
	are given for specified nuclides, particles, or gammas, the product considered 
	is defined as the reaction product (even if it is not the heaviest of several 
	reaction products).

	This subfield contains:
	either a blank, 
		Example: 	(26-FE-56(N,EL),,WID)
	or a nuclide code.
		Example: 	(51-SB-123(N,G)51-SB-124-M1+M2/T)
	or,	a variable nucleus codes:
		Example:	(92-U-235(N,F)ELEM/MASS,CUM,FY)

Quantity consists of four subfields, each separated by a comma.  All combinations 
of codes allowed in the quantity field are given in Dictionary 36.

SF5 Branch.  Indicates a partial reaction, e.g., to one of several energy levels.

SF6 Parameter.  Indicates the reaction parameter given, e.g., differential cross section.

SF7 Particle Considered.  Indicates to which of several outgoing particles 
the quantity refers (see note-8). Multiple codes, e.g., for the correlation between outgoing 
particles, all particles are separated by a slash.

SF8 Modifier.  Contains information on the representation of the data, e.g., relative data.

Data Type Field. Indicates whether the data are experimental, 
theoretical, evaluated, etc.  Codes are found in Dictionary 35. 

Variable Nucleus.  For certain processes, the data table may contain yield or 
production cross sections for several nuclei which are entered as variables 
in the data table.  In this case, either SF1 or SF4 of the REACTION keyword 
contain one of the following codes:
	ELEM 	- if the Z (charge number) of the nuclide is given in the data table.
	MASS 	- if the A (mass number) of the nuclide is given in the data table.
	ELEM/MASS	- if the Z and A of the nuclide are given in the data table.

The nuclei are entered in the common data or data table as variables under 
the data headings ELEMENT and/or MASS with the units NO-DIM.

If the data headings ELEMENT and MASS are used, a third field with the 
data heading ISOMER is used when isomer states are specified:
	0.	= ground state (used only if nuclide has also an isomeric state),
	1.	= first metastable state (or the metastable state when only one is known),
	2.	= second metastable state, etc.

Decay data for each entry under ELEMENT/MASS(ISOMER) and their related parent or 
daughter nuclides may be given in the usual way under the information-identifier 
keyword DECAY-DATA.  Entries under the data headings ELEMENT/MASS(ISOMER) are 
linked to entries under DECAY-DATA (and RAD-DET, if present) by means of a decay flag (see note-9).

	Example:
	BIB
	REACTION	(...(...,F)ELEM/MASS,...)
	ENDBIB
	NOCOMMON
	DATA
	EN	ELEM	MASS	ISOMER	DATA
	MEV	NO-DIM	NO-DIM	NO-DIM	B
	 ...	 61.	 148.	 0.	 ...
	 ...	 61.	 148.	 1.	 ...
	 ...	 61.	 149.	 	 ...
	 ...	 62.	 149.		 ...


Variable Number of Emitted Nucleons.  Where mass and element distributions of 
product nuclei have been measured, the sum of outgoing neutrons and protons may 
be entered as variables in the data table.  In this case SF3 of the REACTION 
keyword contains at least one of the following codes:
	XN	- variable number of neutrons given in the data table.
	YP	- variable number of protons given in the data table.

The numerical values of the multiplicity factors X and Y are entered in the data 
table under the data headings N-OUT and P-OUT, respectively.

	Example:
	BIB
	REACTION	(...(...,XN+YP)...)
	...
	ENDBIB
	NOCOMMON
	DATA
	EN	N-OUT	P-OUT	DATA
	MEV	NO-DIM	NO-DIM	B
	...
	...
	...
	ENDDATA




Reaction Combinations.  For experimental data sets referring to complex 
combinations of materials and reactions, the code units defined in this 
section can be connected into a single machine-retrievable field, with 
appropriate separators and properly balanced parentheses.  The complete 
reaction combination is enclosed in parentheses.

The following reaction combinations are defined:
	((------)+(-----))	Sum of 2 or more quantities (see LEXFOR, Sums).
	((------)-(-----))	Difference between 2 or more quantities.
	((------)*(-----))	Product of 2 or more quantities (see LEXFOR, Products). 
	((------)/(-----))	Ratio of 2 or more quantities (see LEXFOR, Ratios).
	((------)//(-----))	Ratio of 2 quantities, where the numerator and denominator 
				refer to different values for one or more independent 
				variables (see LEXFOR, Ratios).
	((------)=(-----))	Tautologies (see LEXFOR, Tautologies for usage).

When a reaction combination contains the separator "//", the data table will contain 
at least one independent variable pair with the data heading extensions -NM and -DN.

	Example:
	BIB
	REACTION	(((92-U-238(N,F)ELEM/MASS,CUM,FY,,FIS)/
			(92-U-238(N,F)42-MO-99,CUM,FY,,FIS))//
			((92-U-235(N,F)ELEM/MASS,CUM,FY,,MXW)/
			(92-U-235(N,F)42-MO-99,CUM,FY,,MXW)))
	RESULT		(RVAL)
	...
	ENDBIB
	COMMON
	EN-DUM-NM	EN-DUM-DN
	MEV		EV
	 1.0		 0.0253
	ENDCOMMON
	DATA
	ELEMENT		MASS	DATA
	...
	ENDDATA



REFERENCE.  Gives information on references that contain information about the data coded.  
Other related references are not coded under this keyword (see REL-REF, MONIT-REF).  
The general coding format is (reference type, reference, date).

The format of the reference field is dependent on the reference type.  The general 
format for each reference type follows.
 
Type of Reference = B or C; Books and Conferences.
General code format: (B or C,code,volume,(part),page(paper #),date).  Codes from Dictionary 7.

Examples:
 (C,67KHARKOV,,(56),196702)	Kharkov Conference Proceedings, paper #56, February 1967.
 (C,66WASH,1,456,196603)	Washington Conference Proceedings, Volume 1, page 456, March 1966
 (B,ABAGJAN,,123,1964)		Book by Abagjan, page 123, published in 1964.

Type of Reference = J: Journals.
General code format is (J,code,volume,(issue #),page,date).  Codes are from Dictionary 5.
Examples:
 (J,PR,104,1319,195612)		Phys. Rev. Volume 104, page 1319, December 1956
 (J,XYZ,5,(2),89,196602)	Journals XYZ, Volume 5, issue #2, page 89, February 1966

Type of Reference = P or R or S; Reports.
General code format:  (P or R or S,code-number,date).  Codes from Dictionary 6.
Examples:
 (R,JINR-P-2713,196605)		Dubna report, series P, number 2713, May 1966.
 (P,WASH-1068,185,196603)	WASH progress report number 1068, page 185, March 1966.


Type of Reference = T, or W; Thesis or Private Communication.
General code format:  (W or T,author,page,date)
Examples:
 (W,BENZI,19661104)		private communication from Benzi, November 4, 1966.
 (T,ANONYMOUS,58,196802)	thesis by Anonymous, page 58, February 1968.


REL-REF.  Gives information on references related to, but not directly 
pertaining to, the work coded.  The general code format is:  (code,subaccession#,author,reference).

Code:  code from Dictionary 17.

Subaccession #:  EXFOR subaccession number for the reference given, if it exists.  
		Cnnnn001 refers to the entire entry Cnnnn.  
		Cnnnn000 refers to a yet unassigned subentry within the entry Cnnnn.

Author:  first author, coded as under AUTHOR, followed by + when more than one author exists.

Reference: coded as for REFERENCE. 

Example:
(C,B9999001,A.B.NAME+,J,XYZ,5,(2),90,197701)	Critical remarks by A.B.Name, et al., 
			in journal XYZ, volume 5, issue #2, p. 90,  January 1977.


RESULT.  Describes commonly used quantities that are coded as REACTION combinations.
	Example:	REACTION	((Z-S-A(N,F)ELEM/MASS,CUM,FY)/
					(Z-S-A(N,F)MASS,CHN,FY))
			RESULT	(FRCUM)


SAMPLE.  Used to give information on the structure, composition, shape, etc., 
	of the measurement sample.


STATUS.  Gives information on the status of the data presented.  Entered in 
	one of the general code formats, or for cross reference to another data set, 
	the general code format is: (code,subaccession#)

Code:  code from Dictionary 16.

* Subaccession# Field:  cross-reference to an EXFOR subaccession number, see REL-REF.

Example:
	STATUS	(SPSDD,10048009)	-	this subentry is superseded by subentry 10048009.


TITLE.  Gives the title for the work referenced.


Notes:
1 Decay data relevant to the monitor reaction are coded under the keyword DECAY-MON and not under DECAY-DATA.
2 Root means that the data heading given will also define the same heading followed by -MIN, -MAX or -APRX.
3 Root means that the data heading given also defines the heading preceded by + or -.
4 Root means that the data heading given will also define the same heading followed by -MIN, -MAX or -APRX.
5 And similar headings such as DATA-MIN, DATA-MAX, etc.
6 In the few cases where the multiplicity factor may exceed 99, the Variable Number of Emitted Nucleons Formalism may be used, see page 6.7.
7 The code UND is presently used only for charged particle reaction data.
8 Note that the particle considered is not necessarily identical to the particle detected, e.g., the angular distribution of an outgoing particle which has been deduced from a recoil particle detected.
9 If the half-life is the only decay data given, this may be entered in the data table under the data heading HL, although this is not recommended.