Atomic Data and Nuclear Data Tables presents compilations of experimental and theoretical information in atomic physics, nuclear
physics, and closely related fields. The journal is devoted to the publication of tables and graphs of general usefulness to researchers
in both basic and applied areas. The cumulative subject index, which appears in the last issue of each year, is indicative of the types
of subject and treatment that have been considered appropriate.
Three copies of the manuscript, containing introductory material
in English (typed double-spaced) and the tables and graphs, with relevant references, should be sent to the editor,
Dr. David R.
Schultz Oak Ridge National Laboratory Bethel Valley Road Building 6010, Mail Stop 6372 Oak Ridge, TN 37831, USA
or
to an associate editor, who will forward it to the editors with comments. (See the Editorial Board for the list of associate editors
and their addresses.) In the case of very extensive tables or graphs, authors may wish to first send representative sample pages to inquire
with the editor about the suitability of the subject matter and whether sample pages would suffice for two of the three copies to be
sent. At least one submitted copy must contain the complete set of tables or graphs so that the manuscript may be critically reviewed
for both content and presentation. Review criteria may include, in addition to the scientific merit and quality of the work, the utility
value of the presented material. Upon acceptance, authors will be asked to prepare the final manuscript, including camera-ready tables
and graphs, in two complete printed copies, and provide as well the electronic versions (see below for discussion of electronic files
and instructions for preparing manuscripts in LATEX). Proofs of the articles will be sent to authors. Return of proofs within 2 days
is expected.
There is no page charge to authors. However, to contain costs, authors are required to prepare their tables and graphs
as camera-ready copy (see below).
Authors submitting a manuscript do so on the understanding that if it is accepted for publication,
copyright in the article, including the right to reproduce the article in all forms and media, shall be assigned exclusively to the publisher.
The Copyright Transfer Agreement should be signed by the appropriate person(s).
INTRODUCTORY MATERIAL
The introductory
material, which will be typeset, should be organized as follows:
• Abstract • Table of Contents • Introduction
• Explanation of Tables (or Graphs) • Examples of Use of Tables (or Graphs) in cases where such examples will clarify
the uses to which the data may be put
The Introduction should contain, where applicable,
• Description of scope
(with mention of cutoff date for data compilations) • Historical review and mathematical development • Description
of policies with regard to standards adopted treatment of errors, etc. • Information regarding associated computer files (see
below) • Acknowledgments • References for the introductory material.
Extensive listings of references for the main
tables or graphs should themselves be listed in camera-ready form if they are not typeset using the journal's LATEX package adnd.
The Explanation of Tables (or Graphs) should be arranged in a tabular style; that is, each symbol or term that appears
in the tables (or graphs) should be listed in the left-hand column, in the order in which it appears, and its explanation just opposite
in the right-hand column. The Explanation of graphs should define the abscissa, ordinate, legend, plotted symbols, etc. The
explanation can refer to an equation or to a section of the Introduction, if appropriate.
All manuscripts are required to contain
a tabular Explanation of Tables (or Graphs).
Authors should generally follow the style conventions of the Physical Review
for equations, abbreviations, references, etc.
MAIN TABLES OR GRAPH COLLECTIONS
It is expected that the main part of all
papers will consist of camera-ready tables and/or graphical drawings. These should be prepared so that, with photoreduction where necessary,
they fit economically on each page. Allowing room for margins, page number, running captions, etc., the actual printing space available
for the camera-ready tables or drawings is about 6.8 x 8.5 inches (17 x 21.5 cm).
The standard format is for all tables and drawings
to be presented in the same orientation as the manuscript text. Materials that require turning the page sideways to read will be accepted
only in very unusual circumstances.
Captions for these data tables and graphs should be listed in the Table of Contents.
The captions displayed above the individual camera-ready tables or graphs will be typeset by the publisher, unless they are included
as part of the author-prepared page. Authors wishing to include captions should repeat these in full on each page, but should count the
space the captions occupy as being outside the 6.8 x 8.5 inches available for the data tables and graphs themselves.
Tables
Tables can be planned for full-page-width or partial-page-width presentation. A special case of the latter is the side-by-side display
of two successive arrays where, if necessary, the page can be composed by the publisher from two narrow arrays of the proper dimensions.
Headings labeling the data columns form part of the camera-ready material and should be repeated atop each array on each page.
The
printed tables look best when the size of the individual characters approximately matches that of the typeset text, which is in 10-point
font. But because numerals resemble uppercase letters rather than lowercase letters, the overall appearance of numerical tabulations
tends to be optimum if the numbers are in 9- or 8-point and the headings in 10- or 9-point font. We therefore recommend the use of a
9-point font for numerical tables in general, and we advise against the use of the 12-point font.
Graphs
Graphs should
be planned for single-column or two-column presentation, depending on the density of the data displayed. If in doubt about legibility,
authors should make trial photoreductions or they should consult the editors. Lettering should be no smaller than 3/64 inch (1.2 mm)
in size, equivalent to a 9-point font, after reduction. Sets of graphs to be used as camera-ready copy should have all labels (including
figure numbers if these are desirable), reference keys, and comments within the drawing itself. Captions describing each individual graph
should be avoided, and the information contained in such captions (for example, the element name) should instead be incorporated within
the legend of the particular graph.
ELECTRONIC FILES OF MANUSCRIPT MATERIAL
When a paper is accepted for publication, the
editors will request that electronic files of the manuscript material, particularly the files for the main data tables and graphs, be
forwarded for use in the publishing process. (The editors and Elsevier will not refuse publication of an article for which electronic
files cannot be made available.)
The advantages of using electronic versions of the data tables over camera-ready print versions
are threefold: First, the tables created using properly prepared electronic files are of better quality than those prepared from camera-ready
copy in both the printed version and the online version of the article. Second, the portable document format (pdf) files for the online
article created using electronic versions of the tables are smaller and therefore more quickly downloaded by the viewer. Finally, one
can cut and paste data from the pdf files of tables created using electronic files into their own applications, an obvious added benefit.
File formats currently usable are as follows: For tables, the publisher is able to use TEX or LATEX files, tab-delimited or comma-delimited
(where possible, comma-quote-delimited) ASCII, and common word processing and spreadsheet programs (MSWord Table, Excel, Lotus 123, QuattroPro,
etc.) in the typesetting process. For graphs, the same common spreadsheet files are acceptable. TEX or LATEX and Word or WordPerfect
files are usable for typesetting the introductory text. Please see the instructions on the journal home page (http://www.elsevier.com/locate/adt).
It is the author's responsibility to ensure that the camera-ready and electronic versions of the tables and graphs
match exactly. If a discrepancy between the two is found, the camera-ready copies will be used. Electronic files of the data tables and
graphs must be accompanied by a clear description of the contents of each file and identification of the software used to prepare the
file, provided in hard copy (downloadable form available on the journal home page) and as an ASCII "readme.txt" file on each computer
disk.
If an electronic file is provided but not used by the publisher, the camera-ready copy will be used instead and image files
of the tables or graphs will be mounted on ScienceDirect in the published electronic version of the article. The publisher does not guarantee
the use of electronic files in the typesetting process.
As an extension of the published print and electronic versions of the article,
the publisher will also make provisions to mount the associated computer-readable data on ScienceDirect and on the journal home page
(http://www.elsevier.com/locate/adt). In general, only data files
that correspond exactly to the published version will be mounted; acceptable supplementary material (see later discussion) will usually
be restricted to data sets of which the published tables or graphs are illustrative subsets, and must be approved by the editors.
SUPPLEMENTARY
DATA MATERIAL
Supplementary data material is any material that constitutes an extension of the published print and electronic
versions of an article; thus, an article should stand alone in its published form without the supplementary material. Supplementary data
material may be any electronic file that complements published material, for example, computer-readable data files, graphics, videos,
or extensive tables. All supplementary data material must be approved by the editors, and it is their responsibility to ensure that the
file format is applicable and usable for the community of potential users. The availability of supplementary data material will be indicated
in the printed and electronic versions of the article.
The publisher will mount supplementary
data material exactly as it is received from the editor. However, the publisher cannot accept compiled executable programs of any kind.
Authors wishing to make available executables or proprietary viewing programs must do so on their own www or ftp sites. Certain file
types, such as Excel or Word files, sometimes contain macros or viruses. As routine procedure, the publisher will require that any macros
in such files be removed before submission; if macros are necessary to the material, authors should discuss options with the editors.
The publisher and the editors do not bear any liability for the usability or correctness of supplementary data material.
Explanatory file to accompany supplementary material submission
With each
article that includes supplementary material, authors MUST include an "explanatory" file with the following specifications:
The file
must be a text-only file (.txt), including only ASCII characters, or rich-text format file (.rtf) and should be named explan.txt (or
explan.rtf); for security reasons, files should not contain the phrase "readme." In a rich-text format file, the only allowable stylistic
elements are bold and/or italic text (for emphasis), super- and/or subscript text, and standard mathematical symbols (including Greek
letters). Do not use underlined text and do not use TEX coding in the "explanatory" file.
This file must include: (1) A paragraph
of text explaining what the supplementary material consists of (a caption). (2) A description of any requirements that may be necessary
for viewing the file (e.g., Acrobat Reader, RealVideo). (3) A list of all supplementary files that are included, with a description
of the contents and the full name of each file. Please do not include the size of each file.
Electronic files of supplementary data material can be transmitted via FTP, e-mail, or computer disk.
FTP
The file transfer protocol (FTP) is used to transfer files from your computer to the publisher's (upload). Because FTP is fast, reliable,
and convenient, the publisher considers it the preferred method for authors to transmit their electronic files. A folder for this journal
has been set up at the publisher's FTP site. Authors can access this folder by logging on to the FTP server at ftp.elsevier.com with
username anon and password essd4acc.
Important: Please choose unique, descriptive file names that do not include spaces or special
characters. They must contain an extension (e.g., ".txt"). File names should include the manuscript number or production number (if available).
Transmission of electronic files is quicker and more reliable if the files are first compressed or concatenated. The publisher can
accept BinHex, tar files, and shar files. Files processed using the following compression programs are also acceptable: PK-Zip (WinZip,
etc.), StuffIt!, Z (Unix compress), and GZ (GnuZip). All other compression schemes are unacceptable. All files that include binary information,
including all files using compression schemes, must use the binary (bin) FTP protocol for uploading or they will be altered during transmission
and become unusable.
If you have not created a single archive file including all materials and you plan to transmit multiple files,
you are strongly advised to create a new folder, appropriately named in accordance with the recommendations above.
Upon successful
completion of an FTP transmission, authors must send an e-mail message
to the journal as notification that the files have been posted.
The Atomic Data and Nuclear Data Tables e-mail address is adndt@elsevier.com.
E-Mail
Manuscript
files can be transmitted via e-mail if the total file size of all attached files does not exceed 2 megabytes. Address the e-mail to the
journal and supply the information requested for FTP submission.
Storage Media
Although the publisher prefers to receive
files via the Internet, the publisher also accepts transmissions on 3 1/2-inch high-density (not double-density) disks. Note on the
disk label the operating system, software, file format, and version numbers used to create the disk: e.g., Win95 – Word 97; Windows
98 – WordPerfect 9; MacOS 8.6 – Word 98. If you submit your electronic materials on one of these media, please use special
packaging materials and shipping via a reputable express courier service.
Manuscripts transmitted on disk may also be compressed
or concatenated as described above. Transmitted media will not be returned to the author.
GUIDELINES FOR PREPARING A LATEX COMPUSCRIPT
It has become increasingly customary for authors to type and compose their manuscripts
for various journals using some text-processing
system. Systems that are quite popular are TEX and LATEX. Packages (or styles) for the latter have been created and used succesfully
for several years at Elsevier and elsewhere.1 The Publisher of Atomic Data and Nuclear Data Tables has also encouraged
authors to use LATEX in formatting their manuscripts. However, there has been a serious limitation because a LATEX package, conforming
to the special requirements of this journal, has not been available until now. To remove this limitation and to assist authors in preparing
their papers for articles in Atomic Data and Nuclear Data Tables, we have written adnd, a LATEX document package. This package
is designed to be used exclusively in combination with the generic document class elsart of Elsevier. The version of elsart should be
2001/01/05, 2.18, or later.
We give in the following a description of the adnd document style and of its use in preparing manuscripts.
We have tried to make this guide complete enough to provide authors all the information they need when submitting compuscripts to Atomic
Data and Nuclear Data Tables. However, a basic working knowledge of the LATEX document preparation system is assumed. The essentials
of LATEX are given in a concise form in [1]. For more general information about LATEX, see the manual by Lamport [2]. For elsart document
class, see the relevant documentation at http://www.elsevier.com/latex.
Note that although there exists a LATEX 2.09
version of the elsart class, the package adnd has been designed to be used with LATEX2e only. Thus all references to LATEX in the following
are to be interpreted to mean LATEX2e.
1The RevTEX package of the American Physical Society is perhaps the most widely
used.
Proper formatting of manuscripts for Atomic Data and Nuclear Data Tables is
achieved
by using the LATEX class elsart of Elsevier, the current package adnd.sty,
and the file tmpadnd.tex as a template. Furthermore, because
the articles in this journal usually contain long multipage tables, the current package relies heavily on the longtable.sty LATEX package
(1998/05/13, v4.09, or later). The latter is included in most LATEX distributions but, if missing, can be obtained from the CTAN archive.2
The documentclass elsart, with which the article can be prepared and printed, is compatible with the standard document styles of
LATEX, except for the specification of the front matter, i.e., the title, author, addresses, and abstract. Some commands and environments
of the elsart class have been redefined in the adnd package. It has also been necessary to define some new commands.
In the following
sections we describe the differences between normal LATEX usage and the usage of the elsart class and adnd package. Also, we summarize
some of the important aspects of coding a compuscript with LATEX.
There is only one option for elsart which is usually necessary. It is called doublespacing or reviewcopy producing
double line spacing, required for copies submitted for review. The exact format is \documentclass[doublespacing]{elsart} or \documentclass[reviewcopy]{elsart}.
There are no options for the adnd package. It is suffcient to write \usepackage{adnd} in the preamble.
The
elsart document class has a separate frontmatter environment for the title, authors, addresses, abstract, and keywords. Within the frontmatter
environment, you should specify the title, names and addresses of the authors, followed by the abstract. Keyword abstract is not used
for Atomic Data and Nuclear Data Tables. Note that the instruction \maketitle has become obsolete.
• \title: As in
standard LATEX, e.g., \title{Model}. • \author: Different from standard LATEX, the \author command contains only one author
and no address. Multiple authors go into multiple \author commands, separated from each other by commas. The address goes into a separate
\address command. Example: \author{D. E. Knuth}. • \address: The address goes here, e.g., \address{CERN, Geneva}. •
\thanks and \thanksref: These provide footnotes to the title, authors, and addresses. The \thanksref command takes a label: \thanksref{label}
to relate it to the \thanks command with the same label: \thanks[label]. There can be several references to a single \thanks command.
Example: \title{Model\thanksref{titlefn}} and \thanks[titlefn]{Supported by grants.} • \corauth and \corauthref: These provide
footnotes to mark the corresponding author and the correspondence address. They are used in the same manner as \thanks and \thanksref.
Example: author{A. Name\corauthref{cor}} and corauth[cor]{Corresponding author. Address: ... .} • \ead: This command should
be used for the e-mail address or the URL of the author. Note that it refers to the current author, i.e., the author last mentioned before
the command. When it holds a URL, this should be indicated by setting the optional argument to url. Example: \ead{pertti.tikkanen@helsinki.fi}
and \ead[url]{www.elsevier.com/locate/latex}.
The authors and addresses can be combined in one of two ways:
• The simplest
way is to list the authors of one address, followed by the address, and so on for all addresses. • The other way first lists
all authors, and then all addresses. The authors and addresses are related to each other by labels: \author[label1]{Name1} corresponds
to
\address[label1]{Address1}. Example:
\author[ORNL]{D. Schultz}, \author[Helsinki]{P. O. Tikkanen} \address[ORNL]{Oak
Ridge National Laboratory, USA} \address[Helsinki]{University of Helsinki, Finland}.
See the examples that come with the adnd
package. If the frontmatter is put in an included file, that file should contain the whole frontmatter environment, including its \begin
and \end commands. Otherwise, the labels of the frontmatter will remain undefined.
The abstract is produced by
using the \abstract environment. The abstract should be
self-contained. Therefore, do not refer to the list of references. Instead, if
necessary, quote the reference in full as follows: B. White and Y. Redhead [NewA, 1, 17 (1996)].
The manuscripts
submitted to Atomic Data and Nuclear Data Tables are all required to have a Contents. It should include the caption
texts of the sections of the introductory material, which is produced by the command \tableofcontents. The Contents should not
include the lists of figures or tables that are part of the introductory material, but the captions of the data graphs and data tables
must be listed. Therefore, two new commands have been defined for these, \listofDfigures and \listofDtables, respectively. Do not use
the \listoffigures and \listoftables commands. In short, a properly formatted Contents is produced automatically with the three
commands \tableofcontents \listofDfigures \listofDtables, provided that the usual sectioning and caption commands of
LATEX are used correctly.
For unnumbered sections such as Explanation of Graphs, entries to the Contents can be
added using the command \addcontentsline, for example:
\addcontentsline{toc}{section}{\uppercase{Explanation of Graphs}} Sometimes it
is necessary to add extra entries, not to the .toc (Table-Of-Contents) file, but
either to the .ldf (List-of-Data-Figures)
or to the .ldt (List-of-Data-Tables) file. In such cases, the argument toc in the above example should be replaced
by ldf or ldt, respectively. Issuing the command \addcontentsline (or \addtocontents) at an appropriate place is preferable
to
directly editing the .toc, .ldf, or .ldt file.
Text should be typed as usual. Type hyphens
as in "Wigner-Eckart theorem," "Clebsch-
Gordan coeffcients," as -; for numeric ranges, for example, pages 27–31, use the en
dash, --; and use the longest, the em dash, ---, as punctuation---it is normally called the dash. A fourth type
of dash is the minus sign -, which is entered in math mode as $-$.
Although the LATEX 2.09 commands \bf, \em, \it,
\rm, and \sc are still functional, it is recommended that the following (LATEX2e) commands \textbf, \emph, \textit, \textrm, and \textsc
be used instead. For example, emphasized text is obtained with the command \emph. In most cases this will result in italic text representing
emphasis. When \emph is used, italic text need not be terminated by an italic correction; i.e., heavy quarks is produced by
\emph{heavyquarks}.
Extra or exceptional hyphenations are added to TEX's list of abbreviated words by means of the command \hyphenation,
which should be placed in the preamble of the document. An example: \hyphenation{caus-al min-i-mi-za-tion pro-ven}.
Introduce macros
(with care, see section on private definitions below) for notations and abbreviations that occur more than once, for example, "e.g."
and "i.e." This procedure facilitates changes in notation. Because macros for abbreviations are often parameterless macros, you should
be aware of TEX's behavior with regard to spaces following a parameterless macro. An instruction without parameters should be defined
and used as \newcommand{\ie}{i.e.,} ... ...extra particles, \ie{} particles . . . extra particles, i.e., particles
It is recommended
that LATEX's \newcommand and \newenvironment be used instead of TEX's \def, \gdef, etc.
Sectional units are
obtained in the usual way, i.e., with the LATEX instructions \section, \subsection, \subsubsection, and \paragraph.
A new environment
\ack has been added to produce an Acknowledgments section, which should be placed at the end of the introductory material, before
the references.
A new command \noteinproof for Note added in proof has been defined. This command is issued after \ack,
just before the references.
Lists of items are produced with the usual itemize and enumerate environments. The
itemize
environment is used for unnumbered lists and the enumerate environment for numbered lists. Even if the layout of these lists is not precisely
what you would like, we prefer that lists be coded this way instead of by hand. This enables the document style for the Atomic Data
and Nuclear Data Tables to determine the list layout.
In electronic publications articles are internally
hyperlinked. Hyperlinks can be generated effectively only from proper cross-references in the article.
For example, the words "Fig. 1"
will never be more than simple text, whereas the proper crossreference \ref{mapfigure} may be turned into a hyperlink to the figure itself.
In the same way, the words "Ref. [1]" will fail to turn into a hyperlink; the proper cross-reference is \cite{Gea97}. Use \label and
\ref for cross-references to equations, figures, tables, sections, subsections, etc., and \pageref for cross-reference to a numbered
page.
For references to the literature list at the end of the article, see below.
Every numbered part to which one wants to refer
should be labeled with the instruction
\label. For example, consider \begin{equation} e^{\mathrm{i}\pi} + 1 = 0 \label{eq:euler}
\end{equation}
With the instruction \ref or \eqnref (the latter generates parentheses automatically) one can refer to a numbered
part that has been labeled: ..., see also Eq. (\ref{eq:euler}) The \label instruction should be typed • immediately
after (or one line below) but not inside the argument of a number-generating instruction such as \section or \caption, e.g., \caption{Cross
section} \label{fig:crosssec} • roughly in the position where the number appears, in environments such as equation, e.g., \begin{equation}
e^{\mathrm{i}\pi} + 1 = 0 \label{eq:euler} \end{equation}
For in-line formulas
use \(...\) or $...$. Avoid built-up constructions, for example, fractions and matrices, in in-line formulas.
For unnumbered
displayed one-line formulas use the displaymath environment or the shorthand notation \[: : : \]. For numbered displayed one-line formulas
use the equation environment. Do not use $$...$$, but only the LATEX environments, so that the document
style determines the formula layout.
Except for equations in appendixes, the equation numbers in Atomic Data and Nuclear Data
Tables do not include the section numbers. For example, the equations p(t, x, y) = (2πt)-m/2exp(-|x
- y|2/2t) (1) and were produced, respectively, with
When referring to the equations, put the command \ref
in parentheses (or use the command \eqnref) to obtain the correct format for Atomic Data and Nuclear Data Tables, as in Eqs.
(1) and (2), produced by (\ref{1.1}) and \eqnref{eq.a1}, respectively.
In some cases it is necessary to have subnumbers in the equations
and also be able to refer both to the subequations and to the equation as a whole. This can be achieved by using the subequations environment.
For this environment to work, it is necessary to load the amsmath package in the preamble, by putting \usepackage{amsmath} before \begin{document}.
For example, the equations πγ =(-1)L for EL transitions, (3a) and πγ
=(-1)L+1 for ML transitions (3b) were produced by the following commands:
This entire group of equations (3) is referred to by using \eqnref{eq:sub}. For subequation (3b), use \eqnref{eq:sub2}.
Many
physics authors require more mathematical symbols than those provided in standard
LATEX. A useful package for additional symbols is the
amssymb package, developed by the American Mathematical Society. This package includes such often used symbols as \lesssim for less than
or similar to, \gtrsim for greater than or similar to, and \hbar for h(stroke). Note that your TEX system should have the msam and msbm
fonts installed. If you need only a few symbols, such as \Box for a box, you might try the package latexsym. Vectors are preferably coded
as \vec{a} instead of \bf{a} or \pol{a}. Nuclides, e.g., 208Pb, are produced by \nuc{208}{Pb}.
Superscripts and subscripts
that are words or abbreviations, as in σlow, should be typed as roman letters; this is done as follows:
\( \sigma_{\mathrm{low}}
\) σlow instead of \( \sigma_{low} \) σlow
The most common symbols that are conventionally
typeset in a roman typeface, for example, units, are listed below. • The base of the natural logarithm, for example, as in ex, $\mathrm{e}^x$. In elsart, a shorthand command, \e, can also be used. • i when used as imaginary unit, e.g. a
+ b i or eiφ, etc. The Euler equation,
eiπ + 1 = 0, (4)
which was used as an example earlier,
can therefore also be typed as \begin{equation} \mathrm{e}^{\mathrm{i}\pi} + 1 = 0 \label{eq:euler} \end{equation}
•
Elementary functions, e.g., exp, sin, cos, and tan. LATEX provides macros \exp, \sin, \cos, and \tan for these and similar functions.
These macros also give the proper spacing in mathematical formulas. • The differential operators, e.g., dx, and the operators
Im and Re for the imaginary and real parts of complex numbers, respectively. The differential operator "d" can also be coded as $\d$
in elsart. • Groups, for example, SU(2) and SU(3). • Labels for atomic orbitals and atomic shells, for example, 4s,
4p, K, L. • Greek letters when used as a unit, e.g., Ω for ohm. • Units in general, e.g., cm, Å, and b (for
barn). • Subscripts and superscripts that are used as abbreviations, as in TC (Curie temperature), Tc
(critical temperature), and C3v (identifier of space group). • Operator or function names or their abbreviatons,
e.g., Ker, Im, Hom.
The list of literature references can be produced in two mutually exclusive ways,
by using • the environment thebibliography, or • BibTEX
The thebibliography environment is the preferred way, but
if the BibTEX system is familiar to the authors, they can use it also. An appropriate bibliography style for the latter is adnd.bst.
BibTEX is an auxiliary program to LATEX that automatically constructs a bibliography by searching one or more bibliographic databases.
To this end, the command
\bibliography{dbase1,dbase2,...} must be issued at that point where the References is to appear.
We recommend that the authors collect the references in one BibTEX file (.bib) and include it in their submission of electronic
material.
It is even more important to submit also the .bbl file which is generated by the BibTEX program.
Irrespective of the way References
is created, each reference is a \bibitem entry; each \bibitem is identified by a key, by which it can be cited in the text:
\bibitem{ESG96} is cited as \cite{ESG96}. Multiple citation keys should be separated by commas (without spaces!). Consecutive numbers
are converted automatically to numeric ranges.
A compuscript can be submitted as one or more files. If there
is more than one file, one of them should be a root file that is run through LATEX. The root file inputs the files that constitute the
entire article by means of \input or \include. We recommend, especially for large articles, separate files for (i) Introductory Material
including Explanation of Graphs and Figures, (ii) Data Graphs or Figures, and (iii) Data Tables. It is a good
practice to have a separate file also for an extensive list of literature references for the data graphs or tables.
Private definitions should be placed in the preamble of the article, and not at any other place in the document. Such private definitions,
i.e., definitions made using the commands \newcommand, \renewcommand, \newenvironment, or \renewenvironment, should be used with great
care.
Sensible and restricted use of private definitions is encouraged. Large macro packages should be avoided. Definitions that
are not used in the article should be omitted. Do not change existing environments, commands, and other standard parts of LATEX. Definitions
that are merely abbreviations for keystrokes, such as \bt for \begin{theorem}, should be avoided (use the facilities of your editor program
to minimize keystrokes). A short description of the various definitions, in the form of TEX comment lines, is appreciated. Deviation
from these rules may cause inaccuracies in the article or a delay in publication, or may even result in the LATEX file being discarded
altogether, requiring the article to be typeset conventionally.
To facilitate processing of your article, please
give easily identifiable structure to the various parts of the text by making use of the usual LATEX commands or by your own commands
defined in the preamble, rather than by using explicit layout commands, such as \hspace, \vspace, \large, \centering. Also, do not redefine
the page layout parameters.
Do not be concerned with bad line breaks, page breaks, or underfull or overfull boxes. These issues will
be resolved during final production. Restrict manual formatting to equations. It is preferable that you as the author set the line breaks
in them, rather than having undesirable breaks added during the production process.
Use the LATEX picture
commands or other LATEX drawing programs only for simple diagrams, because the quality is usually not acceptable for final typesetting.
Figures should be supplied as separate files, in EPS or TIFF format to ensure the best graphic output. Hard-copy printouts of the
artwork, of reproduction quality, must be included with the printed manuscript. (For more information, see Electronic Artwork
below.)
All figures and complex tables not transmitted in electronic form must be sent as high-quality, camera-ready hard copies.
Floats in the introductory material
Figures and tables for the introductory material will be repositioned and in many
cases also scaled to single-column width during the production process. Do not spend too much effort adjusting the placement of these
oats; they should appear at the end of the introductory material in the order Figure Captions, Figures, Tables. Do make sure
that each oat is clearly cited in the text, and the typesetters will ensure that they are placed in the optimal position, as near the
first citation as possible.
Use \section*{Figure Caption} to produce Figure Captions and use the figure environment for
the captions. Figures in the EPS format can be included with \includegraphics (and issuing \usepackage{graphicx} in the preamble). Note
that in using pdfLATEX instead of plain LATEX, the EPS figures must be transformed first to the PDF format. (In some TEX installations,
such as MikTEX, the TIFF figures can be included as such using \includegraphics). If the figures are not included in the LATEX document,
use \addtocounter{page}{nof} to increment the page counter by an appropriate amount (nof is the number of figures).
The easiest way to produce properly formatted tables is to employ the table and tabular environments. The use of long multipage tables
in the introductory material is strongly discouraged, as is the use of vertical lines within tables. Tables may be submitted within the
main text of the introductory material or as separate .tex files \input to the main file.
Data figures and data tables
The data figures/graphs and data tables constitute in many cases the most important part of the articles published in Atomic Data
and Nuclear Data Tables, and need special attention. These floats should be put at the end of the manuscript submitted to the journal
for review. The recommended order is Explanation of Figures/Graphs, (Examples for) Use of Figures/Graphs, References for
Figures/Graphs, Figures, Explanation of Tables, (Examples for) Use of Tables, Tables, References for Tables.
The way these are
produced is demonstrated in detail in the LATEX template. Only a few
hints are given below: • For the captions, use \section*{EXPLANATION
OF ...} and
\addcontentsline{toc}{section}{EXPLANATION OF ...}. • Use the tabular environment to create the explanations in
a tabular form. For very long explanations the longtable environment can be used instead. • Use the Dfigure environment and
the \includegraphics command for the data figures/graphs. The Dfigure environment of the adnd package is similar to the usual LATEX
figure environment, except that it automatically creates a correct entry to the Contents. • Reference list for the
data figures is produced by using the theDFbibliography environment, which is similar to the thebibliography environment. •
Long multipage tables are best formatted by using the longtable environment. Note that it is necessary to issue the command \datatables
just before the first longtable environment. • Reference list for the data tables is produced by using the theDTbibliography
environment, which is similar to the thebibliography environment.
Electronic artwork
In the interest of quality and
accuracy, Elsevier prefers to use author-supplied electronic artwork for all figures and complex tables. Each individual figure or graphic
must be supplied as a separate, stand-alone file. Figure and table files must be named with their respective numbers and graphic types
such as SmithFig1.tif, SmithFig2a.tif, or SmithTable1.eps. Long file names are acceptable.
Only EPS and TIFF file formats are considered
acceptable; TIFF is preferred. Artwork submitted in TIFF should adhere to the following resolution settings: half-tones (color/grayscale),
300 dpi; line art (black and white) and mixed images (halftones with text or line art), 600 to 1200 dpi. If it is necessary to import
graphics from a vector-based drawing program (e.g., Adobe Illustrator) into a raster-based program (e.g., Adobe PhotoShop) to produce
a TIFF file, a resolution of at least 600 dpi is required for quality reproduction.
Color artwork should be transmitted as CMYK color.
RGB images must be converted to
CMYK and all necessary color adjustments must be made prior to the transmission of the files. Authors
must supply Elsevier with a color-correct CMYK printout of all color electronic art.
When creating your figures, use font sizes and
line weights that will reproduce clearly and accurately when figures are sized to the appropriate column width. The minimum line weight
is 1/2 point (thinner lines will not reproduce well). Eliminate all excess white space from the borders of each figure. Generate EPS
figures without preview and background, but include a decent %%Bounding Box.
Do not include figure legends or other extraneous text
in a graphic file; figure legends should be provided as text in the section on Explanation of Figures/Graphs.
A template article, tmpadnd.tex, can be used as a skeleton for your own article. This file also contains examples of how long tables
are formatted. The template comes with the adnd package, downloadable from http://www.elsevier.com/locate/adt.
TRANSMITTING ELECTRONIC MATERIAL
As described above in Supplementary material, electronic material can be
transmitted
via FTP, e-mail, or computer disk.
Authors are requested to include in their electronic submission a cover letter and all ancillary
materials.
Transmission of electronic files is quicker and more reliable if the files are first compressed or encoded. Files created
using most popular compression/encoding schemes from the Windows, Macintosh, and UNIX platforms are acceptable. Acceptable formats include:
ZIP, SIT, BIN, HQX, CAB, TAR, TGZ, TAZ, TZ, GZ, Z, UU, UUE, XXE, B64, BHX, MIM.
All other formats, including LZH, ARJ, ARC, and self-extracting
archives (EXE and SEA), are not acceptable.
Important: Please choose unique, descriptive file names. File names should include
the corresponding author's last name, or the manuscript number (if available), or else the production number (if available), for example, SmithFig3.eps, ADND2001-0439Fig1.tif, or ADND4212Text.doc.
Upon successful completion of an FTP transmission, authors must
send an e-mail message
to the journal as notification that the files have been posted. The Atomic Data and Nuclear Data Tables
e-mail address is adndt@elsevier.com. In the body of the e-mail, please include the name of the journal to which the manuscript
has been transmitted, the title of the manuscript, the names of all the authors, the type of computer used to create the files, the type
of software and version number used to create the files, and a list of all file names.
REFERENCES
1. T. Oetiker, H. Partl,
I. Hyna, and E. Schlegl, The Not So Short Introduction to LATEX2e (Version 3.20, 09 August, 2001). The current version of this document
is available on http://www.ctan.org/tex-archive/info/lshort.
2. L. Lamport, LATEX—A Document Preparation System, 2nd ed. Addison-Wesley, Reading, MA, 1994.
