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

Memo CP-D/410 (Rev.)

Date:
To:
From:

Subject:

27 August 2004
Distribution
O. Schwerer

Revised NRDC Protocol

Appended is the revised NRDC Protocol (Part IV of the NRDC Exchange Formats Manual,replacing Appendix P of the old EXFOR Systems Manual). It is based on a draft by Vicki
McLane and consists of EXFOR, CINDA and Dictionary Protocols as well as information onother aspects of the NRDC exchanges.
Actually we have now two "Protocols" dealing with the NRDC: This long one (altogether 20
pages) and the 2-page Protocol which was introduced at the 2002 NRDC Meeting and slightly
revised last year, which is included in the "Network document" INDC(NDS)-401 Rev.4 as
Annexes 3 and 4.
Both Protocols are dealing with the same subject; in Vicki McLane's draft of last year, thelong one contained about 95% of the contents of the short one, but spread out in different
chapters, and partly reworded; no cross-reference exists between the two. I very strongly
believe that this situation needs to be harmonized, both for the sake of consistent updating andof usability for the NRDC staff. I see the following options to achieve this:-Issue the long Protocol as Part IV of the NRDC Manual, as foreseen by Vicki McLane,and replace Annexes 3 and 4 in the Network Document by a reference to it (this is myfavorite solution);-

Make the long Protocol part of the Network document; i.e., replace Annexes 3 and 4 by
the long Protocol as attached to this memo;-

The minimum solution (not favored by me) would be to at least have different names forboth protocols (e.g., call the long one "Technical Protocol") and add cross-references inboth places.

I am in favor of the first option. I realize that getting rid of the short version may be an
inconvenience for managers who do not have the time to read long documents; on the other
hand, the existing short version has the effect that technical staff may not read, or even notnotice, the long version which has important technical information for them.

The contents of the draft represents my best understanding of the current consensus, plus atentative addition on the EXFOR compilation scope based on the discussion which wasreflected in various CP memos in the past months (the latest one was CP-D/407; this isreflected in a new paragraph "Scope of compilation" on p.2 and in a new Appendix B). Since
this topic will certainly be discussed further at the NRDC meeting, some modifications to thedraft are to be expected.
The draft and the harmonization of the two Protocols will be discussed and decided at theforthcoming NRDC meeting.

Distribution:
gezg@iris.ciae.ac.cn
hongwei@iris.ciae.ac.cn
tarkanyi@atomki.hu
stakacs@atomki.hu
katakura@ndc.tokai.jaeri.go.jp
hasegawa@ndc.tokai.jaeri.go.jp
vlasov@kinr.kiev.ua
kaltchenko@kinr.kiev.ua
ogritzay@kinr.kiev.ua
jhchang@kaeri.re.kr
ohtsuka@nucl.sci.hokudai.ac.jp
m.wirtz@iaea.org
m.lammer@iaea.org
v.pronyaev@iaea.org
schwerer@iaeand.iaea.org
v.zerkin@iaea.org
henriksson@nea.fr
exfor@nea.fr

oblozinsky@bnl.gov
vml@bnl.gov
nordborg@nea.fr
manokhin@ippe.obninsk.ru
maev@ippe.obninsk.ru
may@obninsk.ru
Mmarina@ippe.obninsk.rug
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
oba@nrdf.meme.hokudai.ac.jp
yxzhuang@iris.ciae.ac.cn

2

Nuclear Reaction Data Centers
Exchange Formats ManualPart IV
Protocolfor Cooperation between
the Nuclear Reaction Data Centers
Draft edited byVictoria McLane
National Nuclear Data Center
on behalf of the
Nuclear Data Center Network
July 2003
Revised Draft (August 2004) by
Otto Schwerer
IAEA Nuclear Data SectionNRDC Protocol(Blank page)ii

NRDC Manual Part IV

August 2004

NRDC Protocol

Table of Contents

INTRODUCTION ..................................................................................................................... 1
EXFOR PROTOCOL ................................................................................................................ 2
Scope of compilation ............................................................................................................. 2
Data Compilation Responsibility ........................................................................................... 2
Neutron Reaction Data Compilation.................................................................................. 3
Charged-Particle Reaction Data Compilation.................................................................... 3
Photonuclear Reaction Data Compilation.......................................................................... 4
EXFOR Transmissions .......................................................................................................... 4
Assignment of Accession Numbers. .................................................................................. 4
Procedure for transmitting new exchange files. ................................................................. 5
Procedure for files received with errors. ............................................................................ 5
Alterations to EXFOR entries ("Retransmissions"). .......................................................... 5
CINDA PROTOCOL ................................................................................................................. 7
Data Compilation Responsibility ........................................................................................... 7
CINDA Transmissions ........................................................................................................... 7
CHANGES TO SCOPE, FORMAT AND CODING RULES OF CINDA OR EXFOR .......... 9
DICTIONARY PROTOCOL................................................................................................... 11
Routine transmission of Dictionaries. .................................................................................. 11
Addition of new codes. ........................................................................................................ 11
COMMUNICATION BETWEEN CENTERS ........................................................................ 12
MANUALS .............................................................................................................................. 13
EXFOR PROCESSING AND RETRIEVAL CODES ............................................................ 14
Appendix A: Compilation Responsibilities ............................................................................. 15
Appendix B: Compilation Scope ............................................................................................ 16

August 2004

NRDC Manual Part IViii

NRDC Protocol(Blank page)

iv

NRDC Manual Part IV

August 2004

NRDC Protocol

INTRODUCTION

The general scope of the Nuclear Reaction Data Centers Network (NRDC) exchange is all
experimental microscopic nuclear reaction data. Modifications to the general scope of thedata exchange can be adopted only as a result of an agreement between the “Core” Centers of
the NRDC.
The Core Centers will be defined by NDS based on contributions to network and user service
capabilities. The currently defined Core Centers and their respective service areas are:•

The National Nuclear Data Center (NNDC) services the U.S.A. and Canada.

•

Nuclear Energy Agency Data Bank (NEA-DB) services the non-American member
Countries of the O.E.C.D.

•

The Russian Nuclear Data Center (CJD), services the countries of the former U.S.S.R.

•

The I.A.E.A. Nuclear Data Section (NDS) services I.A.E.A. Member States not includedin the service areas of the above three centers.

The working language of the Network is English.
The Nuclear Data Section (NDS) will be responsible for ensuring that data compilations andexchanges are done in an efficient, productive and timely manner. The role of NDS will beto:•assign clear responsibilities for the creation and correction of data compilations, and drivethese activities forward,•

ensure implementation of compilation rules,•

decide on all issues relating to dictionary codes,•

be responsible for CINDA and EXFOR distribution to the other data centers

August 2004

NRDC Manual Part IV

1

NRDC Protocol

EXFOR PROTOCOL

Data tapes are exchanged regularly between the Nuclear Reaction Data Centers (NRDC) in
the EXFOR format in accordance with the conventions laid down in the EXFOR Exchange
Formats Manual.
NDS will maintain and distribute the EXFOR Master file.
All matters that affect EXFOR, in general, must be agreed to by the Nuclear Reaction Data
Centers. Final decisions on proposals concerning compilation rules and new quantities canbe made with Core Center agreement after discussions among all centers. NDS will be thefinal arbiter in case the Core Centers are unable to reach a decision.
All free text comments within all EXFOR entries shall be in English.

Scope of compilation
While the general scope of compilation is all experimental microscopic nuclear reaction data,
the NRDC network may divide the scope into the following categories:
A)
B)
C)

Data types which must be compiled,
Data types which may be compiled on a voluntary basis and are exchanged within theregular transmission files,
Additional data types which may be transmitted only on separate transmission files
using different center identification characters.

The definitions of categories A, B and C must be agreed by the network, and all centers must
define and announce their compilation scopes for categories B and C to the network.
The current definitions are given in Appendix B of this Protocol.

Data Compilation Responsibility
NDS will assign areas of responsibility for data compilation. If a center assigned to aparticular area of compilation (e.g., neutron data from a country or countries) is not carryingout their responsibilities, i.e., compiling all new data for that area in a timely manner, theNDS coordinator will reassign all or part of those responsibilities to another volunteer center 1.
An area may be for a given projectile or set of projectiles, for a given country or group of
1

As a consequence, the obligatory link between the geographical area of the Institute and the accession number,which has been in force for neutron data, may now be lifted for all data.

2

NRDC Manual Part IV

August 2004

NRDC Protocol

countries, for a given data type or data types, or for any combination of these.
A center responsible for an area of compilation may agree with another network center toshare the compilation work for that area on a regular basis. However, the responsibility forcoverage and quality of the compilation remains with the responsible center. The currently
assigned EXFOR compilation responsibilities are given in Appendix A of this Protocol.
If a center has a need for a particular data set to be compiled immediately, the center should
send a request to the responsible center with a copy to NDS. If the responsible center cannot
compile the data in time needed to meet the requirements of the center making the request,that center may compile the data as an area Z entry. The entry will then be sent to both the
responsible center and NDS. If the responsible center does not intend to enter the data in atimely fashion, the NDS may then transmit the Z entry to all centers. The responsible center
would then be responsible for deleting the Z entry if they replace it with an entry for theirarea.
For corrections to entries of another center, entries of different accession number areas may
be transmitted on the same TRANS file.
Neutron, charged-particle, and photonuclear reaction data must be compiled in separate
entries, with appropriate identification, even if they are reported in the same publication.
Neutron Reaction Data Compilation.
The responsibility for the collection, compilation and dissemination of neutron data
information is shared among the four major neutron data compilation centers, each being
responsible for a defined service area.
Within the scope of this protocol each center is expected to compile the data measured in its
service area as fast and as thoroughly as possible. If two institutions from different service
areas are involved, the primary institution defines the responsible center. See LEXFOR,Institutes for definition of primary institution.
Where the primary institute is not clear, the centers concerned should consult each otherbefore compiling the data in order to avoid duplicate entry of the same data.
An effort must be made to compile all neutron reaction data published after 1 July, 1970.
Earlier data will be compiled as time permits.
Although each center may compile data measured outside its service area, regulartransmission of EXFOR data from any one center shall include data only from its own service
area.
Each center shall keep an archival copy of the latest version of each of the EXFOR entries
which it originated and shall be ready to provide the data to any center should it be required.
All matters concerning the exchange of neutron data must be agreed to by the four primary
neutron data centers.
Charged-Particle Reaction Data Compilation.

August 2004

NRDC Manual Part IV

3

NRDC Protocol

The following nuclear reaction data centers have the responsibility for the collection,compilation, and dissemination of charged-particle data information from their respective
countries.
•

National Nuclear Data Center (NNDC): for the United States and Canada,•

Japan Charged-Particle Reaction Group (JCPRG): for data from Japan,•

ATOMKI: for data from Hungary and Jülich,•

Russian Nuclear Structure and Reaction Data Center (CAJaD): for countries of theformer Soviet Union, except Ukraine, and for compilation of entries from countries notcovered by other centers after coordination with NDS;•

IAEA Nuclear Data Section (NDS): all countries not covered by other centers.

If two institutions from different service areas are involved, the primary institution defines
the center responsible (see LEXFOR, Institutes, for definition of primary institution).
If a center wishes to compile data outside its area of responsibility, the following proceduresshould be followed.
A center wishing to compile data (C1) will contact the center in whose area of responsibility
the data were produced (C2), with copy to NDS, with a list of the data sets to be compiled.
C2 will inform C1, as quickly as possible, with copy to NDS, whether the data either havebeen compiled or are in the process of being compiled by another center. If the data are notcompiled or being compiled, C2 will either agree to compile them with priority, or ask that
C1 compile the data and to and include it in the next regular C1 transmission file.
1) The center wishing to compile data should notify NDS of the data sets that they intend tocompile.
2) NDS will check that the data set has not been compiled, and is not being compiled byanother center, and will let the originating center know if they may go ahead with thecompilation. All centers are responsible for checking that the data sets transmitted bythem do not duplicate existing data.
Photonuclear Reaction Data Compilation.
The Centre for Photonuclear Experiments Data (CDFE) will be responsible for coordinating
the compilation of photonuclear reaction data.
For photonuclear data there is no requirement for completeness.
EXFOR Transmissions
Assignment of Accession Numbers.
The methods of assigning accession numbers may be different at each center. That is to say,a center may assign them manually or automatically (by computer). A center may assign
legal EXFOR accession numbers only to works within its agreed area of responsibility.
Where the responsibility for compiling a given data set is not clear, the centers concerned
should consult each other before compiling the data in order to avoid duplicate entry of thesame data. (See LEXFOR, Institute).

4

NRDC Manual Part IV

August 2004

NRDC Protocol

Procedure for transmitting new exchange files.
The originating center deposits new exchange files on the IAEA open area, subdirectory
2
TRANS.PRELIM, and notifies the other centers. The other centers will have one month tosuggest modifications to the file.
As soon as possible after the month has passed, the originating center should:
1. Either make any suggested modifications to the file, or notify the other centers why themodifications have not been made.
2. Deposit the corrected file in the IAEA open area, subdirectory TRANS, 3 and notify theother centers.
3. Request NDS to delete the preliminary version from the IAEA open area.
NDS may correct or assign volunteers to correct preliminary transmissions that are notcorrected and resubmitted as final transmissions in a timely manner, and will be responsiblefor distributing all final transmissions.
In general, it is the responsibility of the individual centers to transfer the files from the IAEA
open area.
Procedure for files received with errors.
There are the following cases to be considered for files received with errors.
1. If a file can not be physically read, in part or whole, then the originating center should berequested to send another identical file, which should be done with minimum delay.
2. If there are errors (format, structure, etc.) in one or more entries, then the originating
center should be notified of the errors by e-mail with the usual CP-Memo distribution.
3. Problematic entries which had to be removed from a preliminary transmission can be put
into a special subdirectory of the NDS open area, TRANS.PROBLEMS. These entries
will be reviewed by the other centers and can be finalized at the next NRDC meeting.
Alterations to EXFOR entries ("Retransmissions").
Alterations to EXFOR entries are, in general, transmitted only by the originating center andare included in the regular EXFOR transmissions. However, retransmission of entries
belonging to a center that is no longer active in an area compilation may be done at anothercenter by agreement of the cooperating centers.
Serious corrections (for example, those involving the COMMON or DATA sections, oressential BIB keywords such as REACTION, MONITOR, etc.) should be transmitted as quickly as
possible. Less serious corrections can be made and transmitted as workloads permit.
Notification of errors found in entries originating at another center should be communicated2
3

Suggested naming convention: PRELIM.nnnn, where nnnn is the file identification number.
Suggested naming convention: TRANS.nnnn, where nnnn is the file identification number.

August 2004

NRDC Manual Part IV

5

NRDC Protocol

to all centers. The NDS should make sure these corrections are done in a timely manner. Ifthey are not, the coordinator will ask one of the other centers to submit the corrected entries.

6

NRDC Manual Part IV

August 2004

NRDC Protocol

CINDA PROTOCOLThe CINDA2001 format shall be the method of exchange between the Nuclear Reaction Data
Centers. The CINDA Formats Manual shall contain the coding rules for all CINDA
exchanges.
NDS will maintain and distribute the CINDA Master file.
All matters that affect CINDA2001 formats, in general, must be agreed to by the Nuclear
Reaction Data Centers. Final decisions on proposals can be made with Core Center
agreement after discussions among all centers. NDS will be the final arbiter in case the Core
Centers are unable to reach a decision.
The information compiled in CINDA shall consist of references to experimental nuclear
reaction data and evaluated nuclear data libraries. The quantities to be entered shall be thosethat have been agreed upon for entry into EXFOR and into the ENDF-formatted evaluatedlibraries.
Updates to the CINDA2001 formats must be agreed upon by the core centers.
Data Compilation Responsibility
NDS will assign responsibilities for CINDA compilation.
A subset of the “core” centers will be responsible for all CINDA Transmissions. That is, the
NNDC will be responsible for the US and Canada, the NEA Data Bank will be responsible
for the NEA member countries, and the NDS will be responsible for the rest of the world. Allother centers compiling new references will transmit the data through one of these threecenters.
Updates sent by a center containing new entries and updates to entries that are theresponsibility of the originating center shall be transmitted in a separate file (exchange file)from new entries and updates to entries that are the responsibility of another center. The
latter shall be sent in reader files, separated by coordinating center. New blocks included onreader files shall have block numbers beginning with zero (0) and sequence numbers equal tozero.
CINDA Transmissions
A CINDA Transmission shall consist of the exchange file and one or more reader files.
The EXFOR Accession Number will, in general, be used as the CINDA block number (seeEXFOR Protocol, page 4, for assignment of accession numbers).

August 2004

NRDC Manual Part IV

7

NRDC Protocol

The sequence number within a block shall be unique, i.e., if a line is deleted, the sequencenumber should not be reassigned.
The originating center shall deposit new CINDA transmissions on the NDS open area,
subdirectory CINDA.
In the case where there is problem with updates to files of a given center, the Nuclear Data
Section shall notify the original center before releasing the files. If the original center does
not respond in a timely manner, NDS shall have the authority to produce transmission files
for that center and release them to all data centers.
In general, it is the responsibility of the individual centers to transfer the files from the NDS
open area.

8

NRDC Manual Part IV

August 2004

NRDC Protocol

CHANGES TO SCOPE, FORMAT AND CODING RULES OF CINDA
OR EXFORNo changes in the basic structure of CINDA or EXFOR will be allowed without NRDC
agreement.
However, in particular the EXFOR format is continuously refined and expanded to include
new types of data as the need arises. These refinements are introduced through dictionary
updates, modifications of coding rules which may affect the formats or the file structure, orredefinition of the compilation scope.
Dictionary modifications or additions which appear to be trivial (inconsequential) will be
added to the dictionaries as soon as possible after receipt, without formal approval procedures.
For all other proposed changes, it will be the responsibility of the center originating the
proposal to obtain NRDC agreement, following the procedure outlined below.
The following procedure should be followed by each of the NRDC members in obtaining theagreement for changes or revisions:
1. The initial proposal should be disseminated to all centers. Wherever possible proposals
affecting the content of the Manuals should contain proposals for specific wording to beinserted in the Manual. Adequate explanation and documentation to help in preparing
LEXFOR entries should accompany any suggestions for additions to LEXFOR. Proposals
for new dictionary quantity codes (Dictionaries 30-37) should be supported by an
expansion, a full explanation of its use and limits, a list of corresponding Dictionary 36
entries, and, where appropriate, a reference to the data for which the code will be used.
All communications with regard to such proposals shall be in the form of CP Memos.
2. In the case where there is discussion on a proposal, the initiating center shall then collectand digest all comments, suggestions and counter proposals.
3. In this review, the initiating center shall consider all facts would affect the
CINDA/EXFOR associated computer codes.
4. A change in CINDA/EXFOR will not oblige centers to change existing entries (whether
they have been transmitted or not) unless stated explicitly in the proposal and approvedby the data centers.
5. The initiating center shall then distribute a technical evaluation of alternatives to the othercenters.
6. After receiving the response to this technical evaluation:a) In the case of positive agreement, the initiating center shall submit a final proposal
including all dictionary, CINDA Manual, EXFOR Systems Manual, and LEXFOR
updates and mention which computer programs will need to be updated.
b) If no positive agreement has been reached:- If the proposal implies a change in the basic structure of CINDA or EXFOR, or achange in the general scope, the proposal will be included in the agenda of the next
NRDC meeting. In order to be adopted at an NRDC meeting, a proposal should besent out at least one month prior to the meeting date.

August 2004

NRDC Manual Part IV

9

NRDC Protocol- In all other cases, NDS will seek to reach a consensus between the core centers, inwhich case the proposal is considered approved. If the core centers cannot come to anagreement, NDS acts as the final arbiter.
Whenever decisions are made at an NRDC meeting that require Manual changes, thedictionary and manual updates should be prepared and sent out as soon as possible after thedraft minutes are received. The minutes of the meeting should include either the proposed
dictionary and manual updates or a reference to the CP-Memo(s) in which they are given.

10

NRDC Manual Part IV

August 2004

NRDC Protocol

DICTIONARY PROTOCOL

Routine transmission of Dictionaries.
The IAEA Nuclear Data Section (NDS) is responsible for the coordination and the updatingof the EXFOR dictionaries. For this purpose, an archival dictionary file is maintained at
NDS in a special archive format (see Dictionary Exchange Formats Manual).
About every three months, or whenever a major alteration is made, NDS will transmit thecomplete dictionary file to the cooperating centers, either in the EXFOR or DANIEL format,
as each center prefers.
It is the responsibility of each center to verify that information is compiled in accordancewith the latest version of the dictionaries.
Addition of new codes.
The cooperating centers may propose new codes or any other dictionary alteration by meansof CP-Memos. A proposal for a new code should include any associated information needed
for the dictionary, along with an explanation of its use, and, where appropriate, references todata sets for which it will be used.
The center responsible for updating the dictionaries is also responsible for checking theconsistency of proposed alterations with other codes and with the manuals. Some latitude isallowed in the formulation of a final dictionary entry, but the meaning must not be changed
without the approval of the originating center. In questionable cases, the other centers should
be consulted. The cooperating centers are responsible within their respective areas forkeeping the laboratory (Dictionary 3) and bibliographic reference code (Dictionaries 5-7)
dictionaries up to date.
Consequential updates, in particular, changes to the codes in Dictionaries 1, 2, 4, 16, 24, 25,
28-37 will be entered into the dictionaries only after approval by the centers. 4 Also,
alterations of EXFOR dictionary entries that entail changes to data already transmitted cannot
be implemented without specific NRDC approval. A proposed dictionary alteration thatappears to be trivial (inconsequential) will be added to the dictionaries as soon as possible
after receipt. NDS will be the final arbiter for all decisions concerning dictionary codes.
If a center uses a new dictionary code in a data transmission prior to its inclusion in therelevant dictionary, the center must be prepared to correct the entry and retransmit it, if the
new code is not approved.
In general, a dictionary alteration becomes effective upon its transmission to the cooperating
centers.
4

See section on Changes to Scope and Format of EXFOR

August 2004

NRDC Manual Part IV

11

NRDC Protocol

COMMUNICATION BETWEEN CENTERS

Discussion among the cooperating centers on the subjects of data compilation, the EXFOR
system and its further development, EXFOR Manual and Dictionaries, and EXFOR
transmission files, are continued by means of memos, which are called:•

CP Memos: for the communication of proposals, programming details and other generalconsiderations that touch upon the overall aspect of EXFOR. These memos are
distributed to the cooperating centers. Other compiling groups are informed, as needed,by their center of contact. This series of memoranda is numbered as: Memo-CP-n/m.

•

Four-Center Memos: for the communication of details dealing only with neutron data orother Four-Center (non-EXFOR) matters, e.g., CINDA. This series is numbered as:
Memo 4C-n/m.
For both series of memos n is the center identification number, and m the chronologicalmemo number within the center.

Such memos should conform to the following general format:
1. The memo shall be headed by the memo number, the date, originating staff member(s),and subject.
For memos covering more than one topic, all subjects should be listed separately, and thecontents of the memo should be summarized on a covering-page. Each subject should
begin on a new page to facilitate distribution to the appropriate staff at each center foraction. The memo number should appear on each page.
2. Items requiring agreement of the cooperating centers should be noted on the appropriate
page.
3. All proposed changes and additions to the dictionaries, CINDA Manual, EXFOR Systems
Manual, and LEXFOR should contain (where possible) a revised entry in the format of
the appropriate document in addition to the usual documentation.
4. In case of disagreement, the originating center is responsible for collecting the points ofagreement and issuing a final wording in the format of the appropriate document(s).

12

NRDC Manual Part IV

August 2004

NRDC Protocol

MANUALS
The center responsible for the updating of the Manuals is NDS.
The final proposed manual update submitted in a CP-Memo or in the minutes of an NRDC
meeting, is entered into the manuals substantially unchanged. However, the responsible
center is free to introduce editorial changes to maintain a consistency of style. The
responsible center is also responsible for maintaining the internal consistency of the manuals,
which means, e.g., that they must check whether an agreed proposal entails changes (crossreferences, etc.) in other parts of the manuals.
In general, a non-editorial change on a manual page, as compared to its previous version, ismarked by a vertical line in the left-hand margin, and the date of the latest revision to thatpage is given at the bottom of each page.
Where there are different views on matters of minor importance, These may all be included in
LEXFOR in so far as these views are in agreement with the agreed procedures and do notcause ambiguities in the definitions of codes.
Manual updates will be issued as soon as possible.

August 2004

NRDC Manual Part IV

13

NRDC Protocol

EXFOR PROCESSING AND RETRIEVAL CODES

Some EXFOR Processing and Retrieval programs are used by more than one data center.
Each center using one of these programs is invited to contribute suggestions for updates tothe program. The originating center will coordinate all program updates.
If another center wishes to update a code, that center should communicate their intention tothe originating center before any updates are done. Any updates can be done after discussion
with the originating center and upon mutual agreement. The updated code should betransmitted immediately to the originating center.
The originating center retains responsibility for the official version of the code and is free toreject unsanctioned updates. Only the originating center will transmit updated versions to theother centers.

14

NRDC Manual Part IV

August 2004

NRDC Protocol

Appendix A: Compilation Responsibilities

Center
NNDC
NEA-DB
NDS
CJD
CAJAD
CDFE
CNDC
JCPRG
ATOMKIUkrNDC
RFNC

Basic responsibility
Neutron data and CPND from USA and
CanadaNeutron data from NEA countries
Neutron data and CPND from “rest of theworld” (areas not covered otherwise)
Neutron data from former Soviet
Union (except Ukraine)
CPND from former Soviet Union (except
Ukraine)Photonuclear data
Neutron data and CPND from China (entries
submitted through NDS)
CPND from Japan
CPND from Juelich and ATOMKI (entries
submitted through NDS)
Neutron data and CPND from Ukraine(entries submitted through NDS)
CPND on light nuclei, coordinated withother centers

August 2004

NRDC Manual Part IV

Additional compilation

CPND (coordinated by NDS)

CPND from “rest of the world”(coordinated by NDS)

15

NRDC Protocol

Appendix B: Compilation Scope
General categories
Category

Data typeA - Compulsory compilation

All experimental data for incident projectile energy ≤ 1
GeV and projectiles with A ≤ 12, unless listed in Cat. B

B - Voluntary compilation

Neutron capture γ spectra;
Neutron- or charged-particle data with E in > 1GeV;
Heavy ion data for projectiles with A>12;
Vector and tensor polarization data;
Kerma factors (integral data only)

C - Separate transmission

Other data types, as specified in the table below

Separate Transmission Series
CIC *)

CenterData types

NDS

Evaluated neutron data

IJK
V (extinct)*) Center Identification Character

16

NRDC Manual Part IV

August 2004