Project demo sessions

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:

Equipment

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!

Sessions:

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.

2016 spring schedule:

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!

All sessions start 15 minutes past (10.15, 13.15 etc).

16th of may, 10-12

We need two groups to run!

16th of may, 13-15

Claudia Bratu and Christoffer Nilsson
Mikael Pessa, "Planet"
Johan Manfredsson, Magnus Björnfot, Matilda Lorentzon, "3D hunting game"
Marcus Lind, Sofia Martinsson & Emil Rundgren
Full!

17th of may, 13-15

We need two groups to run!

17th of may, 15-17

Emma Villemoes, Hampus Wåström
Robert Norlander, Erik Dahlström
Maja Ilestrand, Jessica Sällqvist, Andreas Brorsson
Room for more!

18th of may, 10-12

Johan Lind, Björn Kernell
Niklas Sundholm
Magnus Ivarsson
Mena Nadum, Viktor Anderson, "What a wonderful world"
Full!

19th of may, 10-12

Oskar Therén, Oscar Thunberg, Sebastian Parmbäck
Lage Ragnarsson, Isak Wiberg, Hans-Filip Elo
Piotr Olczak
Room for more!

20th of may, 10-12

Antonio Jimenez,  Maximilian Erhardt, Stefan Seibert, Patrick Mayr, "Crescer3D"
Martin Söderén, "3d file manager"
Erik Sven V. Jansson, "NQ Sokoban"
Anna Hjelmberg, Fredrik Fridborn
Full!

23th of may, 10-12

Axel Blackert
Carl Einarsson, Mattias Lantz Cronqvist
Magnus Wedberg
Participants: Jesper Post, Mateusz, "Planet Generator"
Full!


Sessions that are "full" or "crowded" should be avoided. One more group on a "full" session is possible but I think it is better to form one more session. Contact me to be put on a waiting list. As soon as I can find two groups who can share a session, we can add one.

Mandatory participation

You must be present on one session - the one including your own presentation! If it is not possible for all persons in your group to be present at the same session, your group will make two presentations, with different people!


Project demonstrations

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.

Reports

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.