[instructions] version 2020/21
This commit is contained in:
parent
99a8a00848
commit
eae3bf3e7f
@ -1,7 +1,13 @@
|
||||
\setlength{\fboxsep}{2ex}
|
||||
\fbox{\parbox{0.95\linewidth}{\small
|
||||
|
||||
\textbf{Evaluation criteria:}
|
||||
This is your project assignment. Please read the instructions before starting your work.
|
||||
Do not understand the assignment as an exhaustive TODO list, rather the questions below are hints that are meant to guide you and allow for a smoother start. Do not feel limited by the questions; we want to see you diving into it.
|
||||
|
||||
Happy hacking!
|
||||
|
||||
\vspace{1ex}
|
||||
\textbf{Evaluation criteria:}
|
||||
|
||||
You can view the evaluation criteria on the
|
||||
\emph{SciCompScoreSheet.pdf} on Ilias.
|
||||
@ -9,35 +15,34 @@
|
||||
\vspace{1ex}
|
||||
\textbf{Dates:}
|
||||
|
||||
The code and the presentation should be uploaded to ILIAS
|
||||
\textbf{at latest on Tuesday, February 4th, 2020, 23:59h}. We
|
||||
The code and the presentation must be uploaded to ILIAS
|
||||
\textbf{at latest on Sunday, February 21st, 2021, 23:59h}. We
|
||||
will store all presentations on one computer to allow for fast
|
||||
transitions between talks.
|
||||
|
||||
The presentations are on Wednesday February 5th, 10--12, Thursday
|
||||
February 6th, 10--12 and 14--16.
|
||||
The presentations are on Monday February 22nd, 09:30--12:00, Tuesday
|
||||
February 23rd, 9:30--11:00 and Wednesday 24th, 09:30--12:00.
|
||||
|
||||
\vspace{1ex}
|
||||
\textbf{Files:}
|
||||
|
||||
Hand in your presentation as a pdf file. Bundle everything (the
|
||||
pdf, the code, and the data) into a {\em single} zip-file.
|
||||
\textbf{Hand in your presentation as a pdf file.} Bundle everything (the
|
||||
pdf, the code, and the data) into a {\em single} zip-file named with your last name.
|
||||
|
||||
\textbf{Hint:} create the zip file you want to upload, unpack it
|
||||
somewhere else and check if your main script is still running
|
||||
properly.
|
||||
somewhere else on your computer and check if your main script is still running properly.
|
||||
|
||||
\vspace{1ex}
|
||||
\textbf{Code:}
|
||||
|
||||
The code must be executable without any further adjustments from
|
||||
our side. (Test it!) A single \texttt{main.m} script coordinates
|
||||
the analysis by calling functions and sub-scripts which produce
|
||||
the analysis by calling functions and/or sub-scripts (see Box 1.10 in chapter 1) which produce
|
||||
the {\em same} figures (\texttt{saveas()}-function, pdf or png
|
||||
format) that you use in your slides (your code can also generate
|
||||
additional figures). The code must be comprehensible by a third
|
||||
person (use proper and consistent variable and function names).
|
||||
XXX Find out what RTFM means, act accordingly! chapter 1 Box 1.7, Code-style chapter XXX
|
||||
person (use proper and consistent variable and function names, see chapter 4).
|
||||
\textbf{Hint:} Find out what RTFM means and act accordingly ;). You can also always try to google your problems.
|
||||
|
||||
\vspace{1ex}
|
||||
|
||||
@ -48,10 +53,10 @@
|
||||
\vspace{1ex}
|
||||
\textbf{Presentation:}
|
||||
|
||||
The presentation should be {\em at most} 10min long and be held
|
||||
The presentation should be {\em at most} 10\,min long and be held
|
||||
in English. In the presentation you should present figures
|
||||
introducing, explaining, showing, and discussing your data,
|
||||
methods, and results. All data-related figures you show in the
|
||||
methods, and results. All data-related figures shown in the
|
||||
presentation must be produced by your program --- no editing
|
||||
or labeling by PowerPoint or other software. It is always a good
|
||||
idea to illustrate the problem with basic plots of the
|
||||
|
Reference in New Issue
Block a user