Labs
FAIR WARNING: Although solutions to the labs are not distributed, solutions from students who previously took the course may be available on the Internet. Using those solutions is the safest way to earn an F in the course, as it represents a blatant violation of the student's Code of Academic Integrity. In addition, not all those solutions may be correct, and minor changes are introduced each year, so that in addition to relying on MOSS to spot code similarities, those offer easy flags for catching instances of plagiarism.
See Using git and bitbucket for more information on your git repository from which you will be able to retrieve lab assignments and submit your solution code and reports.
The material that needs to be turned in for each lab will typically include code implementing the desired functionality for the lab, results that report on the outcome of running your code in different scenarios, and a hard-copy lab report that includes your code, results, and usually answers to a number of questions meant to verify your understanding of the material and the results. All this material needs to be committed and pushed to you git repository, and a hard copy of the lab report needs to be turned in at the beginning of the class when the lab is due.
