IAIP Exercise Session Information, Fall 2005
You can find the list of accepted programming exercises here and the
scores for the normal handins here.
Should you feel that the information is not up-to-date or incorrect please send an
email to petert@itu.dk .
Format of the exercise sessions
At the start of each exercise sessions we will go through the
suggested answers for the hand-ins that are returned to you the same
day, as well as the associated non-mandatory exercises. The suggested
solutions are available in paper form at the exercise session. For
interesting/complex/problematic exercises we encourage students to
present their solution, even if they suspect it might be wrong, so you
can get a better feeling as to what constitutes a good answer to that
exercise. If there is a programming exercise, we will also briefly
describe the code that is provided.
If there are topics from lasts week lecture that you have problems
with and wish to be recapped at the exercise session, please drops us
an email(before the exercise session) and we will prepare a brief
summary lecture on the topic.
Hand-ins grading system
For each week your work is graded on a fractional scale from 0 to 1. As a general
rule 1 is given when we feel that the answers reflect a good
understanding of topics covered in the exercise, and so does not imply
a 'perfect' score. Anything below 8/10 indicates that we think that
one or more important topics(depending on how far below 8/10) have
been misunderstood, and needs to be looked at again or that the format
of (some of) the answers is unacceptable. You will need to achieve an
average of 8/10 over all the hand-ins. In case someone does not
achieve this and wants to go to the exam anyway, we will give some
extra (tougher) exercises at the end of the course.
Programming exercises are are either accepted or
failed. All programming exercises must be accepted, and if failed they can
be handed-in again. On weeks with programming exercises, the programming exercise
will yield some mininmal score for the week. (note that for week 5 we gave credit to
both people that had done the programing exercise or not, this is because the
programming exercise has to be completed at some point).
Feedback on the course
As this is the first time this course is run, we welcome feedback on
all aspects of the course, including the exercises and the format of
the exercise session. Such feedback is possible through the ITU
course evaluation system , but it is important that you provide feedback
to us as fast as possible, so that we can make any changes in this
semester instead of waiting for the next time course is offered.
This is especially important regarding the amount/complexity of
the exercises, and the overall workload compared to the listed
course requirements.
Electronic Hand-ins
Electronic hand-ins are allowed, but should be avoided if
possible. Acceptable reasons for handing in by email is not being at
the lecture and exercise session or not being able to print at
ITU. Among reasons that are not acceptable are handing by email
because you are too lazy to print yourself.
Electronic handins should be a single PDF or Postscript file, do
not use Word .doc or similar formats.
All that is done on recieving an electronic handin is printing it, stapling it and
putting it in the pile of handins. Therefore all necessary information should be included
in the pdf file, and not as side-remarks in the email. This for example includes the name(or names for
programming exercises) of the students involved. Code should be formatted in a readable manner and should only include
whatever code was altered compared to the framework code provided.
Please send electronic hand-ins to petert@itu.dk onky.
Format of answers to programming exercises
When handing in programming exercises you should only include (on
paper) any code you might have changed as well as a brief description
of what you did (or alternatively lots of good comments). You do not
need to provide the solution in electronic form. If you are not using
the provided code, but have programmed it from scratch, you should be
aware that due to time limitations we can only provide very brief
feedback.
Answers to programming exercises can, contrary to the other exercises,
be handed-in in groups of three.
Where and when to hand-in and how to get hand-ins back
Exercises should be handed in a week after the exercise session for
the exercises. This can be done either at the pigeonhole of Tarik
Hadzic or Peter Tiedemann in 4D, at the lecture, or at the exercise
session. Corrected hand-ins can be retrieved at the exercise session
or from a folder in Peters pigeon hole (in effect from 6.oct, until then
come by our offices).
Late exercises and re-hand-ins
Except for the programming exercises, it is not possible to hand-in a
second time as we give suggested solutions. As default, late exercises
are not accepted, but in case there is a good reason for it, this can
be discussed. Late exercises will be corrected when time allows.