Class, Following are some tips for submitting the lab: 1. Submit your answers as a document (preferred formats .pdf, .doc, .docx) 2. Paste annotated screen shot if any in the document itself. 3. Give examples or explain any formulae etc. to reason out your answer. 4. Kindly comment your code. 5. If you are modifying the example codes available on the website, try to show your modifications a little more explicitly. Eg: /***** My Stuff ***/ your code . . . 6. Please specify the path name and the file name of the modified code. Eg.: pids.c (path name : main/lab1/ques3) I have attached a sample lab report template having couple of questions and expected answer format. Please see grade sheets on this page for deliverables required in each lab and point values. Feel free to ask any questions. Regards, Ronak
1. Lab reports can be submitted in your prefered Text Editor, e.g. Microsoft Word, PDF etc.
2. Compress all the files (source code & lab report) in a single file before uploading to CULearn. Even though *.zip is prefered, any other Freeware used to zip up files will be accepted too.
3. Questions where source code is required, please include the source file in the submission, even if is simply a little modification of source provided on the course website or CD that comes with the book.
4. When pointing to a source file for a perticular answer, please make sure you explain how to run the code and copy paste the scrren shot of the output in your report. For example, you can mention; "See the submitted problem6.c file for answer #6. To view the following output pasted here in the lab report run program main() from the command prompt."
5. Do NOT embed the entire source code into the body of your report. Rather, upload your code as a separate file. It is fine (and encouraged) to embed relevant subsections of your code into the body of your report to discuss those portions if you have something to discuss about your code.6. Do NOT cut and paste host shell output into your report. Take a screen shot and add that to your report instead.
7. Hide non-relevant tasks on WindView trace outputs.
8. For screen shots, zoom in on the relevant material you are trying to discuss. A screen shot of your entire computer screen makes the relevant material hard to read because it is so small. However, make sure that you don't cut off axes or indices that could help explain what is going on with your screen shot.
your screen shots when it might not be obvious what information you are trying
to convey to your reader. Place the annotation directly on the screen shot rather
than explain the
screen shot with a text paragraph.
(Some of these tips are Courtesy of Bruce Hall, former TA ECEN 4/5623).
Back to HOWTO Page
Page updated August 19, 2008