| ... | ... | @@ -14,3 +14,22 @@ Please note that our schedule is tight and there are dependencies between your a |
|
|
|
We strive to give you feedback for your submission as soon as possible. However, you must not await our feedback as a signal to continue working. Seek for help as soon as problems show up to meet all deadlines. We prioritize lab support over submission feedback.
|
|
|
|
|
|
|
|
If your implementation or your review do not fulfill the requirements to pass the lab, you must correct or redo the respective part of the lab. In this case, we expect you to resubmit your lab solution within one week after you receive the feedback for your lab from us.
|
|
|
|
|
|
|
|
### Grading procedure
|
|
|
|
|
|
|
|
Requirements for lab completions is as follows:
|
|
|
|
|
|
|
|
* LabX initial submission
|
|
|
|
* Your lab repo is visible to your peer reviewers, TAs, and examinator
|
|
|
|
* LabX Review
|
|
|
|
* You have made two well-made reviews
|
|
|
|
* LabX final submission
|
|
|
|
* Your repo has had its two reviews marked as closed *by the reviewers*
|
|
|
|
* Your two reviews have been addressed and you have marked them as closed
|
|
|
|
* You submit a zip file containing your project file to Canvas
|
|
|
|
|
|
|
|
Exceptions are for Lab0a and Lab0b, which aren't graded, and Lab1a which is graded på TAs and examinator. After all labs are done there will be a cleanup task, where you will:
|
|
|
|
|
|
|
|
* Mark your lab repos as private
|
|
|
|
* Mark your lab repos as archived
|
|
|
|
* Ensure that reviewers, examinator, and TA's still [have access](https://docs.gitlab.com/ee/user/project/members/#add-users-to-a-project). |
|
|
\ No newline at end of file |
