1833
Comment:
|
4875
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
= Writing Technical Papers (in LaTeX) = This section draws heavily from work at my Alma Mater ([[http://cse.unl.edu/~goddard/WritingResources/|UNL]] - specifically Dr. Godddard's Writing Resources site) == Standard Technical Paper Templates == The standard outline presented here, in different forms, is a tool to assist you in writing technical papers (especially in computer science). It is relevant for a wide range of, but not every single, type of technical paper. It is certainly appropriate for Master's and Ph.D. theses, for conference and journal papers, and for technical reports. It is also appropriate for proposals, although the speculative nature of a project or thesis proposal requires some adaptation of the form. It is less appropriate for user documentation, but still explicitly represents a number of important issues that must be handled when writing product manuals. These outlines were first created by [[niehaus@eecs.ukans.edu|Douglas Niehaus ]], then modified by [[goddard@cse.unl.edu>|Steve Goddard]] and finally reproduced and edited here by [[scot@southern.edu|Scot Anderson]]. * MS Word * [[attachment:Generic-Technical-Paper-Skeleton.doc|Source]] * [[attachment:Generic-Technical-Paper-Skeleton.pdf|PDF]] * LaTeX * [[attachment:generic-template.tex|Source]] * [[attachment:generic-template.pdf|PDF]] * Short HTML version * [[attachment:ShortTemplate.htm|Short Proposal/Paper Template]] When you write a technical report for Dr. Anderson, use the LaTeX template above and assiduously follow DrAndersonsRulesForWritingPapers. == Reviewing Technical Papers == Many students do not know how to review a technical paper. It is important to learn for (at least) two reasons. First, you may be asked to review a confernce or journal paper. Second, you should always know your audience. Knowing what reviewers are looking for makes it easier to write a paper that they will understand (and like). * Prof. John Ousterhout (Berkeley) has a writeup on [[http://swig.stanford.edu/~fox/paper_writing.html#rev|reviewing papers]] (available through Prof. Fox's page). = Using LaTeX Tips and Tricks = Here is simple LatexTemplate with now content. I use wmf2eps which is an excellent program. Here are a few issues to keep in mind: 1. When using \psfrag, always make sure your excel, visio, ... files use ONE letter substitutions. If you use more than one letter, MS products put them in as individual letters instead of strings (which is what psfrag is looking for). |
|
Line 3: | Line 38: |
There are two ways to use LaTeX. Inline: {{{[[latex2(\LaTeX)]]}}} which produces: [[latex2(\LaTeX)]] | There are two ways to use LaTeX. Inline: {{{<<latex(\LaTeX)>>}}} which produces: <<latex(\LaTeX)>> |
Line 5: | Line 40: |
{{{#!latex2 | {{{#!latex |
Line 14: | Line 49: |
= Using LaTeX Tips and Tricks = I use wmf2eps which is an excellent program. Here are a few issues to keep in mind: 1. When using \psfrag, always make sure your excel, visio, ... files use ONE letter substitutions. If you use more than one letter, MS products put them in as individual letters instead of strings (which is what psfrag is looking for). |
= Example Constructs for LaTeX = |
Line 27: | Line 58: |
{{{ | {{{#!latex |
Line 35: | Line 66: |
{\bf input:} Matrix $M$ representing a gap-graph over $n+1$ vertices.\\ {\bf output:} True or False depending on whether $M$ is satisfiable. \\ \\ m := 0 \\ {\bf repeat} \= \\ | {\bf input:} Matrix $M$ representing a gap-graph over $n+1$ vertices.\\ {\bf output:} True or False depending on whether $M$ is satisfiable. \\ \\ m := 0 \\ {\bf repeat} \= \\ |
Line 39: | Line 73: |
\> \> \> {\bf for} \= k := 0 to n {\bf do} \\ \> \> \> \> $M[i,j] := max(M[i,j],M[i,k]+M[k,j])$ \\ |
\> \> \> {\bf for} \= k := 0 to n {\bf do} \\ \> \> \> \> $M[i,j] := max(M[i,j],M[i,k]+M[k,j])$ \\ |
Line 61: | Line 93: |
I usually place the following before the \begin{document} element: {{{ %defines the datalog operator :- with correct spacing etc. \def\lfp{\mathop{\hbox{\it lfp}} } \def\impl{\mathrel{\hbox{~~:---~~}} } %defines the program code minipage environment that I used with rules top and bottom %NOTE: you will need to change the lift value for the \rule command. This is set for 1.5 spacing. % single spacing: 6pt/6pt and doublespacing: 0pt and 12 point (I believe) %NOTE: If you use a \tabbing environment immediately after \progstart, (follow progstart by) put \vspace{-18pt} \def\progstart{\begin{center}\begin{minipage}{0.98\textwidth}\tt\small\noindent\rule[0pt]{\textwidth}{0.4pt} \\} \def\progend{\rm\rule[6pt]{\textwidth}{0.4pt} \\ \end{minipage}\end{center}} }}} |
Writing Technical Papers (in LaTeX)
This section draws heavily from work at my Alma Mater (UNL - specifically Dr. Godddard's Writing Resources site)
Standard Technical Paper Templates
The standard outline presented here, in different forms, is a tool to assist you in writing technical papers (especially in computer science). It is relevant for a wide range of, but not every single, type of technical paper. It is certainly appropriate for Master's and Ph.D. theses, for conference and journal papers, and for technical reports. It is also appropriate for proposals, although the speculative nature of a project or thesis proposal requires some adaptation of the form. It is less appropriate for user documentation, but still explicitly represents a number of important issues that must be handled when writing product manuals. These outlines were first created by Douglas Niehaus, then modified by Steve Goddard and finally reproduced and edited here by Scot Anderson.
- MS Word
- LaTeX
- Short HTML version
When you write a technical report for Dr. Anderson, use the LaTeX template above and assiduously follow DrAndersonsRulesForWritingPapers.
Reviewing Technical Papers
Many students do not know how to review a technical paper. It is important to learn for (at least) two reasons. First, you may be asked to review a confernce or journal paper. Second, you should always know your audience. Knowing what reviewers are looking for makes it easier to write a paper that they will understand (and like).
Prof. John Ousterhout (Berkeley) has a writeup on reviewing papers (available through Prof. Fox's page).
Using LaTeX Tips and Tricks
Here is simple LatexTemplate with now content.
I use wmf2eps which is an excellent program. Here are a few issues to keep in mind:
- When using \psfrag, always make sure your excel, visio, ... files use ONE letter substitutions. If you use more than one letter, MS products put them in as individual letters instead of strings (which is what psfrag is looking for).
Using LaTeX on this site
There are two ways to use LaTeX. Inline: <<latex(\LaTeX)>> which produces: <<latex(\LaTeX)>>
Or for extended paragraphs see the code that produced this \LaTeX \begin{equation} e=mc^2 \end{equation}
For more examples see LatexPreamble and LatexArticle
Example Constructs for LaTeX
Algorithm Template
Don't forget that
- \= sets a tab
\> uses it
- \\ ends a line (every line!)
\noindent \begin{minipage}{4.4in} \tt \noindent \hrulefill \begin{tabbing} {\bf Sat(M,n)} \\ {\bf input:} Matrix $M$ representing a gap-graph over $n+1$ vertices.\\ {\bf output:} True or False depending on whether $M$ is satisfiable. \\ \\ m := 0 \\ {\bf repeat} \= \\ \> m := m + 1 \\ \> {\bf for} \= i := 0 to n {\bf do} \\ \> \> {\bf for} \= j := 0 to n {\bf do} \\ \> \> \> {\bf for} \= k := 0 to n {\bf do} \\ \> \> \> \> $M[i,j] := max(M[i,j],M[i,k]+M[k,j])$ \\ \> \> \> {\bf end-for} \\ \> \> {\bf end-for} \\ \> {\bf end-for} \\ {\bf until} $m = \log(n+1)$ \\ \\ Flag := True \\ \\ {\bf for} \= i := 0 to n {\bf do} \\ \> {\bf if} \= $M[i,i] > 0$ {\bf then} \\ \> \> Flag := False \\ {\bf end-for} \\ \\ {\bf return}(Flag) \end{tabbing} \hrulefill\\ \rm \end{minipage}
I usually place the following before the \begin{document} element:
%defines the datalog operator :- with correct spacing etc. \def\lfp{\mathop{\hbox{\it lfp}} } \def\impl{\mathrel{\hbox{~~:---~~}} } %defines the program code minipage environment that I used with rules top and bottom %NOTE: you will need to change the lift value for the \rule command. This is set for 1.5 spacing. % single spacing: 6pt/6pt and doublespacing: 0pt and 12 point (I believe) %NOTE: If you use a \tabbing environment immediately after \progstart, (follow progstart by) put \vspace{-18pt} \def\progstart{\begin{center}\begin{minipage}{0.98\textwidth}\tt\small\noindent\rule[0pt]{\textwidth}{0.4pt} \\} \def\progend{\rm\rule[6pt]{\textwidth}{0.4pt} \\ \end{minipage}\end{center}}