Memo CP-D/200
20 october 1989
To:

Distribution

From:

O. Schwerer, H.D. Lemme I , and M. Lanwer

Subject:.yp,~(... •..t~( [,--.

Draft of the Conclusions and Actions from theTenth NRDC Meeting, Vienna, 2-4 October 1989

We hope that you had a good travel home from the NRDC meeting.
you very much for attending the meeting and making it successful.

Thank

Please find attached the Draft of the Conclusions and Actions
resulting from the meeting. If you have comments, changes or additions,please transmit them as soon as possible but not later than 20 November
1989. The minutes of the meeting will be published as an INDC report,
including the agenda, list of participants, status reports of thecenters, and the Conclusions and Actions.
The attention of the CINDA centers is drawn to the most urgent
actions related to the clean~p of the CINDA master file in time for thespring deadline of the archi~al issue.

Clearance: J. J.

~ AIL,! _~jI~
V~hrn'GIt

Distribution:
S. Pearlstein, NNDC
N. Tubbs, NEA-DB
V.N. Manokhin, CJD
F.E. Chukreev, CAJAD
A. Hashizume. RIKEN
V. Varlamov, CDFE
H. Chiba, Study GroupCai Dunjiu, IAE-CPNOS:

V. GouloH. Lammer
H.D. Lemmel
M. de Horaes Cunha
K. Okamoto
V. Osorio
J.J. Sclunidt
o. Schwerer
H. Seits
Wang Dahai
3 spare copies

fl3290N

Conclusions and Actions

Action onNOS

NOS

NOS

1.

Publish the report CNOC-89014 as INOC report after
receipt of the final version.

2.

From January 1990, all centres will be able to readmagnetic tapes with 1600 bpi. Therefore, tapes with 800
bpi will no longer be sent from this date.

3.

NOS will give to V. McLane area-3 addresses having
high-energy neutron data activities (14 MeV and up) tobe contacted for contributions to the Fast Neutron DataNewsletter.

4.

The next Technical NRDC Meeting shall take place inVienna. 13-15 November 1990.

5.

The Eleventh NROC Meeting shall take place in Obninskl
Moscow in October 1991. It shall last 5 days and shalloffer opportunities to meet the staff of the three USSR
centers. NOS will approach the USSR authorities.

/.­NOS

11.

Send text of CINDA advertis~~ment and sales conditions tothe other CINDA centers for circulation.

NNOCNEA-OBCJO

12.

Inform their customers of the changes in CTNDA
publication, NEA-DB in particular that the archival issue
will have to be CJD purchased from IAEA.

All, CJO

13.

All centers are invited to inform each other about gaps
in the literature coverage. In particular, CJD is asked
to prepare Cinda entries of the abstracts of USSR
literature that were provided by M. Lanuner. Whereas CJD
covers regularly the more important journals and reportseries, the regular coverage should be extended also tosuch series that have only little Cinda information.

All14.

Reminder to all centers to provide input for the list ofcovered for inclusion in the book CINDA 90.

NNOCNDSCJD

15.

NEA-DB presented the Cinda Manual update of September
1989. All centers are invited to send conunents on it toI. Forest as soon as possible, but not later than end ofNovember 1989.

Lanuner

16.

Some of the changes resulting from conclusions of the1988 NRDC Meeting are not yet included in the Cinda
manual. M. Lanuner will send the text to be included on
the respective manual pages to I. Forest.

NEA- DB

17.

Include on each page of the Cinda Manual the date. of thelast update.

NEA DB

18.

Transmit the new Cinda Manual to the other centers afler
the November deadline.

NEA-DB

19.

Whenever a change has been agreed upon by memo exchange
or at an NRDC meeting, updated manual pages should be
distributed without delay.

20.

(Abstract) remains forbidden for reports.

All

21.

All Cinda centers will correct their own area fileaccording to the conclusions of memo 4C-3/337.

All

22.

the Cinda file of their own area to the other(!enters by end of November 1989.

All

23.

There had been cases where it was not noticed that theproces_?Jng of a lCinda batch was not successful. Allcenters will make sure that their check program issues amessage if the run was not completed correctly.

32~.

Take cure ofa) ilem 4 on page 4 of llu-:1}lo_'!.9-3.L331 concerning smallchanges in the co~nents field.
b) item 5 on page 4 of memo 4C-3/337 concerning pL'oblf~mswith alphanumeric Exfol' accession numbers.
c) item 1. b on pages 2/3 of memo 4C-3/337 concerningsome corrected A-numbers.
NEA-DB25.

For the fields• alphabetic energies,and author, lower case letters are preferable but upper
case is acceptable. NEA-DB will update the Cinda Manual
accordingly.

CJD

26.

Report i f they have difficulties with acceptingcase characters.

All

27.

Include all Exfor index lines before CINDA-C deadline.
Also evaluated data fiels are recommended to be indexe<Seits

28.

Check if all Exfor entries are indexed in Cinda andinform all centers about missing index lines.

All

29.

Check Dr. Manokhin's list of missing Exforin Cinda.

All

30.

Include Exfor index lines for the fission product yield
entries converted from Rider file.

31.

NNDC, NEA-DB and NDS prefer to receive Cinda files
through BITNET.

/,=~~=::_'::C·'_"'_"C'=-.""":;':;' ''-.,''':-.:-.",. =.:;.:;.-c__ Q.!.~ Jt:1CI_@(see also Actions on Fission product Yield Data)
M ;;; Manual update required
UDictionary update required
Schwerer

41.

Check whether the too long unit code MUB/MEV/SR2 is stillin dictionary 25. (Note added after the meeting: it isin the dictionary with the 'obsolete' flag and will bedeleted after checking that it does not occur in anysubentry) .

NDS

42.

Check with CJD staff coming to NDS in November 1989
whether CJD received the Exfor test file prepared forthe 1988 NRDC meeting for comparison of the checkprograms.

NDS

43.

Prepare and distribute new test file for Exfor checkprogramme.

All

44.

Review Exforcompiled by NNDC for missing
data from areas 2,3,4 as soon as transmitted.

M

45.

The BIB keyword
and the data-heading keyword
LVL-FLAG (pages 3/4 of memo CP-D/192) are approved withthe following changes:

Dfirst subfield: isomer extension is allowed butoptional;
second subfield contains on~ of the following three:either E-LVL= ... , with exp licit units MEV or KEV (ifE-LVL=O, the units may be omitted);or LVL-NUMB= ... ,or LVL-FLAG= ... .
The revision of the proposed manual entry is enclosed in
the Appendix.
C.JD

46.

Submit proposal on new coding for partial potential
scattering radius in a CP memo, as was requested in 'lnemo
4C-3/335 regarding entry 40960.

CDFE

47.

Concerning new modifi.ers for some angular distributions,memo CP-D/193 (counter proposal to CP-M/IO) is onlyadopted in principle because CDF'E did not receive memo
CP-D/193 before the meeting. CDFE will study this
proposal in detail and reply in a memo.

rD

48.

Send a memo on the conference code 86BIRMIN.

49.

V. McLane confirmed that the journal code HI stands forHyperfine Interactions (Switzerland).

- sDM50.

A din}Qns.i<2.!Lc-29....e._~ (dict.ionari.es 25 + 36) is inLt'ouucedfor quantilies with undefined dimension (e.g. quantities
which occur only as relative daLa). Manual updaLe inChapter 7.

D51.

Instead of Lhe code ,DA/PRE proposed in memo CP-M/I0 thecode PRE,DA,FF is approved for dictionary 36 with theexpansion "ang.disLof primary fission fragments".

DH

52.

BRA (Bremsstrahlung average) is approved as general
purpose modifier for dict. 34. - Lexfor to be updated.

CDFE

53.

Check the code ,DA/DE"LEG/RS proposed in memo CP-H/I0and provide other centers with correct expansion fordict.36 and, if necessary, further explanations (Lexforentry) for Legendre coefficients for double-differential

RIKEN

54.

Memo CP-C/182 (allow heavie~articles in REACTION SF7)
isapproved; the relevant entries w:ill be retransmitted byRIKEN.

55.

Centres are reminded to try to avoid/eliminate
information in EXFOR entries, as pointed out in memo
CP-CI183.

M

56.

The flag in col.66 in dictionary 16 (STATUS) is approved(memo CP-C/184).

M

57.

Centres are reminded to avoid multiple representationsof independent variables. The updated manual wording
proposed in memo CP-C/185 is approved.

NNDC

58.

is added to the list of headings which may berepeated (Manual page 5.4).

Lammer59.

Check the reference for which the new column headings
ELEMl,2,~ MASS 1,2,3, ISOMERl,2 have been used.
Approval of these headings (proposed in memo CP-C/188)
is postponed.

DH

60.

The BIB keyword STATUS is now obligatory (the addition"when relevant" is cancelled).

DH

61.

New REACTION codes for thick target yields as proposed inmemo CP-C/178 are approved with the modification that"case 2" (on p.2 of memo) is coded with SF6=TTT. nomodifier.

Chukreev

62.

write nl0mo on conversion factors for thick target yields.

Chukreev

63.

write memo on data for production of y+x rays.
possibly suggesting a new code for REACTION SF4 (thisconcenlS e.g. entry A0388).

HM

.

6 ­D

6~.

DifferenLial thick target yields as givon in ~nt~y n0388
are coded with=1'T'l:'{f.!P... (dimension TTDA in dicl. 36).

NDS

65.

Do not send corrected versions of CJD, CAJaD or CD~E
TRANJ? tape§. any more to NNDC.

CAJaD

66.

Provide examples of data involving shortlivi~omers
which cannot be coded sat.1 sfactorily using the keywords
DECAY-DATA, EN-SEC and LEVEL-PROP.

NDS

67.

Send latest versions of Exfor check program, and ofindexing program if revised since 1985, to Dr. Chiba.

68.

Memo CP-D/180 on REACTION branch codes IND and CUM(provisionally approved at the 1988 NRDC meeting) isapproved.

69.

Enter in dictionary 31 that codes IND and CUM are to beused only in eombination with the process codes F and X,
and that IND is to be used only in cases where CUM eanalso occur.

NDSD

NOS

7J.

NOS wi 11 send a formal request to the appt'opriate US
authot'ity fot' release of the last version ofPhotonuclear Data j'<'Ue. It is suggested to contact
Livermore with copy to S. Whetstone.

Tubbs

72.

N. Tubbs will once more informally contact Prof. Bergere(Saclay) to send his pholonuclear data in digital form
to COFE.

COFE

73.

Provide NOS with details of possibleof a CDFE
staff
ll1ember to NNDC for work on US photonuclear data.

NOS

74.

Write formal letter to arrange such a ~~~ under IAEA
auspices.

NOS

75.

Inform CDFE of number of copies needed of future issuesof CDFE's Photonuclear Data Bulletin.

NOS

76.

Verify that CNDC (Beijing) has received the complete
photonuclear Exfor file.

NOS

77.

Assign range of Exfor accession numbers for' photonuclear
data compiled in Nanking.

VarlamovCai

78.

Establish direct contact between
group
about futur'e workplan. The data exchange will be routed
through CNDC.

NNOC

79.

Investigate about suitable US participants in a fut.ure
techn.lcal meeting on evaJuation of photonucleur dat_a lo
be hosted by CDFE in 1992 or later.

Varlamov80.

Write an informal technical letter to NOS about thisfutul"p. meeting and its possible participanls fromnon-USSR countries.

NOS

81.

write to USSR authorities in support of an inteI.'national
photonuclear data meet inK to be hosted by CDI:'E.

NNOC

Chlba82.

Send index of references comp i.led in ~RDF to Dr.
Chukreev.

NDS

83.

Contact Roger Whi te (Livermor~) about his pos)';ible
participation in the compilation network.

NOS

84.

Send INDG report on "Status of monitor reactions forradioisotope production" to other centres when completed.

CAJaD

85.

Send the evaluatlon report of the reactions C-12(p,pn),AI-27(p,3pn), AI-27(p,3p3n), C-12(p,3p3n) and Cu-63(p,n)
to NDS. (Note added after the meeting: abstract of thiswork with numerical data was published at the 88BAKU
conference and is available. NDS will appreciatereceiving the full report from CAJaD).

NDS

86.

start INDG-report series on medical radioisotope
production, as soon as such reports have been received
from CAJaD and RIKEN.

All

87.

CPND Exfor data are exchanged direclli between thecentres.

Hashlzume

88.

Send RJKEN data onNOS

89.

Send form~lett.g~ to CAJaD asking for cooperation wiLhother centres, in particular RIKEN (wiLh copy to Dr.
Hashizume) .

Hashizume

90.

Send list of reactions covered in his future publication
on MRL"p.£..oductioD. daLa to NDS.

NDS

91.

Send INDC report numbe!: for this publ icatlon to Dr.
Hashizume.

Hashizume

92.

Report on production of J -123 and Xe-).23 will be
supplemented by data for Cs-1.21 and sent to NDS foe
publication as INDC report.

to CAJaD.

<)

NNDC

95.

Inv~~sti gate

whether NNDC can ine lude a PC -,!~rsLo.!.! intheir END!-'/B utili~~des.

NDS

96.

Find out whether anywhere else a PC~p-rsi0.!l of the
ENDF/B utjlity~odes of NNDC exists.

NDS

97.

Check i f the ENDF/B-6 "illustration" file (n and p onFe-56) was received at NDS and, if necessary, request it
from NNDC.

Pearlstein

98.

Prepare a memo on an example of evaluated CPND in
ENDF IB-6 format.

·109Q!.!.!.~~l_~Ums_ ?..!l~'!....§~J- 1.Q!12 _~)!lin(~ ll!tJ iI!1l..

NDSNDS

on r'PY has be~~niniti.atedby convening a Consultants' Meeting (CM) on the"Compi] ation and EvaluaHon of Fission Yield NuclearData", 27-29 September 1989. CRP participants have beenasked to review the codes for FPY and to send their­cOTI1ments, proposals for new codes and information theywant to be included in FPY RXl"OR entr-ies to M. Lammer­
before the end of 1989. Soon after-, M. Lawl.ler wi 11summarize the matp.rial received together with proposals
for revisions or additions of codes and coding r-ules ina CP-memo,
102. M. Lammer will sununarize theandrecommendations about the compi.lation of FPY" in EXl"OR,
which were already issued by CM participants during
their meeting, and the resulting acti.ons in memo
CP-D/199.

Neutr-onCenters103. To send out

author,proof~ for all new EXFOR entr-ies
containing FPY" data and, at the same time, ask theauthor-s about exper-imental details not included in thepublication but mentioned in CP-D/199 and the memo
resulting from action 101.

104. The following new COd~R fnr dietionary 34 have been

adopted:FSTEPI

Fast reactor neutron spectrum
Epithermal neutron spectrumwith more infnt'maLion under INC-SPEC.
NNDC

105. To write a Lexfo£ entry on this.

NNDC

106. Submit new method codes (see CP-D/199) for FPY in aCP-memo.
Neutron107. Comments by evaluators about FPY experiments (method,Centersdataand possible erL'ors found) should be included in theCOLTp.sponding RXFOR entries.

Neutr-onCenter's

108. EXl"OR comp tIers of FPY" may propose further new codes, i fneeded (e.g, for methods) in a CP-n1emo, but should not
use them prior to appr·oval.
109. The cle.anup of old FPY data is coming near tocompletion. All data from Rider's file have been
converted to a ser-ies of quasi-EXFOR entries sorted byar-ea. Most of them have been distl'ibuted to the othercenter-sox(1)This keyword is used to spt~cify level-energy, spin and parity ofexcited levels, as supplemontary information to energy levels
specified in the COMI{ON or DATA section under the column-headings
R-LVL or LVL-NUMB.

(2) Use of this keyword is opt.ional.
be given

Infor'malion under this keyword mayin coded form with or without free text following,or in free text only.
(3) The format of the coded infurmaLion is illustrated by the following
example:LEVgL-PROP (82-PB-206, E-LVL=O. ,SPIN=O. ,PARITY=+l. ,E-LVL=1.34MEV,SPIN=3.,PARITY=+1.)(82-PB-207,LVL-NUMB=2.,SPIN=1.5,PARITY=-1)(82-PB-208,LVL-FLAG=1.,PARITY=+1.)
The nuclide is coded in the form Z-S-AX as shown on page 8.3, with
the isomer extension being optional even when an isomeric stateexists.
The second subfield contains
either the level ener£Y with explicit units KEV or MEV
E-LVL=O. the units may be omitted);(ifLVL-NUMB should be used only when the level-energy is not known.
LVL-FLAG is used to link a LEVEL-PH.OP entry to a line in the DATA
table; the flag is repeated in the DATA table under the colunm
hending LVL-FLAG Clnd the unit NO-DIM. The values of E-LVL andLVL-NUMB have to be repeated in the COMMON or DATA sectIon under thecolumn headings E-LVL or LVL-NUMB.
The third subfield contains the spiT! as :indicated in the example..
The fourth subfield contains the parity as indicated in the example.
A range of spin or parity values can be indicated with a slash, e.g.
SPIN=2./3.
The string of subfIelds 2 to 4 may be repeated as indicated in theexample.
rThe separator between tne suhfields is a comma. The apin or parity
subfield may be omitted in ~hich (~ase the separating comma may begiven or omitted.
(4) If level--properties for more than one nuclide are given, the coded
info~lation for each nuclide starts in a separate record in col. 12.