This repository includes all the files you will need for preparing your GPTP 2016 Proceedings Volume chapter—including a template you should edit to include your chapter's text—except for image and BibTeX files you will need to provide.
Updated thoroughly (and simplified, thanks to the folks at Springer Verlag) since the workshop occurred! Please take a moment to give it a try.
- revised manuscripts due June 15, 2016
- copy editing will be done while you're all busy at the Big Meeting
- manuscripts will be returned to the author(s) as copy-editing is completed. Note this will involve actual copy editing and thus there may be important clarifications and improvements asked before the manuscript is complete.
- all manuscript work should be complete (including changes made in response to copy editing) by August 15, 2016
- yes, that said "August 15, 2016"
- That means August 15, 2016 is the final deadline. We will be mean. More than a decade of experience informs our promise of meanness on this.
- Chapters that have been completed satisfactorily by August 15, 2016 will be submitted to the publisher on September 1, 2016.
Just to make sure everything is set up correctly on your machine:
- clone or download this repository; unzip it if necessary
- navigate to the folder created, and then into
gptp2016-chapter - open the file
author.texin your LaTeX editor of choice - render the document (all dependencies used by the example chapter, including images and references, are already here in this directory)
- Take a moment to look over the document produced. It's loaded with helpful information for your own manuscript preparation!
- Look over the documentation provided by Springer, which is stored in
documentation/authinst.pdf. It's great!
OK, so now we both know your LaTeX installation is working! Now:
Make a copy of the file author.tex, leaving it where it is for now
Rename the file to something more useful, like yourname.tex for example, or some other name that will help us know whose chapter it is.
at line 39, add the chapter title
at line 43, add the author names
Edit the institutional affiliations appropriately. If you don't have an affiliation, that's OK, but please include the email address of the corresponding author.
Edit the abstract to include a succinct abstract of your work. "Succinct" means five or six sentences, 10–15 lines (rendered), max. If your abstract continues past the first page of the rendered manuscript, guess what? It's not an abstract, it's a paper.
Edit the section headings and the contents of the sections.
Probably you should also take out the example content from the example file. If you want. It's not too bad, but I don't recall anybody talking about it in the workshop, so maybe you'll want to.
Please be very careful to read the comments and example code regarding figures. Don't add new packages to make fancy figures unless you contact the editors (Bill Tozier, probably) first. Don't stretch the figures to be in weird places or weird sizes. Don't try to jam too many figures into one chapter. Don't use color. Don't use pixelated images. Don't don't don't.
Make them nice please. Then pictures are fun.
In your text, use \cite{<label>} for every citation, and make sure every <label> is unique in your document.
Actually, hang on... no there isn't. Please don't use the appendix shown in the example template.
Traditionally we've relied on Bill Langdon's GP Bibliography. Please feel free to include items you want from that. But but but you must also include any other references not present in that eminent file in your own references file. Edit (or generate using you favorite bibliographic management software) the file referenc.tex so that it has your chapter's references in it.
Editing bibliographic entries is complicated, but the documentation included in this repository is actually quite good. If you glance at the PDF file generated when you rendered author.tex (the original template you copied) you'll see all kinds of amazing useful helpful stuff near the end about references.
You can choose whichever bibliographic standards you like, but I think probably we will use the ones given in the first or second example blocks of the template's bibliography (references 1-5 and 6-10).
If you have trouble rendering the bibliography, please don't spend too much time fixing it to be pretty. We'll do that. Instead
- get all the references you use in your chapter into
referenc.tex - don't include any references there that aren't in your chapter
- make sure all the bibliographic info is present (full title, full author list, etc) and we will fiddle with the styles later
Please spell check. We will correct obvious misspellings without informing you, but would rather not have to do that.
Please write clearly. We will flag obscure or incorrect grammar if it appears in your manuscript and return it to you, and we'd really rather not do that.
Please refer to the pertinent literature in your contribution. Err on the side of extra references. Imagine somebody who is (1) interested but (2) a complete novice is reading your chapter.
Include all figures as encapsulated postscript .eps or PDF files .pdf in the directory with your chapter, at the same level as your text. Don't put them in a sub-directory, please. Just make sure the files are named reasonably and can be identified if they all get mixed up.
We'll do that. But these will certainly help:
Don't use color.
Don't use new or extra fonts.
Don't play bounding box games or check for hbox overflow errors.
Don't hyphenate things unless you really know they need to be hyphenated.
Don't have too many figures.
If you absolutely must must must have a full-page figure, please...
Sixteen pages, rendered using this template. Including figures and bibliography.
Please discuss your manuscript early and often on the Slack channel assigned to it.
Submit revised manuscripts by 15 June, 2016. To submit your manuscript:
- rename the folder
gptp2016-chaptertogptp2016-chapter-YOURNAMEHERE - zip the entire folder, and all contents
- upload this zip file to the Slack channel assigned to it (just drag it onto the channel input box!); if for some reason you're unable to upload via slack, then email it to Bill Tozier as an attachment with an explanation (and then he will help you figure out how to upload it correctly to the Slack channel, because that's probably what you wanted to do anyway)