Assignments

This page contains information about the assignments.

Assignments

The lectures in this class run over 8 weeks. Each week, we will post a number of exercises. After a set of lectures, we will post an assignment. The assignment is a subset of the exercises. This means that, if you solve the exercises each week, the assignments will be easy. Since Assignments 1 and 2 will be written reports (an IPython notebook, website), summarizing the work contained in exercises preceding it.

Groups

• Assignments should be handed in groups.
• Groups should have 3 members.
• It's preferred that you can work in the same groups throughout the semester.
• All group members should be familiar with every aspect of the assignment. That means, that you can split up the writing, etc., but everyone in the group should be able to solve every exercise. If there's an exercise that you can't solve, talk to your fellow group members, the professor, or one of the TAs about how it's done ... otherwise, you will be missing out.
• It is possible to have fewer than 3 group members, but we judge all reports the same, so being 3 in a group decreases the amount of writing you have to do.
• Remember to write a final section at the end of the report specifying the contributions of the various group members. I recommend calling that section "Contributions".

Formalia regarding Assignments

We will be grading your .ipynb file, it should be uploaded via [probably DTU Learn]

• For the delivery:

1. make sure that your code runs and renders all images, prints, etc. before you save your file and upload. We recommend restarting the kernel >under 'Kernel' and then clicking Cell --> Run all and making sure everything looks OK before uploading.
2. Opt in to a group on DTU Learn
3. Hand in as a group via DTU Learn

Some useful tips:

• To help us navigate the Notebook, it's a good idea to repeat the question you're answering and to be consistent in your formatting.
• Try to control the length of your notebook. While grading, we look at how you prioritize material and express yourself clearly and succinctly.
• Answering "yes" or "no" to questions is not sufficient. The questions are an invitation for you to reflect on why.
• Make sure you comment your figures and explain which information you're able to extract from them even if it's not explicitly asked.
• Make sure you add references any time they're needed, e.g. when you introduce a formula, cite a paper, etc. and follow academic standards.
• Read the text carefully - make sure you understand the question. And make sure that you answer all sub-questions, etc. (It's easy to miss something, so be thorough).
• Do not solve all exercises in a single code cell. Split your code according to the questions/sub-questions.
• The notebook is designed to contain your code, so do include it. But do keep it short & neat. Make sure that your notebook does not contain irrelevant output, e.g. unnecessary print, etc.
• Format your plots properly. Axes must be labeled, make sure there's text explaining the figure, etc.
• Be precise, write as objectively as possible - if you make an observation, support it with data and theory.