Laboratory Write-Up and Submission

CSC 295 - Computer Vision - Weinman

Information about expectations for laboratory exercises and methods for preparing to submit them.


This course features weekly laboratory exercises, as listed on the course schedule.
Unless otherwise stated: Laboratory submissions will generally consist of two parts: These are to be written and submitted using the guidelines below.

Laboratory write-ups

In creating a write-up for a lab, please follow the directions within the lab on what is to be submitted. In particular, your write-up should consist of: Because most of our labs are tightly focused, the overall text you may need to write will likely be small, though the reports may seem longer due to the inclusion of many images.
You are free to use whatever authoring program you wish for your write-ups. It is relatively easy to include images in LibreOffice documents (it even supports drag-and-drop on the MathLAN!). You may also wish to learn LATEX, or LYX a spiffy front-end for the mark-up language available on the MathLAN via the command lyx (I use it for all my research and teaching writing).
You must submit your write-up as a PDF file. I will not open or read any other format (esp. OpenOffice or Word). It is generally easy to create PDF files from most processors (LibreOffice even has a button to do it).

Laboratory programs: scripts and functions

In preparing any scripts or programs for the course, please follow these guidelines.

Submitting your work

You will have multiple files to submit (at the least a PDF and a Matlab file). Therefore, you will need create an archive of them for electronic submission. For example,
tar cf lab.tar source.m writeup.pdf ...
where lab.tar is the name of the archive file you want your files stored in. You may list as many files on line as you wish, or even use a wildcard (*.m) You may also add an entire directory to an archive by including the directory name without a trailing / in the list of files. If you do this to include the entire directory, please be sure you do not include any unwarranted image files, etc.
One group member should submit an electronic version of the file archive (i.e.., lab.tar) online via PioneerWeb by the beginning of class.

Notes on grading


When a lab write-up is submitted according to the format specified above, it should be understood that the images and figures accurately reflect the output from the accompanying program. Anything otherwise may raise questions of academic dishonesty; and, by College policy, any evidence of academic dishonesty must be turned over to the Academic Standing Committee for action.


Every programming task should yield readable and tested code. Because code maintainability is an important part of development, your labs' code will be graded in part on style, as well as correctness. After all, if I cannot understand your code (or it takes me too long to), I cannot give it a grade regarding its correctness.
Some style matters I care about: Failure to incorporate these style considerations will lower your grade.


Adapted from Assignments for Computer Science 213, Henry Walker; and CSC213, Fall 2006 : Laboratory exercises, Janet Davis. Some of the style considerations were adapted from Marge Coahran's.


1If you have read any of Tufte's four Graphics Press books and practice his advice well, you may be exempted from this requirement.