Provided more structure to timetable
Signed-off-by: Jim Martens <github@2martens.de>
This commit is contained in:
parent
d6a75f25bd
commit
4e776dd247
|
@ -210,6 +210,29 @@ regularly plan the time between 11 am and 5 pm for working on the
|
|||
thesis as the evenings are mostly full and regardless of that
|
||||
fact I do want to reserve free time.
|
||||
|
||||
\paragraph{Main tasks}
|
||||
Everything but the stretch goals are non-optional which makes
|
||||
the term "main task" rather difficult to grasp. The term implies
|
||||
that all other tasks are nice-to-have but not required. Therefore,
|
||||
I have chosen to use milestones instead as the highest grouping
|
||||
level.
|
||||
|
||||
\subsection*{Milestones}
|
||||
|
||||
The detailed timetable starts in the next subsection. A summary
|
||||
of the timetable regarding the milestones is presented here.
|
||||
|
||||
\begin{enumerate}
|
||||
\item Environment set up: Due date 20th March
|
||||
\item Fine-tuned SSD on SceneNet RGB-D: Due date 5th April
|
||||
\item Fine-tuned GPND on SceneNet RGB-D: Due date 12th April
|
||||
\item Networks evaluated: Due date 10th May
|
||||
\item Visualizations created: Due date 31st May
|
||||
\item Stretch Goals/Buffer: Due date 27th June
|
||||
\item Thesis writing: Due date 30th August
|
||||
\item Finishing touches: Due date 13th September
|
||||
\end{enumerate}
|
||||
|
||||
\subsection*{Environment set up}
|
||||
|
||||
\textbf{Due date:} 20th March
|
||||
|
|
Loading…
Reference in New Issue