Introduction to Functional Programming – General information about labsTDA555 / DIT440, LP1, HT2013
Home | Schedule | Labs | Exercises | Exam | AboutFire | Forum | TimeEdit | Links | 2012

Grading feedback

The feedback that you get on your lab submissions will make use of the following symbols:

--    Your function f does not work

Denotes something that has to be corrected and submitted again

==    Your function f is a bit too complicated

Denotes something that has to be corrected only if the lab has to be submitted anyway

**    I see you have solved the problem

Just a regular comment, nothing to correct

++    Your implementation of f is better than mine!

Something extra good, should of course not be corrected


Deadlines

Each lab (except the first one) has three deadlines.

First deadline:

  • Submit initial part of the lab
  • Must be a serious attempt
  • If there are problems, you will get feedback

Second deadline (one week later):

  • Complete lab
  • Must be a serious attempt
  • If there are problems, you will get feedback

Final deadline (1.5 weeks after second deadline):

  • Can submit several times over this period, each time getting new feedback
  • Final, correct solution must be submitted before final deadline
Submitting after a deadline is in principle unacceptable. It is much better to submit what you have before the deadline, even if you are not happy with it. If you have a good reason for an extension – contact us before the deadline.

If you do miss a deadline, you may get a new chance at the end of the course. Otherwise, there is always a new opportunity to finish the labs next year.


Cheating

Cheating on labs is unacceptable. Cheating means:

  • Using someone else's code
  • Showing your code to someone else (copying, emailing, printing, pen-and-paper writing)
  • Copying code from the web
  • Etc.
On the other hand, it is fully allowed to orally discuss assignments and solutions. The web forum can be used for general and specific questions, but of course not for posting parts of solutions.

If you have problems, you should talk to us instead of copying from others. If needed, you may get more time and more help. If this is not enough, it is advisable to redo the course next year. This option makes much more sense than cheating.

Some cheating can be detected by the lab graders, when they discover similar solutions (e.g. same code, but different comments, layout, variable names, etc.). At the end of the course, we will also use automatic software that checks for similarity between all submitted solutions.

This is what happens if we detect cheating:

  • We report this to the disciplinary board (Chalmers or GU)
  • You might be suspended ("avstängd")
    • 1-3 months (no studiemedel)
    • This has actually happened...
  • You might be expelled
But hopefully, this is not going to happen.