added proposal and moved tex
This commit is contained in:
parent
3c2f8d2c87
commit
d3154c077c
5 changed files with 296 additions and 0 deletions
0
code/flake.lock → flake.lock
generated
0
code/flake.lock → flake.lock
generated
54
proposal/main.bib
Normal file
54
proposal/main.bib
Normal file
|
|
@ -0,0 +1,54 @@
|
||||||
|
|
||||||
|
@inproceedings{DBLP:conf/sc/AndreadisVMI18,
|
||||||
|
author = {Georgios Andreadis and
|
||||||
|
Laurens Versluis and
|
||||||
|
Fabian Mastenbroek and
|
||||||
|
Alexandru Iosup},
|
||||||
|
title = {A reference architecture for datacenter scheduling: design, validation,
|
||||||
|
and experiments},
|
||||||
|
booktitle = {Proceedings of the International Conference for High Performance Computing,
|
||||||
|
Networking, Storage, and Analysis, {SC} 2018, Dallas, TX, USA, November
|
||||||
|
11-16, 2018},
|
||||||
|
pages = {37:1--37:15},
|
||||||
|
publisher = {{IEEE} / {ACM}},
|
||||||
|
year = {2018},
|
||||||
|
url = {http://dl.acm.org/citation.cfm?id=3291706},
|
||||||
|
timestamp = {Mon, 12 Nov 2018 09:20:44 +0100},
|
||||||
|
biburl = {https://dblp.org/rec/conf/sc/AndreadisVMI18.bib},
|
||||||
|
bibsource = {dblp computer science bibliography, https://dblp.org}
|
||||||
|
}
|
||||||
|
|
||||||
|
@misc{techblog:latex,
|
||||||
|
author = {{Overleaf Team}},
|
||||||
|
title = {Learn {LaTeX} in 30 minutes},
|
||||||
|
howpublished = {Tech blog},
|
||||||
|
url = {https://www.overleaf.com/learn/latex/Learn_LaTeX_in_30_minutes},
|
||||||
|
year = {2019},
|
||||||
|
note = {[Online; accessed Mar 10, 2020] \url{https://www.overleaf.com/learn/latex/Learn_LaTeX_in_30_minutes}}
|
||||||
|
}
|
||||||
|
|
||||||
|
@misc{techrep:latex,
|
||||||
|
author = {Tobias Oetiker and
|
||||||
|
Hubert Partl and
|
||||||
|
Irene Hyna and
|
||||||
|
Elisabeth Schlegl},
|
||||||
|
title = {The Not So Short Introduction to {LaTeX} 2$\epsilon$, or: {LaTeX} in 139 minutes},
|
||||||
|
howpublished = {Tech report, Version 6.3, March 26},
|
||||||
|
url = {https://tobi.oetiker.ch/lshort/lshort.pdf},
|
||||||
|
year = {2018},
|
||||||
|
note = {[Online; accessed Mar 10, 2020] \url{https://tobi.oetiker.ch/lshort/lshort.pdf}}
|
||||||
|
}
|
||||||
|
|
||||||
|
|
||||||
|
@book{research:book/SharpPW02,
|
||||||
|
author = {John A. Sharp and
|
||||||
|
John Peters and
|
||||||
|
Keith Howard},
|
||||||
|
title = {The Management of a Student Research Project},
|
||||||
|
location = {UK},
|
||||||
|
publisher = {Gower Publishing Limited},
|
||||||
|
edition = {3rd Ed.},
|
||||||
|
year = {2002}
|
||||||
|
}
|
||||||
|
|
||||||
|
|
||||||
242
proposal/main.tex
Normal file
242
proposal/main.tex
Normal file
|
|
@ -0,0 +1,242 @@
|
||||||
|
% document based on the VU Beta / BSc Thesis template
|
||||||
|
|
||||||
|
\documentclass[11pt]{article}
|
||||||
|
\usepackage{graphicx}
|
||||||
|
\usepackage{url}
|
||||||
|
|
||||||
|
\textwidth 15cm
|
||||||
|
\textheight 22cm
|
||||||
|
\parindent 10pt
|
||||||
|
\oddsidemargin 0.85cm
|
||||||
|
\evensidemargin 0.37cm
|
||||||
|
|
||||||
|
|
||||||
|
\begin{document}
|
||||||
|
|
||||||
|
\thispagestyle{empty}
|
||||||
|
|
||||||
|
\begin{center}
|
||||||
|
|
||||||
|
Vrije Universiteit Amsterdam
|
||||||
|
|
||||||
|
\vspace{1mm}
|
||||||
|
|
||||||
|
%\includegraphics[height=28mm]{vu-griffioen-white.pdf}
|
||||||
|
|
||||||
|
\vspace{1.5cm}
|
||||||
|
|
||||||
|
{\Large Bachelor Project Computer Science - Project Proposal}
|
||||||
|
|
||||||
|
\vspace*{1.5cm}
|
||||||
|
|
||||||
|
\rule{.9\linewidth}{.6pt}\\[0.4cm]
|
||||||
|
{\huge \bfseries Title of the Research Project\par}
|
||||||
|
{\huge \bfseries Comes Here\par}\vspace{0.4cm}
|
||||||
|
\rule{.9\linewidth}{.6pt}\\[1.5cm]
|
||||||
|
|
||||||
|
\vspace*{2mm}
|
||||||
|
|
||||||
|
{\Large
|
||||||
|
\begin{tabular}{l}
|
||||||
|
{\bf Author:} ~~student name ~~~~ (student number)
|
||||||
|
\end{tabular}
|
||||||
|
}
|
||||||
|
|
||||||
|
\vspace*{1.5cm}
|
||||||
|
|
||||||
|
\begin{tabular}{ll}
|
||||||
|
{\it VU supervisor:} & ~~supervisor name \\
|
||||||
|
{\it Daily supervisor:} & ~~supervisor name (company, if applicable) \\
|
||||||
|
|
||||||
|
\end{tabular}
|
||||||
|
|
||||||
|
\vspace*{2cm}
|
||||||
|
|
||||||
|
\vspace*{1cm}
|
||||||
|
|
||||||
|
\today\\[4cm] % Date
|
||||||
|
|
||||||
|
\end{center}
|
||||||
|
|
||||||
|
\newpage
|
||||||
|
|
||||||
|
\section*{Abstract}
|
||||||
|
|
||||||
|
Explain here the context, problem, prior work, your own approach, and expected impact if the project is successful. The word count is a maximum of 250.
|
||||||
|
|
||||||
|
Note:
|
||||||
|
\begin{enumerate}
|
||||||
|
\item This can be seen as a short summary of the combined Introduction and Conclusion sections.
|
||||||
|
\end{enumerate}
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
\section{Introduction} \label{sec:introduction}
|
||||||
|
|
||||||
|
Explain the research project. Also include here the personal value you hope to derive from this project.
|
||||||
|
|
||||||
|
Explain at least:
|
||||||
|
\begin{enumerate}
|
||||||
|
\item The context of this research project. How broad do you see the impact of a good result? (Will you change the world? The science of Europe? The industry of the Netherlands?)
|
||||||
|
|
||||||
|
\item The key terms addressed in this research project. You will expand on this element in Section~\ref{sec:background}.
|
||||||
|
|
||||||
|
\item The main problem addressed in this research project. You will expand on this element in Section~\ref{sec:problem}.
|
||||||
|
|
||||||
|
\item The key prior work related to this research project. You will expand on this element in Section~\ref{sec:related}.
|
||||||
|
|
||||||
|
\item The main research question, possibly paraphrased. You will expand on this element in Section~\ref{sec:researchq}. (If possible, also indicate the core of the approach, or an insight that can lead to it. You will expand on this element in Section~\ref{sec:approach}.)
|
||||||
|
|
||||||
|
\item The expected contribution of this research, for the scientific community and/or for your employer. You will expand on this element in Sections~\ref{sec:researchq}, \ref{sec:approach}, and~\ref{sec:plan}.
|
||||||
|
|
||||||
|
\item Expected contribution of this research, for yourself. How will this project develop you? How will it develop your career?
|
||||||
|
|
||||||
|
\end{enumerate}
|
||||||
|
|
||||||
|
For example, consider the project leading to publication~\cite{DBLP:conf/sc/AndreadisVMI18}:
|
||||||
|
\begin{enumerate}
|
||||||
|
\item Context: datacenters, the backbone of cloud computing and our digital economy.
|
||||||
|
\item Key terms: datacenters, scheduling, reference architecture.
|
||||||
|
\item Problem: understanding and improving the process of scheduling in datacenters.
|
||||||
|
\item Key prior work: research on scheduling in large-scale systems, scheduling practices in Big Tech companies (Google, Microsoft, Alibaba, etc.)
|
||||||
|
\item Main research question: How to design a good abstraction for datacenter scheduling? Key insight: a unified reference architecture is a good abstraction for the scheduling process.
|
||||||
|
\item Expected contribution, community: a survey, a reference architecture, an analysis of existing systems as mapped to the new reference architecture, a simulator implementing the reference architecture as the scientific instrument, experiments in simulation, description of a process for others to use the reference architecture, analysis of threats to validity.
|
||||||
|
Plus: a technical report accompanying the publication\footnote{The technical report is published as open science: \url{https://arxiv.org/pdf/1808.04224.pdf}}, various public talks, etc. (The team also went for and obtained the ACM reproducibility badge, which among others requires publishing FOS software and FAIR data.)
|
||||||
|
\item Expected contribution, personal: development into an independent researcher.
|
||||||
|
\end{enumerate}
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
\section{Background} \label{sec:background}
|
||||||
|
|
||||||
|
Explain the key concepts needed to understand this work.
|
||||||
|
See also Section~II of ~\cite{DBLP:conf/sc/AndreadisVMI18}.
|
||||||
|
|
||||||
|
|
||||||
|
\section{Problem} \label{sec:problem}
|
||||||
|
|
||||||
|
Explain in this section the main problem addressed in this work. The goal is to emphasize the value of a research project that addresses the problem. See also Sections~I and~III.A of~\cite{DBLP:conf/sc/AndreadisVMI18}.
|
||||||
|
|
||||||
|
Notes:
|
||||||
|
\begin{enumerate}
|
||||||
|
\item
|
||||||
|
Define the scope of the problem.
|
||||||
|
|
||||||
|
\item
|
||||||
|
Refer back to the background~(see Section~\ref{sec:background}) for key terms.
|
||||||
|
\end{enumerate}
|
||||||
|
|
||||||
|
\section{Related Work} \label{sec:related}
|
||||||
|
|
||||||
|
Explain in this section related work on the problem explained in Section~\ref{sec:problem}. The goal is to emphasize the extent and the key elements of related work.
|
||||||
|
See also Sections~I and~VII of~\cite{DBLP:conf/sc/AndreadisVMI18}.
|
||||||
|
|
||||||
|
Notes:
|
||||||
|
\begin{enumerate}
|
||||||
|
\item
|
||||||
|
At this stage of your research career, this part will include a brief survey of the state-of-the-art, guided by the project supervisor.
|
||||||
|
|
||||||
|
\item
|
||||||
|
Review and summarize the related work. What is known already? What should be known but isn't?
|
||||||
|
|
||||||
|
\end{enumerate}
|
||||||
|
|
||||||
|
|
||||||
|
\section{Research Question(s)} \label{sec:researchq}
|
||||||
|
|
||||||
|
Explain in this section the core research of the project. The goal is to show that the research is sufficiently balanced and broad. See also Sections~I and the short formulations (e.g., ``we investigate...'') in the following sections of~\cite{DBLP:conf/sc/AndreadisVMI18}. \\ \\
|
||||||
|
|
||||||
|
Notes:
|
||||||
|
\begin{enumerate}
|
||||||
|
\item
|
||||||
|
Formulate the main research question.
|
||||||
|
|
||||||
|
\item
|
||||||
|
Define the scope of the project. Typically, the scope of the project is much smaller than the scope of the problem (defined in Section~\ref{sec:problem}).
|
||||||
|
|
||||||
|
\item
|
||||||
|
Define detailed research questions. For each, explain at least: \textit{Why?}, \textit{Why important?}, and \textit{Why challenging?}
|
||||||
|
|
||||||
|
\end{enumerate}
|
||||||
|
|
||||||
|
\section{Approach} \label{sec:approach}
|
||||||
|
|
||||||
|
Explain in this section how you anticipate you can answer the question(s) formulated in Section~\ref{sec:researchq}. The goal is to show that the research is feasible. For this reason, this section is mainly methodological; the pragmatic plans on how to complete all this work follow, in Section~\ref{sec:plan}. See, for example, Sections~I (overview) and~V.A (experiment design) of~\cite{DBLP:conf/sc/AndreadisVMI18}.
|
||||||
|
|
||||||
|
Notes:
|
||||||
|
\begin{enumerate}
|
||||||
|
\item
|
||||||
|
Describe the approach, for each research question. Emphasis on method(s) -- What? Expected contribution.
|
||||||
|
|
||||||
|
\item
|
||||||
|
Introduce intuition about the key innovation and/or conceptual contribution.
|
||||||
|
|
||||||
|
\item
|
||||||
|
Try to explain why the approach would work. Explain the expected technical contribution.
|
||||||
|
|
||||||
|
\end{enumerate}
|
||||||
|
|
||||||
|
\section{Plan} \label{sec:plan}
|
||||||
|
|
||||||
|
Explain in this section how you expect to complete the parts defined in Section~\ref{sec:approach}. The goal is to show the work is feasible in the allocated time.
|
||||||
|
\
|
||||||
|
Notes:
|
||||||
|
\begin{enumerate}
|
||||||
|
\item
|
||||||
|
Understand this is a preliminary plan.
|
||||||
|
|
||||||
|
\item
|
||||||
|
Try to define at least the large components of the project. To do this, discuss with the project supervisor and/or consult a good article published recently in the field. For the running example, consult~\cite{DBLP:conf/sc/AndreadisVMI18}.
|
||||||
|
|
||||||
|
\item
|
||||||
|
Try to plan tasks with a granularity of at most one week, and ideally with a granularity of a day. Try to make the near-future tasks SMART. Plan tasks long into the future of the project as \textit{slack}.
|
||||||
|
|
||||||
|
\item
|
||||||
|
Try to attach milestones and key deliverables to the most important tasks. Make sure deliverables include the final report (or article) and at least one presentation (hopefully, in a major scientific venue).
|
||||||
|
|
||||||
|
\item
|
||||||
|
Revisit the plans as soon as you complete a task, but especially after the first few tasks of a kind, e.g., a literature review task (you read a new article), a design iteration (you made or improved a design), an implementation task (you coded a new feature), an experiment task (you conducted one experiment).
|
||||||
|
|
||||||
|
\end{enumerate}
|
||||||
|
\newpage
|
||||||
|
For the running example, the research plan included:
|
||||||
|
\begin{verbatim}
|
||||||
|
```
|
||||||
|
I plan to take the first two research questions in one step, since
|
||||||
|
they are closely related:
|
||||||
|
|
||||||
|
To build a representative abstraction, I need to survey the
|
||||||
|
existing approaches in the field. This way, the validation step
|
||||||
|
is combined with the design step. This combined stage I
|
||||||
|
intend to work on in the coming three months, and
|
||||||
|
have a first report on my results ready by late January 2017.
|
||||||
|
|
||||||
|
After this stage is completed, I will begin integrating it in the
|
||||||
|
OpenDC project [n.b., the simulator].
|
||||||
|
Because I can imagine that this step will take a
|
||||||
|
substantial amount of time, I plan to have produced a first,
|
||||||
|
full prototype of this integration by May 2017.
|
||||||
|
|
||||||
|
I will try to keep the paper writing process parallel to
|
||||||
|
these two stages as much as possible. However, knowing that
|
||||||
|
this is difficult, I am allocating the time from June to
|
||||||
|
July of 2017 to tie together the pieces and get
|
||||||
|
this paper ready for publication.
|
||||||
|
```
|
||||||
|
\end{verbatim}
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
\section{Conclusion} \label{sec:conclusion}
|
||||||
|
|
||||||
|
Revisit the context, problem statement, related work, and research design. See, for example, Section~VIII of~\cite{DBLP:conf/sc/AndreadisVMI18}.
|
||||||
|
|
||||||
|
|
||||||
|
% For more on bibliography styles, see
|
||||||
|
% https://www.overleaf.com/learn/latex/Bibtex_bibliography_styles
|
||||||
|
\bibliographystyle{abbrv}
|
||||||
|
\bibliography{main}
|
||||||
|
|
||||||
|
\end{document}
|
||||||
|
% \end{document}
|
||||||
Loading…
Add table
Add a link
Reference in a new issue