Timeline

Assignment 1.
Posted: During Lecture 4
Due: Tuesday, Feb 27th, 23:59

Assignment 2..
Posted: During Lecture 8
Due: Tuesday, Apr 2nd, 23:59

Project Assignment A
Slides Due: Tuesday, Apr 16th, 23:59 Presentation: Wednesday, Apr 19th (in class)

Project Assignment B
Due: Friday, May 10th, 23:59

Groups

• Assignments should be handed in in groups.
• You shall register in a group on DTU Learn.
• Groups should have 3 members.
• You shall work in the same groups throughout the course.
• All group members should be familiar with every aspect of the assignment. Everyone in the group should be able to solve every exercise.
• It is possible to have fewer than 3 group members, but we judge all reports the same.

Assignments 1 and 2

The lectures in this class run over 8 weeks. Each week, I will post a number of exercises. After 4 lectures, I will post an assignment. The assignment is a subset of the exercises you have solved in the previous 4 weeks (including the ongoing week). This means that, if you solve the exercises each week, the assignments will be easy. Follow carefully the instructions below to ensure your work is correctly submitted and assessed:

Repository Setup

• Create a Private Repository: Create a repository on GitHub or GitLab. This will allow me to review the commit history of each group member. Keep the repository private until the assignment deadline.
• Collaboration: Work collaboratively on the assignment within your group. It’s important that each member is familiar with all exercises.
• Jupyter Notebook: Include a Jupyter notebook in your repository, named Assignment1.ipynb or Assignment2.ipynb, containing solutions to all exercises.
• First Cell Requirements: The initial cell must contain a link to your GitHub repository and a contribution statement, explaining how you have divided work among members of the group. If you have worked together, but all commits to the Github repository were made by one (or two) specific member(s) of the group, explain why.

Submission Instructions

• Ensure the code runs: Make sure that your notebook runs and all outputs are visible. I recommend selecting Kernel -> Restart and run all cells before submission.
• Verify Output: Double-check that all outputs are correctly rendered. You’ll be annoyed to get bad evaluations because no-one could see your plots or there were errors in the output.
• Upload the Jupyter Notebook to DTU Learn: Submit the Jupyter notebook on DTU Learn.
• Make Repository Public: Change your repository’s visibility to public on the submission date.

Compliance

• Understand the Assignment: Read questions carefully and ensure you understand exactly what I ask before answering.
• Complete All Parts: Make sure you address all sub-questions.
• Follow Instructions: Follow any additional guidelines (specified in the assignment) regarding answer length, formatting, etc.

Notebook Formatting

You shall follow these formatting rules:

• Divide Your Answers: Do not solve all exercises in a single code cell. Organize your code according to the questions.
• Question Repetition: For clarity, repeat the question above its corresponding answer.
• Conciseness: Provide clear and concise answers, respecting any word limits set.
• Code Documentation and Output formatting: Include all necessary code and ensure it is well-documented and tidy. Avoid lengthy outputs and ensure there are no errors displayed.
• Plot Formatting: Format your plots properly. Label axes on plots and include explanatory text.
• Use of References: Cite references appropriately following academic standards.
• Objective Language: Be precise, write in objective language (avoid: “I think …”, “In my opinion…”, etc) - if you make an observation, support it with data.

Important: Non-compliance with the above instructions may negatively impact your evaluation (more on that below).

Evaluation

Your assignment will be assessed based on the following:

• Individual Assignment Parts:
  • Completeness (all questions/exercises have been answered/solved)
  • You have taken appropriate decisions to ensure the integrity/accuracy of your solution you have justified your choices
  • Code is implemented correctly
  • Your answers to the reflection and open questions demonstrate that you have understood the exercise and the course material.
• Notebook Formatting:
  • Adherence to the provided formatting guidelines.
  • Quality and clarity of plots and figures.

Scoring: Scores are assigned on a scale from 0 (insufficient), 1 (sufficient), 2 (good) to 3 (excellent), with the possibility of half-point increments (e.g., 0.5, 1.5, 2.5). The overall evaluation is the average of these scores, including all individual parts and the notebook formatting evaluation. These scores are intended for feedback purposes and do not directly map to a grade in the standard Danish grading scale.