Sample Paper for Complex Systems

First Author

The abstract should summarize the content of the paper, including its context and conclusions. Make sure that it is possible to understand the abstract without having read the entire paper. Remember that many database systems will access the paper through the listed keywords and from the title and abstract. If possible, use the passive voice and avoid personal pronouns in the abstract (“X is shown,” rather than “we show X”), but not if it leads to awkward sentence constructions. Try to keep the abstract below 150 words in length (and shorter for short papers). Do not cite references or display equations in the abstract.

The title serves as a headline for the paper and many readers will use it to decide whether or not to look at the paper. Avoid excessively general, technical or cutesy titles. Questions are acceptable as titles. In the title and other headings, capitalize the first letters of important words and proper names only.

Give complete affiliation and mailing address, including country. Use standard two-letter abbreviations for state names. For foreign addresses, give as much as possible in English. Authors are encouraged to give their first names and middle initials. Titles and positions should not be given or implied. Authors are listed by their affiliation. The example given has the first author at one organization and the second and third with a different affiliation. Funding and personal acknowledgments go at the end of the paper in an Acknowledgments section.

The introduction is a crucial part of a paper. It should explain the background and goals and should strive to be as widely accessible as possible. Jargon and abbreviations should be avoided. References to textbooks and other basic material should be cited, for example, as [–]. References should be numbered in the order in which they appear in the text. A space should be left before the brackets used to indicate a citation to a reference. If an arbitrary choice out of many possible references is made, indicate it as (e.g., []). It is preferred that author names are not used when referencing their works.

Except for very short papers, division into sections is strongly encouraged. The first section need not necessarily be entitled “Introduction.” There may be subsections as well as sections. Subsubsections should only be used for lengthy papers where more structure is required. All section headings are numbered.

A paper should be long enough to convey its main points to the general readership of Complex Systems. It is OK for a paper to be shorter than average. The length of a typical paper is between 20 and 30 pages.

Formatting Systems

Authors are encouraged to send electronic media as their submission. Although we prefer that papers be submitted as Wolfram Mathematica notebooks, we can process papers from a variety of other formats, such as LaTeX. Papers prepared using other formatting systems or submitted in hard copy only may have to be retyped, causing delays in processing. This sample paper was prepared with Wolfram Mathematica and can be used as a template. It is available for download at www.complex-systems.com/contribute.html. A LaTeX version is also available.

Figures and Other Displays

Figures are an excellent mechanism for communicating many kinds of results. Great care should be taken to produce clear, well-constructed figures. When there are many related graphs or images, they should usually be combined into a single figure.

Figures should be displayed near where they are first mentioned in the text and are numbered sequentially: Figure  is an example. All figures and tables should be mentioned in the text.

It is best to send your figures in a “scalable” form such as Wolfram Mathematica Graphics Objects, Encapsulated PostScript (EPS) or Portable Document Format (PDF). Figures can also be processed in “bitmap” formats such as BMP, PICT or TIFF, but scalable formats generally reproduce better.

ArrayPlot[CellularAutomaton[30,{{1},0},50],ImageSize->{244,Automatic}]

Figures should reproduce well (i.e., without noticeable aliasing) on common printers. The source file for a particular figure must include all elements of the figure and should not require modification. Lettering should be consistent throughout a figure and must be no smaller than 6 points when the figure is at final size. Lines should be thick enough that they do not break up under reduction (single-pixel lines rarely suffice). Filled black areas must not drop out. Whenever possible, the figures should be oriented in the same sense as text (portrait mode).

Computer programs or algorithm descriptions may be given either in equations or in figures. Literal expressions that occur as computer input or output should be given in typewriter font.

Tables should include captions similar to those for figures and should be numbered sequentially throughout the paper: Table  is an example. Tables must be oriented with the text and use 9-point type, and should be enclosed by a box.

The Main Text

Good English grammar is essential. Authors not fluent in English are strongly encouraged to have their paper checked for grammar by colleagues fluent in the topic of the paper and English. American spelling should be used and, if possible, checked by computer. Contractions such as “weren’t” should never be used, nor should exclamation marks.

Acronyms should be spelled out at their first use and given in capitals thereafter: cellular automaton (CA for singular), cellular automata (CAs for plural). Avoid introducing too many acronyms. Spell out abbreviations when they are first used. Spell out integers under 10 unless they are used with units of measure or begin a sentence (i.e., write “two” rather than “2” but use “2 miles”).

Italicize defined terms when they are introduced. Also italicize foreign language phrases on first use, if they are likely to be unfamiliar to the reader. The abbreviations “e.g.,” “i.e.” and “etc.” should not be italicized and should be used only in parenthetical material; spell out “for example,” “that is” and “and so forth” (or equivalents) in regular text.

Cross-references can be made to other sections in the paper (e.g., Section ) and to other numbered elements. When referencing displayed formulas use, for example, equation (). Footnotes should be avoided. Points worth making should appear in the main text.

Lists of items should be preceded by a complete sentence and may be laid out as follows.

If a list of items is given in the text, such as: (a) first item; (b) second item; and so forth, they should be indicated with parenthesized letters in italic typeface.

Equations and Mathematical Symbols

Consistent mathematical notation is essential to clear exposition. Try to use familiar notation; for example, avoid having x stand for an integer index.

All standard mathematical symbols and notations must be formatted in equation form, whether inline or displayed. Even standard English letters such as x must appear as x (mathematical font) if they correspond to mathematical symbols. Use roman for abbreviations in equations, for example, sin(x).

Displayed equations that are referenced in the text should be numbered sequentially:

(e^(2πi))==1.

Spaces should be inserted in equations where necessary to improve readability. Equations should be referred to as “equation ().” Short equations may be inserted directly in the text, as in β==2. Equations that involve extensive subscripts, superscripts or built-up objects should be displayed. Special symbols in equations must be strictly limited to those that can be produced with Wolfram Mathematica using common fonts.

If a formatting system other than Wolfram Mathematica or LaTeX is used, make sure that all symbols are very clearly identified, and that all subscripts and superscripts are evident. Complex Systems allows many kinds of notation. It is suggested that symbols or words related to actual or theoretical computers be indicated in typewriter font.

Great care should be taken in mixing plain English, mathematics and algorithm descriptions. Say, for example, “x is the position” rather than “x== position.” Consistency must be maintained between different occurrences of a symbol. If x is a mathematical symbol, make sure it appears as x everywhere, not sometimes as x or as x. As a rough guide, mathematical symbols should appear as x and computer symbols as x.

Theorem .  Theorems and other structured mathematical text should be used when it improves the presentation. They should not be a substitute for clear English exposition.

Proof.  Proofs can continue for several paragraphs. They should end with an empty square. □

About the References

References should give pointers to background material and related work. They should record credit due to other authors.

References are numbered sequentially throughout the text. Each item should be given a separate number (except when citations are made to different portions of the same document: these should be indicated as “[, pp. 3–56]” or “[, Chapter 14]”).

Full titles of papers should be given. They should be enclosed in quotation marks, with all important words capitalized. Titles of printed items should be followed by a comma inside the quotation marks. Include the paper’s digital object identifier (DOI) name (number) if it is available (www.doi.org/hb.html). Titles accessible only via the internet are treated differently based on their type. See the examples described in the References section of this sample paper.

To cater to a wide variety of disciplines, it is important that all names of journals be spelled out in full and italicized. (Use Physical Review Letters, not Phys. Rev. Lett., and Journal of Computer and System Science, not J. Comput. Sys. Sci.)

For printed items, give the journal’s volume number in boldface (do not write the word “volume” explicitly). The issue number should be placed in parentheses immediately following the volume number, but not in bold: for example, 4(1). Include months only when necessary, using their three-letter abbreviation. Give starting and ending page numbers.

Author names should be given with initials first, with spaces after each period. For sources that list more than 10 authors, the names of the first seven authors should be given, followed by “et al.” For sources with fewer than 10 authors, all names are listed.

Titles of books (i.e., published material with ISBN numbers) should be italicized. Names and cities of publishers and dates of publication should always be given. Conference proceedings that are distributed through ordinary publishers should be cited like books.

Titles of proceedings and reports that are distributed in other ways or via the internet should be given in full in the standard roman typeface. URLs or other information on how to obtain them should be given following the title. Pricing information should not be included.

Acknowledgments should thank individuals and organizations for their contributions to the work. All funding information should be placed in the acknowledgments. If acknowledgments imply some endorsement of the paper (e.g., “We thank X for checking…”), make sure the parties involved approve the statements made.

F. Authorlast and S. Authorlast, “Article Title,” Full Name of Journal, volume(issue number), year pp. #–#. doi:name.
R. Albert and A.-L. Barabási, “Statistical Mechanics of Complex Networks,” Reviews of Modern Physics, 74(1), 2002 pp. 47–97. doi:10.1103/RevModPhys.74.47.

I. J. Authorlast, Book Title, Publisher Location: Publisher Name, year. 
T. C. Schelling, Micromotives and Macrobehavior, New York: Norton, 1978.

A. Authorlast, “Paper Title,” in A Collection (F. Editor and S. Editor, eds.), Publisher Location: Publisher Name, year pp. #–#. doi:name.
S. Hou, J. Sterling, S. Chen and G. Doolen, “A Lattice Boltzmann Subgrid Model for High Reynolds Number Flows,” in Pattern Formation and Lattice Gas Automata (A. T. Lawniczak and R. Kapral, eds.), Toronto: Fields Institute Communications, 6, 1996 pp. 151–166.

A. Editor, ed., Book Title, nth ed., Publisher Location: Publisher Name, year. 
A. Law and D. Kelton, eds., Simulation Modeling and Analysis, 3rd ed., Boston: McGraw-Hill, 2000.

A. Authorlast, “Paper Title,” in Conference Proceedings Title (Conference Acronym and year), Conference Location (A. Authorlast, ed.), Publisher Location: Publisher Name, year pp. #–#.
P. Fritzson, L. Viklund, J. Herber and D. Fritzson, “Industrial Application of Object-Oriented Mathematical Modeling and Computer Algebra in Mechanical Analysis,” in Proceedings of the Seventh International Conference on Technology of Object-Oriented Languages and Systems (TOOLS EUROPE’92), Dortmund, Germany (G. Heeg,
B. Magnosson and B. Meyer, eds.), Hertfordshire, UK: Prentice Hall International (UK) Ltd., 1992 pp. 167–181.

A. Authorlast, Technical Report Title, Classification/Number, Department, University or Organization, Location, year. URL if available.
C. Lemieux, M. Cieslak and K. Luttmer, RandQMC User’s Guide: A Package for Randomized Quasi-Monte Carlo Methods in C, Technical report 2002-712-15, Department of Computer Science, University of Calgary, 2002. hdl.handle.net/1880/46569.

A. Authorlast, Preprint Book Title, Publisher Location: Publisher Name, forthcoming. 
J.-P. Aubin, L. Chen and O. Dordan, Tychastic Measure of Viability Risk: A Viabilist Portfolio Performance and Insurance Approach, Heidelberg: Springer, forthcoming.
vimades.com/AUBIN/EradicationVPPI-Presentation.pdf.

Company Name, Computer Program Reference Manual (available from Name, address). 
Xerox, InterLISP Reference Manual (available from Xerox Palo Alto Research Center, Palo Alto, CA).

A. Authorlast, “Future Paper,” Full Name of Journal, forthcoming. 
J. Riedel and H. Zenil, “Cross-Boundary Behavioural Reprogrammability Reveals Evidence of Pervasive Universality,” International Journal of Unconventional Computing, forthcoming. arxiv.org/abs/1510.01671.

A. Authorlast, “Title,” presentation given at Conference Name (Conference Acronym and year), Location. URL of abstract if available.
A. Banos, “Exploring Network Effects in Schelling’s Segregation Model,” presentation given at S4-Modus Workshop: Multi-scale Interactions between Urban Forms and Processes, Besançon, France, 2009.

Software Name, Release Version Number, Location: Organization, year.
U. Wilensky. “NetLogo.” Center for Connected Learning and Computer-Based Modeling, Northwestern University, Evanston, IL. (Oct 25, 2012) ccl.northwestern.edu/netlogo/index.shtml.

A. Authorlast. “Website (or page) Title.” (Month Day, Year) URL.
OnlineAtlas.us. “United States Interstate Highway Map.” (May 7, 2012) www.onlineatlas.us/interstate-highways.htm.

A. Authorlast. “Blog Title,” Blog Series Name (blog). (Month Day, Year) URL.
B. Yorgey, “Recounting the Rationals, Part II,” The Math Less Traveled (blog). (Apr 2, 2010) www.mathlesstraveled.com/?p=97.

A. Authorlast. “Forum Post” from Forum Name. (Month Day, Year) URL.
T. Rowland. “Enumerating Strings” from The NKS Forum—A Wolfram Web Resource. (Apr 2, 2010)
forum.wolframscience.com/showthread.php?s=&threadid=929.

A. Authorlast. “Demonstration Title” from the Wolfram Demonstrations Project—A Wolfram Web Resource. URL.
E. Pegg Jr. “Coin Flips” from the Wolfram Demonstrations Project—A Wolfram Web Resource. www.demonstrations.wolfram.com/CoinFlips.

A. Authorlast. “Wolfram Cloud Article Title.” (Month Day, Year) URL.
A. A. de Laix. “Encryption with Enigma.” (Jul 1, 2014)
www.wolframcloud.com/objects/1f52ae4b-0686-4bde-966e-
5e60d8225ae4.