Differences between revisions 20 and 35 (spanning 15 versions)
Revision 20 as of 2009-09-20 15:05:07
Size: 5095
Editor: 24-183-238-75
Comment:
Revision 35 as of 2013-01-22 18:12:12
Size: 6218
Editor: 24-151-197-61
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
<<TableOfContents>>
Line 8: Line 10:
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]]. 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, 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]].
Line 10: Line 12:
  * 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]]
'''Under no circumstances shall you turn in a paper that contains any content from the template. This includes bold questions within the paragraphs''' (this does not apply to section names). Any repreductions of content constitutes plagerism and carries standard consequences from the syllabus.
Line 19: Line 14:
When you write a technical report for Dr. Anderson, use the LaTeX template above and assiduously follow DrAndersonsRulesForWritingPapers. LaTeX template:
 
   * [[attachment:generic-template.tex|Source]]
   * [[attachment:generic-template.pdf|PDF]]
   * [[attachment:my.bib]]
   * My own [[attachment:Grading_Rubric.pdf|grading rubric]] for project papers (No longer used, but still a good guideline) See: [[http://dra.cs.southern.edu/compwiki/SupplementaryLatexRubric?action=AttachFile&do=view&target=LaTeX+Paper+Dr.+A+Supplementary+Rubric.pdf|LaTeX Supplementary Rubric]]

This simple LatexTemplate, with no content, works specifically with Winedt's gather function.

== LaTeX Tools ==

  * [[http://www.tug.org/texworks/|TeXworks]] - popular, free! Often comes with [[http://miktex.org/|MikTeX]]
  * [[http://www.xm1math.net/texmaker/|Texmaker]] - popular free! Has spell checking integrated.
  * [[http://www.winedt.com/|WinEdt]] - popular shareware! My personal choice.

== Writing Rules ==

Technical writing for sciences varies significantly from what you typically produce in English classes. When you write a technical report for Dr. Anderson, you must use the LaTeX template above and assiduously follow DrAndersonsRulesForWritingPapers.
Line 31: Line 43:
Here is clean, simple LatexTemplate with no content (this was designed to work specifically with WinEdt's gather function). [[http://ctan.mirrors.hoobly.com/info/svg-inkscape/InkscapePDFLaTeX.pdf|Include inkscape drawings in LaTeX]] is a howto for inkscape - a great option.
Line 33: Line 45:
I use wmf2eps which is an excellent program. Here is at least on issue 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)>>

{{{#!latex
Or for extended paragraphs see the code that produced this \LaTeX
\begin{equation}
    e=mc^2
\end{equation}
}}}

For more examples on including LaTeX in this wiki see LatexPreamble and LatexArticle
If you are using eps files instead of .png/.jpg files (rare now), you may want to use wmf2eps to convert files to eps format. This is especially useful if you are using \psfrag to alter picture text. One issue 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).
Line 73: Line 72:
          \> \> \> \> $M[i,j] := max(M[i,j],M[i,k]+M[k,j])$ \\           \> \> \> \> $M[i,j] := \max(M[i,j],M[i,k]+M[k,j])$ \\
Line 107: Line 106:

= Using LaTeX on this site =

There are two ways to use LaTeX. Inline: {{{<<latex(\LaTeX)>>}}} which produces: <<latex(\LaTeX)>>

{{{#!latex
Or for extended paragraphs see the code that produced this \LaTeX
\begin{equation}
    E=mc^2
\end{equation}
}}}

For more examples on including LaTeX in this wiki see LatexPreamble and LatexArticle

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, 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.

Under no circumstances shall you turn in a paper that contains any content from the template. This includes bold questions within the paragraphs (this does not apply to section names). Any repreductions of content constitutes plagerism and carries standard consequences from the syllabus.

LaTeX template:

This simple LatexTemplate, with no content, works specifically with Winedt's gather function.

LaTeX Tools

  • TeXworks - popular, free! Often comes with MikTeX

  • Texmaker - popular free! Has spell checking integrated.

  • WinEdt - popular shareware! My personal choice.

Writing Rules

Technical writing for sciences varies significantly from what you typically produce in English classes. When you write a technical report for Dr. Anderson, you must 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

Include inkscape drawings in LaTeX is a howto for inkscape - a great option.

If you are using eps files instead of .png/.jpg files (rare now), you may want to use wmf2eps to convert files to eps format. This is especially useful if you are using \psfrag to alter picture text. One issue 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).

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 text below before the \begin{document} element which allows me to use \progstart and \progend around a tabbing environment:

%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}}

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 on including LaTeX in this wiki see LatexPreamble and LatexArticle

WritingTechnicalPapersInLaTeX (last edited 2024-06-12 16:17:29 by scot)