Browse Source

initial commit: templates

master
Trolli Schmittlauch 4 years ago
commit
f0dc3fd7b5
  1. 3
      .gitignore
  2. 2417
      IEEEtran.bst
  3. 4702
      IEEEtran.cls
  4. 188
      main.tex
  5. 6
      mybib.bib

3
.gitignore

@ -0,0 +1,3 @@
*.aux
*.log
*.synctex.gz

2417
IEEEtran.bst
File diff suppressed because it is too large
View File

4702
IEEEtran.cls
File diff suppressed because it is too large
View File

188
main.tex

@ -0,0 +1,188 @@
\documentclass[10pt,conference,final]{IEEEtran}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{clrscode}
\usepackage{xcolor}
\usepackage[pdftex]{graphicx}
\newcommand{\comment}[1]{{\parindent0pt\fbox{\begin{minipage}{0.45\textwidth}{\em #1}\end{minipage}}}}
\newenvironment{changed}{\red}{\color{black}}
\newcommand{\todo}[1]{ \color{red} \footnote{ \color{red}[#1] \color{black}} \color{black}}
\newcommand{\Hide}[1]{%
{
\parindent0pt
\emph{\scriptsize #1}
}
}
%\renewcommand{\Hide}[1]{}
\newcommand{\documenttitle}{This is a title}
\begin{document}
%----------------------------------------------------------------------
% Title Information, Abstract and Keywords
%----------------------------------------------------------------------
\title{\documenttitle}
% % %
% In case of double blind submissions:
%\author{
% \IEEEauthorblockN{Anonymous}
% \IEEEauthorblockA{Some Research Group\\
% Some Institution\\
% Some Email Addresses%
% }
%}
\author{
\IEEEauthorblockN{Author 1 ~ and ~ Author 2 ~ and ~ Author 3}
\IEEEauthorblockA{P2P Networks\\
TU Darmstadt\\
$[$login1, login2, login3$][$at$]$cs.tu-darmstadt.de%
}
}
\maketitle
% % %
% sources on writing papers:
% look for a /good/ outline at the end of this text, the /why/ is found at this link:
% http://homepages.inf.ed.ac.uk/bundy/how-tos/writingGuide.html
% http://www-net.cs.umass.edu/kurose/writing/
% http://www.cs.columbia.edu/~hgs/etc/writing-style.html
% Read ``Zen - or the art of motorcycle maintenance'' to understand what science and research is
% Read ``The craft of research'' to /really/ learn how to conduct research and report about it! :-)
% some hints on plagiarism: http://www.williamstallings.com/Extras/Writing_Guide.html
% read the text above again. the most important part (that we all tend to forget) is only 5 paragraphs
\begin{abstract}
\Hide{
1) Problem statement: The Problem (one is more than sufficient for each paper!)\\
2) Relevance: Why ist this problem /really/ a problem?\\
3) Response: What is our solution to the problem?\\
4) Confidence: how do we show in this paper, that our solution is good?
}
\end{abstract}
\begin{IEEEkeywords}
% Are NOT: Peer-To-Peer, Anonymity, Privacy.
% BUT TAKEN FROM THIS LIST:
% http://www.ieee.org/organizations/pubs/ani_prod/keywrd98.txt
Networks, Distributed Computing, Distributed Control, Availability, Security
\end{IEEEkeywords}
% }
\maketitle
%\IEEEpeerreviewmaketitle
\section{Introduction}
% % %
% Broad Topic
\Hide{Broad Topic, potentially little broad background}
% \IEEEPARstart{F}{irst} word
% % %
% Thema, special problem we're looking at, motivation
% pbly more background for our problem (why is it actually hard?)
% Broad background, general definitions
\Hide{Topic, some background}
% % %
% our goal and our claims (what are we solving in this work?)
\Hide{Our goal, research question, motivation and relevance (Why is it a problem the reader should care about? Why is it hard?)}
% % %
% Requirements for our solution
\Hide{Requirements for a good solution}
% % %
% Which metrics can we use to show the quality/quantity of our solution?
% pbly rough definition of metrics
\Hide{Metrics to measure how good a solution is}
\Hide{\{If space missing the related work may be presented in a paragraph here\}}
% % %
% Summary of our solution
\Hide{Overview of our solution and first confidence (how do we show that it's good?)}
\Hide{Our contributions in this paper}
% % %
% outline of the paper / reader's digest
\Hide{Reader's digest}
% % %
% Literature Survey and Background
\section{Background}
\label{sec:background}
% % %
% Theory (probably)
% % %
% Specifications
% % %
% Implementation
% % %
% Evaluation
% % %
% Related work (can be done together with literature survey)
% STATE HOW THE RELATED WORK RELATES TO YOUR WORK!! (how is it similar, how is it different?)
% Related work is not your enemy, but gives you ``the shoulders of giants'' you can stand on
% (and besides: some of the authors might review your paper... ;)
% % %
% Further work and conclusion
\nocite{booth08craft}
\bibliographystyle{IEEEtran}
\bibliography{mybib}
%----------------------------------------------------------------------
\end{document}
% % %
% A good outline for a computer science paper (according to Al Bundy)
%
% Title
% * - ideally the title should state the hypothesis of the paper
%
% Abstract
% * - state hypothesis and summarise the evidence that supports or refutes it
%
% Introduction
% * - motivate the contribution!
%
% Literature Survey
% * - broad and shallow account of the field, rival approaches, drawbacks of each, major outstanding problems
%
% Background
% * - states previous work in more detail, where this is necessary for understanding
%
% Theory
% * - underlying theory, definitions, theorems etc.
%
% Specification
% * - requirements and specs of implementation
%
% Implementation Evaluation Related Work
% * - narrow but deep comparison with main rivals
%
% Further Work Conclusion
% * - summarise research, discuss significance, restate hypothesis and the evidence for and against it, - recapitulate original motivation, reassess the state of the field in the light of this new contribution
%
% Appendices
%

6
mybib.bib

@ -0,0 +1,6 @@
@book{booth08craft,
author = {Wayne C. Booth and Gregory G. Colomb and Joseph M. Williams},
title = {{The Craft of Research}},
publisher = {University Of Chicago Pres},
year = 2008
}
Loading…
Cancel
Save