This page summarizes the style guides used in the hadron structure paper arXiv:1001.3620. Since this paper combines several contributions by authors with distinct computational strategies and visual tastes, we needed to establish a common ground for how the figures are supposed to look like and how to express physical constants and observables in a unified manner.
To this end, I have written three style guides which put forward reasonable rules for how the results were presented. You can feel free to use them in your own papers if you so wish.
Note, that the paper is consistently written in LaTeX, thus all comments on symbols below explicitly refer to the standard software.
The issue of uniform graphs has come up a few times in some small-group and large-group conference calls. Therefore, I have suggested to employ a wide-spread graphics program uniformly in our upcoming paper. The one discussed on this page is already used by the majority of collaborators and thus a logical choice.
The standard program for 2D plots in the final version of the paper is Grace with the default font size altered. This software is available for all relevant platforms and easy to learn and use. The data files are human readable and can also be accessed and edited by scripts (e.g. via Python or Perl).
Grace is open source software and thus should outlive the production process of our paper. (I hope … with regards to the production process, I mean.) In addition, this page contains a standard template and a tutorial on how to draw error bars.
I submit the following template for 2D graphs: Kappa-v template for Grace. The template produces the following graph:
The template for Grace with a sample graph of the isovector anomalous magnetic moment.
The plot contains experimental data, lattice data, and error bands. The color scheme is close to the default and is both easily readable and supports quick comprehension.
The following rules apply:
Since several people have asked about this, I describe how to draw error bands using Grace.
Prior to reading them in the error bands have been computed (this form is quite common and human-readable):
<x_val_1> <y_val_1>-<y_err_1> <y_val_1>+<y_err_1>
<x_val_2> <y_val_1>-<y_err_1> <y_val_1>+<y_err_1>
<x_val_n> <y_val_n>-<y_err_n> <y_val_n>+<y_err_n>
Next, they need to be brought into the form:
Unless the data has already been generated in the proper form it can easily be converted with the following Python program:
#!/usr/bin/env python -ttt import sys # Read input file myh = open(sys.argv, 'r') cont = myh.readlines() myh.close() # Column offset? if len(sys.argv)>2: offset = int(sys.argv) else: offset = 0 # Compute result for i in range(len(cont)): j = cont[i].split() print '%s %s' % (j, j[1+offset]) for i in range(len(cont)-1, -1, -1): j = cont[i].split() print '%s %s' % (j, j[2+offset])
The important point is that the data forms a “contour” on the canvas that can be interpreted as a closed polygon. Therefore, the reversed ordering of the second half of the data
(x_n back to x_1) is crucial. Also note, that the data is now a simple
x y data set, no longer a data set of points with error bars
x y dy.
If we have prepared the input as a text file, we import it in the usual way via Grace's Data→Import→ASCII… dialog. We select the data, load a
“Single set” and choose
set type: “XY” (as discussed above).
In the Plot→Set Appearance dialog, we select the data, right click on it and choose
“Send to back”. This way, it won't block other information.
Next, we go to the
“Line” tab and select the
“Fill properties”. We pick the
“As polygon” and choose a solid pattern and color (in the example it is “cyan”). The rest can be left unchanged. Additionally, we should also set same color in the
“Line properties” part on the first tab (
“Main”). Otherwise, the error band will have a band around it plotted in a different color.
That's basically all there is to it. We can still play around with settings (to send systematic error bands to the back behind statistical ones etc.). But there is little need to tinker with the other settings since in most cases the default options are fine and/or already set in the sample graph linked above.
This style guide standardizes notations for equations, observables and symbols and finally some miscellaneous items. Notations follow the former paper on GPDs, arXiv:0705.4295, unless otherwise explicitly stated.
Imprint / Impressum
© 1997-2013 Dr. Wolfram Schroers. This site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License.
Additional permissions available at http://www.field-theory.org/editorial/index.html.
Wolfram is a leading software engineer focused on Enterprise and B2B apps on iOS. His clients rank from small independent studios to companies in the German DAX index.
He has worked at top Universities on three continents in the past decade and is a popular speaker at conferences. He is currently working in Berlin, Germany, and can be reached at his company website.