Lab Outline
Labs focus on the key many of the key ideas and skills we look at in this course. It is important that students make consistent progress completing the labs. They will be marked by your tutor, and feedback provided.
Labs start on week 2 and are scheduled on:
- Tueday 2pm-3pm
- Wednesday 2pm-3pm
- Thursday 2pm-3pm
Please use MyTimetable to enrole in a lab before the end of week 1.
Weighting
The labs are worth 30% of the final mark. There are 6 labs and each one will be marked out of 5. All labs are due fridays at 5 pm. The first lab is due in Week 3. The school’s git lab server will be used for submitting labs. Late work will not be marked.
Links
A few handy links:
- Java Doc API within the labs use the url: file:///usr/share/doc/openjdk-8-jdk-headless/api/index.html
- Text book
- An Introduction to Programming and Software Development using Java
- OpenGL v1.1 Command Summary
- Blender Summary
- Example code from lectures - This code will not be made available during the lab tests.)
Getting Started
We have created a guide for getting started with the labs here.
Marking
All the labs will have 3 tasks (questions) each marked out of 4, with the following marking guide will be used:
Criteria | Indicative mark |
---|---|
Correct solution including all edge cases, the code well designed and formatted, names (including functions, variables, and classes) are appropriately selected, along with appropriate comments. | 4 / 4 |
Correct solution except on very minor edge cases, or solution has minor issues with style. | 3.5 / 4 |
Working solution with a number of minor issues associated with function or style. | 3 / 4 |
Most of the solution is complete, although functionally not completely working. | 2 / 4 |
Made some attempt at the solution that shows some understanding of the requirements and how a solution may be done. | 1 / 4 |
No attempt was made or what was done was unrelated to the problem. | 0 / 4 |
The marking guide is indicitive, and we reserve the right to modify (increase or decrease) marks based on the quality of the work. For most questions, the work involved in going from 3.0 to 4.0 is comparable to that of going from 0.0 to 3.0. We highly recommend making at least a start on each question, as not attempting the final question limits the maximum possible mark to 3/5. If you really get stuck, even adding comments describing how you think the problem should be solved might get you some marks.
The lab will be scored according to
Labs
Labs will be released two-weeks before they are due.
To get started
- fork the project.
To submit your work
- perform a git commit.
- perform a git push.
For a demonstration of how to get started and information about how to set up an environment, please see Week 2’s lecture.
While discussing labs with other students is encouraged, each lab must be completed individually. Labs will be checked for students colluding with each other. If there is evidence of colluding or reusing previous students’ labs or contract cheating, the academic integrity process will be started.
Lab | Specifications | Repo | Due |
---|---|---|---|
Lab 1 | specs | repo | Week 3 Friday 5pm |
Lab 2 | specs | repo | Week 5 Friday 5pm |
Lab 3 | specs | repo | Week 7 Friday 5pm |
Lab 4 | specs | repo | Week 9 Friday 5pm |
Lab 5 | specs | repo | Week 11 Friday 5pm |
Lab 6 | specs | repo | Week 12 Friday 5pm* |
*Due to this lab’s due date aligning with the assignment due date, we have decided to issue a 1-week extension to all lab-6 submissions. That is, the new date for this lab is Friday, 5 PM, the 4th of November.