All Projects → diku-dk → hpps-e2021-pub

diku-dk / hpps-e2021-pub

Licence: other
Public repository for the HPPS course

Programming Languages

c
50402 projects - #5 most used programming language
python
139335 projects - #7 most used programming language
Makefile
30231 projects

Syllabus and Material for High Performance Programming and Systems (HPPS)

Welcome to the course website for HPPS! While assignment handin is still on Absalon, all material and information will be located here. You are not expected to treat this repository as anything more than a website, but feel free to clone it if you are already comfortable with Git.

speedracer

Basics

HPPS takes place in block 2. There are three kinds of in-person teaching activities: lectures, exercises and the study café. All take place physically on campus.

Lectures are mostly conventional, but may use aspects of the flipped classroom approach.

Exercises are conducted in four smaller classes, each conducted by a teaching assistant (TA). An exercise session involves working on problems that will help you learn the curriculum, and in many cases directly train you in the skills you will need for the mandatory assignments.

Study cafés are places where you can get assistance with the mandatory assignments.

This course website is used for handing out material.

Discord can be used for asking questions. Invite link.

Absalon is used for handing in assignments and for course announcements.

Textbook

The textbooks are as follows:

Textbook videos

The authors of the CS:APP textbook have made videos available of their lectures. Note that these lectures are from a classic systems programming course, with a different focus (and much longer length) than HPPS. However, they may still be worth watching.

Schedule

Tuesday

  • Lecture: 10:00-12:00 (Lille UP-1, DIKU).

Thursday

  • Lecture: 10:00-12:00 (Aud 04, HCØ)

  • Exercises: 13:00-15:00

Exercises are split along four hold, in the following rooms and TAs:

Friday

  • Study café: 13:00-15:00 at A110, A111, C103, all at HCØ. Depending on needs, we may not use all these rooms.

Assignments

There are 5 assignment in total during the course with deadlines roughly every week.

The assignments will be graded with points from 0 to 4 and it is not possible to re-hand-in any of the assignments.

Assignments are made to be solved in groups of preferably three students, but groups of two active students will also do. We strongly encourage you not to work alone. Groups cannot be larger than three students. Each group must make their own solutions and cannot share implementations and report with other. You may however discuss material and ideas.

A1

  • Handout: 25/11

  • Handin deadline: 3/12

Text, code handout.

A2

  • Handout: 9/12

  • Handin deadline: 17/12

Text, code handout.

A3

  • Handout: 16/12

  • Handin deadline: 22/12

Text, code handout.

A4

  • Handout: 21/12

  • Handin deadline: 7/1

A5

  • Handout: 6/1

  • Handin deadline: 14/1

Study café

You can get help for assignments at the study cafés every Friday 13:00-15:00.

Exam qualification

To qualify for the exam you are required to achieve at least 50% of the total number of points in the first four assignments (that is, 8 points at minimum). You also need to get at least one point in each of the first four assignment.

Exam date

The exam is a take-home exam held from the 21st of January to the 25th of January. It has an estimated workload of 20 hours. It will involve practical programming and performance analysis of programs.

Languages

All written material will be in English.

Most oral teaching will be in Danish or English, depending on the specific teacher or TA.

You will mainly be programming in C and Python.

Software

You will be using a Unix command line and Unix tools for much of the course. See the Unix software guide.

See also this guide on the GDB debugger, which is a very useful tool for debugging C programs.

If you prefer an IDE see the VS Code installation and setup guide.

People

The teachers are

The TAs are

Exam format

The exam will be a take-home exam that will be very similar in form to the mandatory assignments.

Course plan

Each teaching activity has an associated subdirectory here on GitHub that lists expected reading and other material. Direct links below.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].