Assignments 1, 2, & 3

• Assignment 1 will be posted after lecture 4 and due one week later (see details regarding Formalia below)
• Assignment 2 will be posted after lecture 7 and due one week later.
• Assignment 3 will be posted after lecture 9 and due one week later.

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.

Formalia regarding assignment 1-3

• For the delivery:

make a zip file named with your studentids

make sure to include all needed files (csv, images, html)

make sure the output (text, plot) is included

make sure that your code runs

• Try to control the length of your notebook. While grading, we look at how you prioritize material and express yourself clearly and succinctly.
• 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 make one single program to solve all exercises. Split your code according to the questions
• Check that you've saved your content to the notebook - so that we can see the results.
• The notebook is designed to contain your code, so do include it. But do keep it short & neat (not a lot of output, etc), and if something is bulky and ugly and you don't think it's necessary, you may leave it out.
• Format your plots properly. Axes must be labeled, etc.
• Make sure that you use references when they're needed and follow academic standards.
• Be precise, write in objective language (avoid: "I think ...", "In my opinon...", etc) - if you make an observation, support it with data.