Author's Guide

Paper specification

The JuliaCon is accepting two different kinds of submissions:

  • a short form extended abstract (similar to a standard JOSS paper),

  • a more in-depth long form paper.

Extended abstract submissions

A one page paper + references etc.

An extended abstract lays out in a concise fashion the methodology and use cases of the work presented at the conference. It should be at most one page of content excluding references. The format is similar to a standard JOSS paper.

Full paper submissions

A paper of about 5-10 pages + an abstract with at most 600 characters, written in plain English with no symbol nor formula + references etc.

Compared to an extended abstract, a full paper presents more of the background and context motivating the work. It compares the work to other approaches taken in the field and gives some additional insights on the conference contribution. Use cases back up the work by showing how it can be used.

Submission details

On the technical side, the submission (to be submitted through this form) must be based on a git repository on GitHub. Typically, this would be the repository of your julia package or code. The paper itself should be written in LaTeX (not Markdown) and should reside in a paper/ subfolder (potentially in a separate paper branch) of this repository.

⚠ Note
It is possible to have the paper in a separate repository but we recommend using a paper/ subfolder instead.

To simplify and unify the submission process, we provide a template repository on GitHub. Using the structure of the paper/ subfolder of this template as a base is mandatory! In particular, it contains the following files:

├── paper.tex 
├── ref.bib
├── paper.yml
├── header.tex
├── jlcode.sty
├── journal_dat.tex
├── juliacon.bst
├── juliacon.cls
├── logojuliacon.pdf
├── prep.rb
├── bib.tex
└── bib.rb

Only the first 3 files should be edited. Modifications to others might be over-written and replaced by the template version later in the process.

All fields from paper.yml must be filled, including:

  1. title: the title of the paper

  2. keywords: the list of keywords (at most 10), each put on a new entry as in the example.

  3. authors: all authors in the order in which they are listed. Providing all authors' ORCID is not mandatory but advised.

  4. affiliations for all authors

  5. bibliography: the name of the BibTeX file, including the .bib extension.

⚠ Warning!
While the JOSS accepts papers in Markdown format it is important that your JuliaCon proceedings submission, i.e. the paper/ subfolder, does not contain a Otherwise Whedon will be confused by the existence of both paper.tex and Note that because of the absence of a file the Whedon preview service shouldn't be used/won't work.

Local build

Important: The paper is built using the latexmk tool:

latexmk -bibtex -pdf paper.tex

This will re-generate header.tex, bib.tex, journal_dat.tex and build the final PDF. The LaTex document can be split in multiple files without problem, just keep paper.tex your main file.

To clean up the directory, use:

latexmk -c


Note that the template repository is also available on OverLeaf in read-only mode. The platform supports the build process and can be used for authors which cannot create the PDF locally.