You are required to work in groups of 3, which you may create on your own. In case you don't know where to start, you could reuse the groups we created in the introduction weeks. If you have any trouble you could use the #lab-partner-wanted channel of the Slack workspace to find a group.

Lab submission and grading

All labs should be submitted online via Canvas. You have to pass all of them to pass the course.

For Labs 1 and 4, a teaching assistant will review your submission and respond to you online via Canvas.
For Labs 2 and 3, which are divided into multiple parts, you need to submit the first parts online using Canvas, which will be graded by a TA. When you have finished the last part and thereby the whole lab, you need to present and explain your solution to a teaching assistant. See the detailed information below.

Some labs have extra assignments. These are for your own pleasure; there are no bonus points awarded.

Before you submit your code, spend some time on cleaning up your code; make it simpler, remove unneccessary things, etc. We will reject your solution if it is not clean. Clean code:

Does not have long lines (< 78 characters)
Has a consistent layout (avoid using TAB characters in your code)
Has type signatures for all top-level functions that you are asked to write
Has good comments
Has no junk (junk is unused code, commented code, unneccessary comments)
Has no overly complicated function definitions
Does not contain any repetitive code (copy-and-paste programming)
Make sure your names and group number are listed in your source files

Feel free to use the hlint program to help with many of these issues and other haskell style issues. If a the suggestion from hlint looks like it assumes knowledge about things we haven't covered yet in the lectures, you can ignore it (or possibly include it in a comment in your code).

Presentation of solutions

When you have finished all parts for labs 2 and 3 you need to present your solution to your supervisor. Make sure you present your solution to the same supervisor who graded the preceding parts of the lab assignment. You can do this during normal lab sessions via Zoom. See the TimeEdit schedule.

All members of the group must be present during the presentation, and are required to understand all of the code submitted, and it is the responsibility of all of the group members to make sure that this is the case. If one of the group members clearly does not understand the code then the group will not be passed, and will be expected to try again when all members of the group are able to explain the solution.

Deadlines

The assignments have two deadlines to be aware of:

First submission deadline, the so-called 'Due date' in Canvas:

Submit your complete solution.
Must be a serious attempt.
If there are problems, you will get feedback so you can revise your solution and resubmit.

Final deadline (~1.5 week after the first submission deadline):

You can submit several times before the final deadline, but you should have addressed all the supervisor's remarks. In case of a resubmission for the final part of lab 2 and 3, you might need to present your solution again. This is left up to the supervisor to decide.
Final, correct solution must be submitted and presented before final deadline.

We do not accept submissions after the deadline, so 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, not afterwards.

Code of Honor

Working on the assignments and developing your own solutions is an important part of the learning process. You can of course discuss assignments and solutions with other students, and the web forum can be used for general and specific questions, but don't share your solutions or parts of solutions directly.

Needless to say, 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.

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 suspect cheating:

We are obliged to 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.

Use of external libraries

In principle, the only external modules you are allowed to use in the labs are the ones mentioned in the lab descriptions, which include the following:

You are encouraged to look around on Hackage and experiment with external libraries after you have solved the assignments. But keep in mind that the graders may not have those libraries installed, so don't use non-standard modules in the files you submit.