Commit 069936e3 authored by Michael Kohlhase's avatar Michael Kohlhase
Browse files

dimitar did not do his thesis with us afterall

parent c5984772
F=main
default:
pdflatex $F
# bibtex $F
# pdflatex $F
# pdflatex $F
evince $F.pdf
clean:
rm -f *.aux *.bbl *.blg *.log *.out *.toc *.nav *.snm *.pdf
This diff is collapsed.
\documentclass[orivec]{llncs}
%\usepackage{url}
%\usepackage{wrapfig}
\usepackage{amsmath,amssymb}
%\usepackage{listings}
%\usepackage{tikz}
%\usetikzlibrary{arrows}
%\usepackage{xkeyval}
%\usepackage{multicol}
\setlength{\hfuzz}{3pt} \hbadness=10001
\setcounter{tocdepth}{2} % for pdf bookmarks
\usepackage[bookmarks,linkcolor=blue,citecolor=green,urlcolor=red,colorlinks,breaklinks,bookmarksopen]{hyperref}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% local macros and configurations
\usepackage{ed/ed}
\usepackage{florian/basics}
\usepackage{local}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%\urldef{\mailsa}\path|{...}@jacobs-university.de|
%\newcommand{\keywords}[1]{\par\addvspace\baselineskip
%\noindent\keywordname\enspace\ignorespaces#1}
\begin{document}
\title{Automated Discovery of Modular Structure}
\author{Michael Kohlhase and Dimitar Misev and Florian Rabe}
\institute{Jacobs University Bremen, Germany}
\maketitle
\begin{abstract}
\end{abstract}
\section{Introduction}\label{sec:intro}
\input{intro}
\section{Conclusion}\label{sec:conc}
\input{conc}
\bibliographystyle{alpha}
\bibliography{florian/bibs/pub_rabe,florian/bibs/rabe,kwarc}
\end{document}
@TechReport{JS06,
author = "J. Sample",
title = "{On the Possibility of the Impossible}",
institution = "Jacobs University Bremen",
month = sep,
year = "2010",
}
\documentclass[a4paper,11pt,oneside]{article}
% $Id: ba-sample.tex 952 2006-03-06 20:14:35Z schoenw $
% To use this template, you have to have a halfway complete LaTeX
% installation and you have to run pdflatex, followed by bibtex,
% following by one-two more pdflatex runs.
%
% Note thad usimg a spel chequer (e.g. ispell, aspell) is generolz
% a very guud ideo.
\usepackage{times} %% native times roman fonts
\usepackage{parskip} %% blank lines between paragraphs, no indent
\usepackage[pdftex]{graphicx} %% include graphics, preferrably pdf
\usepackage[pdftex]{hyperref} %% many PDF options can be set here
\pdfadjustspacing=1 %% force LaTeX-like character spacing
\hypersetup{
pdfauthor = {Joe Sample},
pdftitle = {On the Possibility of the Impossible},
pdfkeywords = {possibility, impossibility, truth, myths}
}
\begin{document}
\thispagestyle{empty}
\begin{flushleft}
\textbf{\huge On the Possibility of the Impossible}
\end{flushleft}
\vspace*{6mm}
\begin{flushleft}
\textbf{\large Joe Sample}\\[2ex]
\end{flushleft}
\vspace*{1mm}
\begin{flushleft}
\textit{Computer Science \\
Jacobs University Bremen \\
Campus Ring 1 \\
28759 Bremen \\
Germany}
\end{flushleft}
\vspace*{6mm}
\begin{tabbing}
\textit{Supervisor:} \= \kill
\textit{Type:} \> \textit{Guided Research Proposal}\\
\textit{Date:} \> \textit{\today} \\
\textit{Supervisor:} \> \textit{Prof.\ V.\ Confused}\\
\end{tabbing}
\vspace*{2mm}
~\hrule
\begin{abstract}
Consider this a separate document, although it is submitted together
with the rest. The executive summary aims at another audience than
the rest of the proposal. It is directed at the final decision
maker, who typically is not an expert at all in your field, but more
a manager kind of person. Thus, don't go into any technical
description in the executive summary, but use catch-words and bold
statements that highlight the importance of your project.
(target size: 15-20 lines)
\end{abstract}
~\hrule
\newpage
\section{Introduction}
This, like the rest, addresses fellow experts from your field (but
not from your particular topic of research). Here you should
technically connect to the main concepts from that field and give an
outline of your project, stating the research/engineering question
that you want to get answered by your project.
(target size: 1 page)
\section{Statement and Motivation of Research}
This part should make clear which question, exactly, you are
pursuing, and why your project is relevant/interesting. This is the
place to cite relevant literature. Where does your project extend
the state of the art? what weaknesses in known approaches to you
hope to overcome? If you have carried out preliminary experiments,
describe them here.
(target size: 2-3 pages)
\section{Planned Investigation}
This is the technical core of the proposal. Here you lay out your
plans of how you want to answer your research question specify your
design of experiments or simulations, point out difficulties that
you expect to encounter, etc.
(target size: 2-3 pages)
\section{Evaluation Criteria}
This section discusses criteria which can be used to evaluate the
research results and which can be used to related research results
to the already known state-of-the-art.
(target size: 1 page)
\section{Timeline}
Here you break down the research activity into smaller steps which
will then guide you during the guided research work. Try to define
realistic milestones.
(target size: 1/2 page)
\section{Conclusions}
Summarize the main aspects of the proposal.
(target size: 1/2 page)
\nocite{JS06}
\bibliographystyle{unsrt}
\bibliography{bsc-sample}
\end{document}
The topics folder contains the open topics, the year folder the actual topics given out.
There is one year folder per year, and one subfolder for every student doing a guided research with us. This folder contains subfolders admin and project. The latter is accessible to the student. It contains a subfolder for the proposal and a file for the abstract.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment