-
Notifications
You must be signed in to change notification settings - Fork 23
Assignments
This page contains information about the 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.
- Assignments should be handed in 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.
We will be grading your .ipynb file, it should be uploaded via http://peergrade.io/
- For the delivery:
give the file any name, e.g.
Assignment1.ipynbmake 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 before uploading.
double check that your file renders correctly once you've uploaded it to http://peergrade.io/ (you will be able to do this as part of the upload procedure). Remember that you'll be annoyed to get bad evaluations because no-one could see your plots.
- Remember that the Notebook should be anonymous, so don't include your name and student ID.
- To help us navigate the Notebook, it's a good idea to repeat the question you're answering.
- 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 solve all exercises in a single code cell. Split your code according to the questions
- The notebook is designed to contain your code, so do include it. But do keep it short & neat (minimize long outputs, etc)
- Format your plots properly. Axes must be labeled, make sure there's text explaining the figure, 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.
This class has been hand crafted for you by Sune Lehmann in Copenhagen.
This work is licensed under a Creative Commons Attribution 4.0 International License.
