This is a template for typical lab reports of CEG 429. Fill-in your details above. There are editorial comments (colored green, color="#008000") like the present paragraph that should be deleted from your report. In this course, we prefer open source tools, but you use what ever editor you like, turnin your report as an all inclusive PDF file. There may be additional requirements described for a specific experiment.
A lab report is a technical report. Because there are about eight to be submitted in this 10 week course, our standards of how well written the report should be are fairly low. Not counting the Recorded Observations, the entire report is probably about 2 pages.
Be driven by the following motive. Suppose you come across the lab report of yours, say, two years from now, and re-read it. Can you make sense of it? Can you recall the important thoughts you had and observations you made two years ago? Include all such details.
Submit your report using the ~ceg42900/bin/turnin program while logged in with your OSIS lab login ID. The first parameter is Ln, where n is the lab number as you see it on the course home page, second and subsequent arguments are path names of files you wish to submit. But, remember, we prefer that you turn in an all-inclusive single pdf file.
Identify the equipment you used. Some of this will repeat for every lab. Currently, in OSIS Lab, this is a Dell PC with such and such hardware. Record the IP addresses, and Ethernet MAC addresses. Record any other details that you think are relevant.
Copy, paste and edit as needed the procedures given in the article on our web corresponding to this lab. Any time you include verbatim copy-and-paste, from my articles or those written by others, you must cite your source explicitly. If you literally followed the steps in our lab articles, with no changes whatsoever, just say so instead of copy and paste.
Collect all your observations here. Much of this should be verbatim cut-and-pasted from stdout, or from a redirected stdout file. Be judicious about how voluminous this is. Cut out portions that are repetitive, or not illuminative.
Include time stamp/ duration of major steps.
Interpret your recorded observations.
Always include a "personal experience" story in your description. What did you learn? Was something surprising? Was something difficult? How long did it take to complete the lab? Are there any suggestions?
A number of labs require that you
find a witness who has watched (seen? noticed?) you perform the lab.
It would be good to find a witness who understands the lab. If you
did the lab completely alone in the OSIS lab, or in a network outside
the WSU perimeter, state this fact. In this case, we may ask you to
demo this to us in the OSIS lab. No witness report is
needed.
In technical reports, the conclusion section includes both summary/derived statements as well as ending remarks.
Include scripts, etc. here.