Overview

This course features several laboratory exercises that will require formal write-ups, as listed on the labs page.

• Unless otherwise stated:
• you may use the Mathworks' Matlab language reference (i.e. documentation) to determine relevant Matlab syntax and semantics. This will be considered "general knowledge", and you need not cite reference sources.
• you may consult only our textbooks and Mathworks references for information. All non-syntax consultations (including the textbook and Matlab references) require formal citation within the related program or exercise.
• You always may consult the instructor regarding questions (at least if the instructor is in his office with the door open).
• You may always consult your colleagues regarding questions on interpreting example code or about what an exercise is asking (but not about solutions or implementations).

Laboratory submissions will generally consist of two parts:

• A prose write-up consisting of complete sentences and accompanying images or figures, with headings as appropriate.
• Matlab script or function .m files used to produce your results.

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:

• Headings to easily separate the various sections of your write-up.
• A brief introduction to the lab summarizing the technique(s) or subject(s) being explored and your purpose or objective.
• As appropriate to the lab (its exercises and deliverables), prose descriptions of your approach to solving the problem at hand.
• Figures (images and/or graphs) inlined at appropriate places in the text. Your text should refer to the figures where appropriate. Note also that:
  • Every figure must have a caption.
  • Graphs should have axis labels (i.e. using xlabel and ylabel).
• As directed by the lab assignment, a section describing your observations about the behavior of the algorithm (i.e., stability, uniqueness, reliability, etc.).
• A brief conclusion summarizing your results and analysis.

Since 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 OpenOffice 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

You must submit your write-up as a PDF file. I will not open/read any other format (esp. OpenOffice or Word). It is generally easy to create PDF files from most processors (OpenOffice even has a button to do it).

Laboratory Programs: Scripts and Functions

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

• The first dozen or so lines of any Matlab file should be comments containing your name, your mailbox number, the class section, an identification of assignment being solved. If it is not a function, it should also contain a brief description of the contents of the file. For example,

   
  %
  % Author
  %   Jerod Weinman
  %   Box - SCIE
  %   CSC295
  %
  % Lab
  %  Image Formation
  %
  % Summary
  %   Estimates the noise encountered by a CCD from several images
  %   of a uniform surface. 
  %
      

• In addition to the above, documentation is required for every definition of a Matlab function, stating in English what that program unit is supposed to do. Documenting before you write a procedure can help you plan and clarify the requirements of your implementation. For example,

   
  %
  % Author
  %   Jerod Weinman
  %   Box - SCIE
  %   CSC295
  %
  % Lab
  %  Image Formation
  
  function N = estimateNoise(X,Y,Z)
  % ESTIMATENOISE Estimates the noise in a sequence of three images
  %
  % N = ESTIMATENOISE(X,Y,Z) where X, Y, and Z are grayscale images 
  % (all of the same dimensions) and N is a matrix of the same size 
  % containing the noise estimate -- a standard deviation
  % of the values at each pixel in the sequence.
  

Submitting Your Work

1. 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.
2. One group member should submit an electronic version of the file archive (lab.tar from 4 above) online via PioneerWeb by the beginning of class.

Notes on Grading

Requirements

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.

Style

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 that you may want to consider:

• Indentation/whitespace that helps delineate code blocks. (Most editors will help you with this.)
• Helpful comments on blocks of code or particularly complicated expressions
• Procedures that are reasonably small. (A very good guideline I try to follow is getting an entire procedure to fit on much less than one screen; this makes interpreting a procedure's action more readable by forcing you to break it down into named steps that can be seen at once. It also promotes easier debugging and unit testing.)
• Code lines that are no wider than 80 characters. This makes them easier to read both on screen and on paper. (Emacs's Matlab mode will do this for you automatically.)