PFP is structured around five weeks with lectures and lab sessions on Monday and Wednesday, followed by a final project to be presented orally at the exam. Throughout the course, you will hand in four weekly assignments. These weeklies count for 40% of the grade, while the exam counts for 60%.
The teachers are Cosmin Oancea and Troels Henriksen.
All lectures and lab sessions will be delivered in English. The assignments and projects will be posted in English, and while you can chose to hand in solutions in either English or Danish, English is preferred.
All course material is distributed via this GitHub page. Assignment handin is still on Absalon. There is no mandated textbook for the course - you will be assigned reading material from papers and such.
This course schedule is tentative and will be updated as we go along.
The lab sessions are aimed at providing help for the weeklies and group project. Do not assume you can solve them without showing up to the lab sessions.
On Monday, we are in "Kursussal 3" at "Zoo" (a building connected to the museum of zoology).
On Wednesday, we are at DIKU in classroom 1-0-22 from 10:00-12:00 and in classrom 1-0-26 from 13:00-15:00.
Note that the order of labs and lectures are swapped for the first three teaching days.
After New Years, there will be no lectures, but labs will still be held to help with the group project.
| Date | Time |
|---|---|
| 6/1 | 15:00-17:00 |
| 8/1 | 13:00-15:00 |
| 13/1 | 15:00-17:00 |
| 15/1 | 13:00-15:00 |
The weekly assignments are mandatory, must be solved individually, and make up 40% of your final grade. Submission is on Absalon.
You will receive feedback a week after the handin deadline (at the latest). You then have another week to prepare a resubmission. That is, the resubmission deadline is two weeks after the original handin deadline.
The final project, along with the exam as a whole, contributes 60% of your grade, and is done in groups of 1-3 people (although working alone is strongly discouraged). We have a list of project suggestions, but you are free to suggest your own (but please talk with us first). Since the time to work on the project is rather limited, and there is no possibility of resubmission, you should ask for help early and often if you are having trouble making progress. The project should be handed in via Absalon on Friday the 17th of January. Send an email if you have trouble meeting this deadline.
Most of the projects are about writing some parallel program, along with a report describing the main points and challenges of the problem. The exam format is a group presentation followed by individual questions about both your project and anything else in the curriculum. Each group prepares a common presentation with slides, and each member of the group presents non-overlapping parts of the presentation for about 10 min (or less). Then each member of the group will answer individual questions for about 10 min.
You may find it useful to make use of DIKUs GPU machines in your work.
You log in by first SSHing to the bastion server
ssh-diku-apl.science.ku.dk using your KU license plate (abc123) as
the user name, and then SSHing on to one of the GPU machines. Despite
their names, they each have two multi-core CPUs and plenty of RAM as
well.
-
gpu01-diku-apl,gpu02-diku-apl,gpu03-diku-aplhave dual GTX 780 Ti GPUs. -
phi-diku-aplhas a K40 GPU. -
gpu04-diku-aplhas a GTX 2080 Ti GPU (by far the fastest).
All machines should have all the software installed you need. If you
are missing something, contact Troels. The
machines have a shared home directory (which is very slow), except
gpu01-diku-apl, which has its own home directory (which is a little
faster).
For CUDA to work, you may need to add the following to your $HOME/.bash_profile:
CUDA_DIR=/usr/local/cuda
export PATH=$CUDA_DIR/bin:$PATH
export LD_LIBRARY_PATH=$CUDA_DIR/lib64:$LD_LIBRARY_PATH
export LIBRARY_PATH=$LD_LIBRARY_PATH:$LIBRARY_PATH
export CPLUS_INCLUDE_PATH=$CUDA_DIR/include:$CPLUS_INCLUDE_PATH
export C_INCLUDE_PATH=$CUDA_DIR/include:$C_INCLUDE_PATHYou are not expected to read/watch the following unless otherwise noted, but they contain useful and interesting background information.
-
The Futhark User's Guide, in particular Futhark Compared to Other Functional Languages
-
The story of
ispc(you can skip the stuff about office politics, although it might ultimately be the most valuable part of the story)