Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

10.
Use the Correct Style File (.sty)
Which one do you want?
• Manually format the paper, e.g.,
All text must be in a two-column format. The total allowable width of the text area is 6 7/8 inches
(17.5 cm) wide by 8 7 8 inches (22.54 cm) high. Columns are to be 3 1/4 inches (8.25 cm) wide,
with a 5/16 inch (0.8 cm) space between them. The main title (on the first page) should begin 1.0
inch (2.54 cm) from the top edge of the page. The second and following pages should begin 1.0
inch (2.54 cm) from the top edge. On all pages, the bottom margin should be 1-1/8 inches (2.86
cm) from the bottom edge of the page for 8.5 × 11-inch paper; for A4 paper, approximately 1-5/8
inches (4.13 cm) from the bottom edge of the page. All printed material, including text,
illustrations, and charts, must be kept within a print area 6-7/8 inches (17.5 cm) wide by 8-7/8
inches (22.54 cm) high.
• Or, just make sure that you use the correct style file
Recommended by Tiffany Yu-Han Chen

19.
Subsections
section{Algorithm XXX}
label{sec:algorithm}
subsection{Problem formulation}
label{sec:problem}
subsection{Objective function}
label{sec:objective}
subsection{Optimization}
label{sec:optimization}
• DO add labels to all subsections
subsection{Objective function}
label{sec:objective}
• For sections, I cap the first letter
for every word
section{Experimental Results}
• For subsections, I cap ONLY the
first letter of the first word
subsection{Implementation
details}

21.
Organize your files
• Move figures to separate folders
• Use one tex file for each figure, table, and algorithm
• Leave the main.tex with only main texts
• Help focus on finetuning each figure
• Avoid copying and pasting an entire block of tables/figures
• Use input{FILE_NAME} to include the file to the main paper
• input{figures/teaser}
• input{figures/overview}
• (Optional) Use one tex file for each major section
• Avoid merge/commit conflicts

25.
Figures
• File format
• DO NOT use JPEG images (to avoid compression artifacts). Use PNG or PDF
• Resolution
• DO NOT use low-resolution images
• Position
• Put the figures to the top of each page begin{figure}[t]
• Caption
• The image caption should be self-contained
• Highlight the topic of the figure with bold font
textbf
[Faktor and Irani 2014]

27.
Multiple Images
• Put sub-captions directly under subfigures, do not put them in the
caption
• All the legends, axis, labels must be clearly visible
• Make use of color and textures to code information
(a) (b) PatchMatch propagation Flow-guided propagation
[Huang et al. 2016]

34.
Tables – Results
• Highlight the best and the second best results
• Group methods that use different training sets or different levels of
supervision
• Always provide citation for each method
• If you have a big table, use
resizebox{textwidth}{!}{
begin{tabular}
…
end{tabular}
}

35.
Tables – Making nice tables
• Which one looks better?
Source: Small Guide to Making Nice Tables by Markus Püschel (ETH Zürich)
Recommended by David J. Crandall

36.
Algorithms
• See the documentation of algorithm2e
• Provide the main steps of the algorithm
• Use consistent annotations
• Use references to sections and
equations to connect the main texts
with the algorithm
[Huang et al. 2016]

37.
Equations
• Use begin{equation}…end{equation} environment.
• Use begin{algin} … end{align} if you have multiple lines of
equations
• Label every equation label{eqn:Eqn-Name}
• For in-text math symbols, use $$, e.g. Let $x$ be …
• Define every notation
• For texts that are not part of the equation, use mathrm, e.g.
$x_mathrm{color}$

38.
Equations
• Number all equations
• Easy to refer to them
• Equations are grammatical parts of the sentences
• Never forget a period after an equation
• Never create a dangling displayed equation
• Negative numbers
• “-” indicate the dash. Use $-1$ to represent minus one
• Angle braskets
• Use langle and rangle, instead of the comparison operators < and >
• Big parentheses
• Use left and right for automatic resizing round (), square [], and angled
langlerangle brackets as well as vertical bars vert and Vert
Source: https://www.cs.dartmouth.edu/~wjarosz/writing.html

39.
Dashes
• hyphen (-, produced with one dash -)
• interword dashes
• E.g., non-negligible
• en-dash (–, produced with two dashes --)
• indicate an opposition or relationship
• e.g., mass--energy equivalence → “mass–energy equivalence”
• Pages
• e.g., as seen on pages 17--30 → “as seen in on pages 17–30”
• em-dash (—, produced with three dashes ---)
• denote a break in a sentence or to set off parenthetical statements
• e.g., A flock of sparrows – some of them juveniles – flew overhead
Source: https://www.cs.dartmouth.edu/~wjarosz/writing.html

42.
References
• Avoid multiple entries of the same paper
• Find the correct venue where the paper was published
• Do not use arXiv for every paper
• Manage the references
• Group the papers into different categories

43.
Citations
• Do not use citations as nouns
• If you remove all parenthetical citations from the paper, you should still have
complete, grammatically correct sentences
• “As shown in [1]” -> “As shown by XXX et al. [1]”
• No “[1] present XXX…”
• Spacing
• Use a non-breaking space “~” between a citation and the preceding word in
the sentence: “Path tracing~cite{Kajiya:86} is...”.
• Multiple citations
• Use cite{key1,key2}
• Do not use cite{key1}cite{key2}
Source: https://www.cs.dartmouth.edu/~wjarosz/writing.html