Advanced Deep Learning Systems (ADLS)
Course code: ELEC70109/EE9-AML3-10/EE9-AO25
Important dates
- 2nd Feb, Team making deadline
- 7th Feb, Practical submission
- 9th Feb, Midterm lab oral
- 27th Mar, Report submission and pull request finalization
Full dates
| Week Number | Date | Schedule |
| 2 | 15th Jan | Lectures (1 and 2), Team signup starts |
| 3 | 19nd Jan | Lectures (3 and 4) and lab sessions |
| 4 | 26th Jan | lab session |
| 5 | 2nd Feb | lab session |
| 5 | 5th Feb | lab session |
| 6 | 9th Feb | lab oral exam |
| 6 | 12th Feb | Lectures (5 and 6) |
| 7 | 16th Feb | Lectures (7 and 8) |
| 7 | 19th Feb | Lectures (9 and 10) |
| 8 | 23rd Feb | Lectures (11 and 12) |
| 8 | 26th Feb | Team Project scoping |
| 9 | 2nd Mar | Team Project Lab |
| 10 | 9th Mar | Team Project Lab |
| End of term | 27th Mar | Final report and code submission |
Lecture 1: Introduction
Lecture 2: MASE: Abstractions, Optimizations and Implementations
Lecture 3: An Introduction to Labs
Lecture 4: An Introduction to Labs (2)
Labs
Labs are hosted on MASE Wiki
The assessment contains practicals (30% in total), and a team project with two people (70%). If you used Colab Pro, we are wiling to reimburse that cost, please keep a copy of your receipt.
Practical Submission (30%)
- Deadline (7th Feb, email to a.zhao@imperial.ac.uk): A Markdown file, submitted as a team: with all answers (plots, tables …) of the questions and optional questions in labs. The email title should be “ADLS lab group xx”, and the file should be named as
adls_labs_group_xx.md (eg. adls_labs_group_0.md). - Corresponding code in your forked repository (will be checked in the lab oral, no submission needed). But you can include code snippets in the submitted markdown file.
- Deadline (9th Feb) Lab Oral, assessed individually.
Team Project (70%)
- A team of 3-4 people
- Team making link
- Team Project Requirements
- Past project lists
- Deadline (27th March): Coursework code submission as a pull request or an open repository on Github (assessed). The PR or repository should also have a clear documentation of the functionality that you have implemented and its corresponding tests. There should also be testing in place.
- Deadline (27th March, PDF attached in the PR): 6-page Report (assessed). The report should mainly focus on an evaluation of your implementation. The description of functionality and testing have being described in the PR or code repository already, so this 6-page report should include only the experiments you have designed to explore certain trade-offs and properties of your optimization.