teaching/scientificComputing
Archived
3
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

[projects] rewrote instructions

Browse Source
This commit is contained in:
Jan Benda 2021-02-01 10:46:03 +01:00
parent eae3bf3e7f
commit e7787d6c3b
1 changed files with 64 additions and 56 deletions

120
projects/instructions.tex
View File

@ -1,65 +1,73 @@
\setlength{\fboxsep}{2ex} \setlength{\fboxsep}{2ex}
\fbox{\parbox{0.95\linewidth}{\small \fbox{\parbox{0.95\linewidth}{\small
This is your project assignment. Please read the instructions before starting your work. This is your specific project assignment. The project applies
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. topics from the course on real or simulated data, or is about
concepts we haven't covered yet. Work yourself into the data and
the topic and in the end present your insights to your fellow
students. The instructions to your project are meant as a guide to
get you started, but feel free to come up with own ideas. Do not
feel limited by the questions. We want to see you diving into it.
Do not hesitate to contact us for help on problems and to discuss
your ideas.
\vspace{1ex}
Happy hacking! Happy hacking!
\vspace{1ex} \vspace{2ex}
\textbf{Evaluation criteria:} \textbf{Evaluation criteria:}
For your grade we mainly evaluate the technical aspects of your
You can view the evaluation criteria on the code and figures. You can view the evaluation criteria in
\emph{SciCompScoreSheet.pdf} on Ilias. \emph{SciCompScoreSheet.pdf} on Ilias.
\vspace{1ex} \vspace{2ex}
\textbf{Dates:} \textbf{Dates:}
Deadline for uploading the code and the presentation on ILIAS is\\
The code and the presentation must be uploaded to ILIAS \centerline{\textbf{Sunday, February 21st, 2021, 23:59h}.}
\textbf{at latest on Sunday, February 21st, 2021, 23:59h}. We
will store all presentations on one computer to allow for fast The presentations are on Monday February 22nd, 09:30--12:00, Tuesday
transitions between talks. February 23rd, 9:30--11:00 and Wednesday 24th, 09:30--12:00.
The presentations are on Monday February 22nd, 09:30--12:00, Tuesday \vspace{2ex}
February 23rd, 9:30--11:00 and Wednesday 24th, 09:30--12:00. \textbf{Files:}
Bundle everything (the code, the data, and the pdf of the
\vspace{1ex} presentation) into a {\em single} zip-file named with your last
\textbf{Files:} name.
\textbf{Hand in your presentation as a pdf file.} Bundle everything (the \textbf{Hint:} create the zip file you want to upload, unpack it
pdf, the code, and the data) into a {\em single} zip-file named with your last name. somewhere else on your computer and check if your main script
is still running properly.
\textbf{Hint:} create the zip file you want to upload, unpack it
somewhere else on your computer and check if your main script is still running properly. \vspace{2ex}
\textbf{Code:}
\vspace{1ex} The code must be executable without any further adjustments from
\textbf{Code:} our side --- test it! A single \texttt{main.m} script
coordinates the analysis by calling functions and/or sub-scripts
The code must be executable without any further adjustments from (see Box 1.10 in chapter~1) which produce the {\em same} figures
our side. (Test it!) A single \texttt{main.m} script coordinates (\texttt{saveas()}-function, pdf or png format) that you use in
the analysis by calling functions and/or sub-scripts (see Box 1.10 in chapter 1) which produce your slides (of course your code can also generate additional
the {\em same} figures (\texttt{saveas()}-function, pdf or png figures). The code must be comprehensible by a third person (use
format) that you use in your slides (your code can also generate proper and consistent variable and function names and document
additional figures). The code must be comprehensible by a third the code, see chapter~4). \textbf{Hint:} Find out what RTFM
person (use proper and consistent variable and function names, see chapter 4). means and act accordingly ;). You are allowed and even
\textbf{Hint:} Find out what RTFM means and act accordingly ;). You can also always try to google your problems. encouraged to use the internet for every aspect of your project.
\vspace{1ex} \vspace{1ex}
\emph{Please note your name and matriculation number as a \emph{Please note your name and matriculation number as a
comment at the top of the \texttt{main.m} script.} comment at the top of the \texttt{main.m} script.}
\vspace{2ex}
\vspace{1ex} \textbf{Presentation:}
\textbf{Presentation:} Hand in your presentation as a pdf file.
The presentation should be {\em at most} 10\,min 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 in English. In the presentation you should present figures
introducing, explaining, showing, and discussing your data, introducing, explaining, showing, and discussing your data,
methods, and results. All data-related figures shown in the methods, and results. All data-related figures shown in the
presentation must be produced by your program --- no editing presentation must be produced by your program --- no editing
or labeling by PowerPoint or other software. It is always a good or labeling by PowerPoint or other software. It is always a good
idea to illustrate the problem with basic plots of the idea to illustrate the problem with basic plots of the
raw-data. Make sure the axis labels are large enough! raw-data. Make sure the axis labels are large enough!
}} }}