Submitting Assignments
All assignments are submitted using the unix command give at any terminal in a CSE lab.
How to Submit
-
CHECK the file before you submit it. Each year many students make last minute changes just before submitting and don't check them, and their programs don't work.
-
Check your modules compile.
-
One common mistake students make each year is to add last minute comments but then forget to put -- before some of them.
-
Check your functions, modules, and files all have the correct names.
-
Check your code works using the latest versions of the stub modules provided. Press shift-reload in firefox/mozilla to check that you have the latest version of each page.
-
Check your code works for the published test cases.
-
Check you have not altered anything in the protected regions of the stub files.
-
Check you have put header comments with your name and tutorial in it at the top of the file. Don't put your student number in the file as other students may get to see the file.
-
After you have checked your submission, and you are sure it is working, submit it by typing the submission commands in an xterm window (or by using ssh from home if you know how to do so). The submission command is given in the assignment specification, it will be somthing like:
give cs1711 task2 Network.hs Diary.txt
-
You may submit as often as you wish but only your last submission will be marked.
-
The submission process may take a few minutes to complete (especially around the deadline!) so don't leave it to the last minute to submit or you may be late.
-
To check that your submission has been accepted, you can type somthing like:
-
If you are intending to submit remotely via ssh then do some trial runs long in advance to check it all works, and leave yourself enough time to drive into uni and manually submit if somthing goes wrong (you can bet your cable connection will fail shortly before the due time).
-
Checklist
1711
classrun -check task2
