lab04 - CISC106 Fall 2009 Lab04 Review the code examples...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: CISC106 Fall 2009 Lab04 Review the code examples from class. Some programs below are associated with a question. Answer the questions using comments below your code in the m-file. The office hours of the TAs and the instructor are on the class website. Visit us! NOTE: Every function comment section should contain, at a minimum, three examples of the function being called and the result of evaluating the call. These examples must include boundary conditions (as discussed in class). Your test files must cover at least these exact examples (other- wise, why did you choose them?) and possibly more. Testing is important. Problems 1. files: fact.m, factCPUTimeTest.m, factCPUTimePlot.m, myFactPlot.png An important tool for computer users, as scientists, is the ability to compare how fast programs run. Though we think of computers as fast, there are many problems which machines could do better if our programs ran faster (e.g. weather tracking and prediction, automated interpretation of x-rays, optimizing internet traffic in a dense city network). NOTE: The timing runs for this lab must all be run in Matlab on Strauss . You may do so remotely, but do not submit timing runs from a Matlab running directly on your own computer. If you are interested in how long something takes, do not time it only once. Time it multiple times and record all of your results. Matlab makes this easy....
View Full Document

Page1 / 3

lab04 - CISC106 Fall 2009 Lab04 Review the code examples...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online