Instructions for the presentation and report
On this page, I list booked demo sessions. If you want to sign up for a session, send an E-mail to me. Include the following information:
If you don't tell me about computer needs I must assume that you bring your laptop. I can provide a computer with Linux and XP that should be able to run anything that runs in the lab. It is about the same performance as Olympen. (Athlon 64x2, NVidia GT240.) If you need higher performance, that can be arranged (like AMD x6, 650Ti, Linux/Windows8, not far behind Southfork in performance) but I need a warning about it. I can also bring a Mac when needed. Other needs, please ask.
If you use my computer, do not expect us to have a working network connection in the presentation room. Bring your program on CD or USB stick, and if possible come to my room and test it no later than the day before!
A good demo session should have 3-4 groups, possibly 5. If we have only one group for a session, we will cancel it and move the group to another session.
E-mail me about what time you wish to present your work.
We will be in the small seminar room "Transformen" in the B
building, upper floor near the front entrance 27. (Near my office.)
Projector (VGA or HDMI) and whiteboards are available!
16th of may, 10-12We need two groups to run!
16th of may, 13-15Claudia Bratu and Christoffer Nilsson
17th of may, 13-15We need two groups to run!
17th of may, 15-17Emma Villemoes, Hampus Wåström
18th of may, 10-12Johan Lind, Björn Kernell
19th of may, 10-12Oskar Therén, Oscar Thunberg, Sebastian Parmbäck
20th of may, 10-12Antonio Jimenez, Maximilian Erhardt, Stefan Seibert, Patrick Mayr, "Crescer3D"
23th of may, 10-12Axel Blackert
Your demonstration consists of two parts:
Make us understand what you did. Focus on interesting points. Don't forget to be somewhat entertaining. Be aware of who you are talking to (your course mates). Make the time worthwhile for the audience!
Inform me beforehand of any special hardware and software needs! I will do my best to provide what you need, but inform me in time. Also, it is wise to test your program beforehand on the computer that you will use.
About 3-5 pages (no less than two pages of text), describing what you did, how it was done and why you solved it the way you did. I am not counting pages, I am counting contents. Use figures, it is a graphics course and screenshots are cheap. Typical structure:
1. Introduction. Describe the problem, basically the specification you started from. What features were mandatory and optional?
2. Background information. Any information about the kind of problem you solved that is needed to follow the rest of the report.
3. About your implementation. Tools used, program structure.
4. Interesting problems. Did you run into any particular problems during the work?
5. Conclusions. How did it come out? How could it have been done better?
Source-code must be supplied, preferrably in electronic form.