Assignments

This page contains information about the assignments.

Timeline

One important thing is (of course) when the various assignments are due. Below is an overview

• Assignment 1

  • Posted: During lecture 4.

  • Due: Monday, Feb 19th. 23:55.

  • Peergrading due: Monday, Feb 26th. 23:55.

• Assignment 2

  • Posted: During lecture 8.

  • Due:

  • Peergrading due:

Assignment 1 & 2

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 .html file), summarizing the work contained in exercises preceding it.

Groups

• 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.

Formalia Regarding Assignment 1

We will be grading a single .html file (which we will view on localhost - it does not need to be online). Some instructions for creating that page

• Set up the entire assignment on a single page,

• Style it nicely using css that you like

• Separate each "Part" of the exercise using h2 tags

• If you have dependencies (e.g. Data, D3 library, style-sheet, external JS code, etc), put everything in a .zip-file and hand in the zip with everything. (Maybe even check that it runs on another computer).

More notes

• Remember that the handin should be anonymous, so don’t include your name and student ID.

• To help us navigate the work, it’s a good idea to repeat the question you’re answering.

• Try to control the length of your writing. 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).

• Format your plots properly. Axes must be labeled, make sure there’s text explaining the figure. "Plots" include your D3 visualizations.

• 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 opinion …​", etc unless I specifically ask for that) - if you make an observation, support it with data.

The assignment should be uploaded via http://peergrade.io/ (you can find the info for setting up your class account on Aula. All people in the group will need to register).

For the Delivery:

• Give the file any name, e.g. index.html. We will view your work on a local webserver.

• Once again: Double check that your file works correctly once you’ve uploaded it to http://peergrade.io/. Remember that you’ll be annoyed to get bad evaluations because no-one could get your code to run on their localhost.