1. 1 Dr. Scott Schaefer Data Structures and Algorithms CSCE 221H

2. 2/38 Staff Instructor  Dr. Scott Schaefer  HRBB 527B  Office Hours: T 8:30am – 9:30am, R 9:30am-10:30am (or by appointment) TA  Keishla Ortiz Lopez  HRBB 410A  Office Hours: MW 1pm-3pm Peer Teacher  Kuo-Wei Chiao

3. What will you learn? Analysis of Algorithms Stacks, Queues, Deques Vectors, Lists, and Sequences Trees Priority Queues & Heaps Maps, Dictionaries, Hashing Skip Lists Binary Search Trees Sorting and Selection Graphs 3/38

4. 4/38 Prerequisites CSCE 121 “Introduction to Program Design and Concepts” or (ENGR 112 “Foundations of Engineering” and CSCE 113 “Intermediate Programming & Design”) CSCE 222 “Discrete Structures” or MATH 302 “Discrete Mathematics” (either may be taken concurrently with CSCE 221)

5. Textbook 5/38

6. 6/38 Grading 3% Labs 12% Homework 5% Culture Assignments 30% Programming Assignments 10% Quizzes 20% Midterm 20% Final

7. 7/38 Assignments Turn in code/homeworks via CSNET (get an account if you don’t already have one) Due by 11:59pm on day specified All programming in C++ Code, proj file, sln file, and Win32 executable Make your code readable (comment) You may discuss concepts, but coding is individual (no “team coding” or web)

8. 8/46 Late Policy Penalty = m: number of minutes late days late percentage penalty

9. 9/46 Late Policy Penalty = m: number of minutes late days late percentage penalty

10. 10/46 Late Policy Penalty = m: number of minutes late days late percentage penalty

11. 11/46 Late Policy Penalty = m: number of minutes late days late percentage penalty

12. Labs Several structured labs at the beginning of the semester with (simple) exercises  Graded on completion  Time to work on homework/projects 12/38

13. Homework Approximately 5 Written/Typed responses Simple coding if any 13/38

14. Programming Assignments About 5 throughout the semester Implementation of data structures or algorithms we discusses in class Written portion of the assignment 14/38

15. Quizzes Approximately 10 throughout the semester Short answer, small number of questions Will only be given in class or lab  Must be present to take the quiz 15/38

16. Culture Assignments Two research seminar reports  One before Spring break, one after Biography of a famous Computer Scientist  5 minute presentation  Signup this week by sending me an email http://faculty.cs.tamu.edu/schaefer/teaching/221_Spring2015/Assignments/culture.html 16/38

17. Academic Honesty Assignments are to be done on your own  May discuss concepts, get help with a persistent bug  Should not copy work, download code, or work together with others unless specifically stated otherwise We use a software similarity checker  http://moss.stanford.edu 17/38

18. Class Discussion Board piazza.com/tamu/spring2015/csce221200 18/38

19. Asymptotic Analysis 19/38

20. Running Time The running time of an algorithm typically grows with the input size. Average case time is often difficult to determine. We focus on the worst case running time.  Crucial to applications such as games, finance, and robotics  Easier to analyze Running Time 1ms 2ms 3ms 4ms 5ms Input Instance ABCDEFG worst case best case 20/38

21. Experimental Studies Write a program implementing the algorithm Run the program with inputs of varying size and composition Use a method like clock() to get an accurate measure of the actual running time Plot the results 21/38

22. Stop Watch Example 22/38

23. Limitations of Experiments It is necessary to implement the algorithm, which may be difficult Results may not be indicative of the running time on other inputs not included in the experiment. In order to compare two algorithms, the same hardware and software environments must be used 23/38

24. Theoretical Analysis Uses a high-level description of the algorithm instead of an implementation Characterizes running time as a function of the input size, n. Takes into account all possible inputs Allows us to evaluate the speed of an algorithm independent of the hardware/software environment 24/38

25. Important Functions Seven functions that often appear in algorithm analysis:  Constant  1  Logarithmic  log n  Linear  n  N-Log-N  n log n  Quadratic  n 2  Cubic  n 3  Exponential  2 n 25/38

26. Important Functions Seven functions that often appear in algorithm analysis:  Constant  1  Logarithmic  log n  Linear  n  N-Log-N  n log n  Quadratic  n 2  Cubic  n 3  Exponential  2 n 26/38

27. Why Growth Rate Matters if runtime is... time for n + 1time for 2 ntime for 4 n c lg nc lg (n + 1)c (lg n + 1)c(lg n + 2) c nc (n + 1)2c n4c n c n lg n ~ c n lg n + c n 2c n lg n + 2cn 4c n lg n + 4cn c n 2 ~ c n 2 + 2c n4c n 2 16c n 2 c n 3 ~ c n 3 + 3c n 2 8c n 3 64c n 3 c 2 n c 2 n+1 c 2 2n c 2 4n runtime quadruples when problem size doubles 27/38

28. Comparison of Two Algorithms insertion sort is n 2 / 4 merge sort is 2 n lg n sort a million items? insertion sort takes roughly 70 hours while merge sort takes roughly 40 seconds This is a slow machine, but if 100 x as fast then it’s 40 minutes versus less than 0.5 seconds 28/38

29. Constant Factors The growth rate is not affected by  constant factors or  lower-order terms Examples  10 2 n  10 5 is a linear function  10 5 n 2  10 8 n is a quadratic function 29/38

30. Big-Oh Notation Given functions f(n) and g(n), we say that f(n) is O(g(n)) if there are positive constants c and n 0 such that f(n)  cg(n) for n  n 0 Example: 2n  10 is O(n)  2n  10  cn  (c  2) n  10  n  10  (c  2)  Pick c  3 and n 0  10 30/38

31. Big-Oh Example Example: the function n 2 is not O(n)  n 2  cn  n  c  The above inequality cannot be satisfied since c must be a constant 31/38

32. More Big-Oh Examples 7n-2 7n-2 is O(n) need c > 0 and n 0  1 such that 7n-2  cn for n  n 0 this is true for c = 7 and n 0 = 1 3n 3 + 20n 2 + 5 3n 3 + 20n 2 + 5 is O(n 3 ) need c > 0 and n 0  1 such that 3n 3 + 20n 2 + 5  cn 3 for n  n 0 this is true for c = 4 and n 0 = 21 3 log n + 5 3 log n + 5 is O(log n) need c > 0 and n 0  1 such that 3 log n + 5  clog n for n  n 0 this is true for c = 8 and n 0 = 2 32/38

33. Big-Oh and Growth Rate The big-Oh notation gives an upper bound on the growth rate of a function The statement “f(n) is O(g(n))” means that the growth rate of f(n) is no more than the growth rate of g(n) We can use the big-Oh notation to rank functions according to their growth rate f(n) is O(g(n))g(n) is O(f(n)) g(n) grows moreYesNo f(n) grows moreNoYes Same growthYes 33/38

34. Big-Oh Rules If is f(n) a polynomial of degree d, then f(n) is O(n d ), i.e., 1. Drop lower-order terms 2. Drop constant factors Use the smallest possible class of functions  Say “2n is O(n)” instead of “2n is O(n 2 )” Use the simplest expression of the class  Say “3n  5 is O(n)” instead of “3n  5 is O(3n)” 34/38

35. Computing Prefix Averages We further illustrate asymptotic analysis with two algorithms for prefix averages The i-th prefix average of an array X is average of the first (i  1) elements of X: A[i]  X[0]  X[1]  …  X[i])/(i+1) 35/38

36. Prefix Averages (Quadratic) The following algorithm computes prefix averages in quadratic time by applying the definition Algorithm prefixAverages1(X, n) Input array X of n integers Output array A of prefix averages of X #operations A  new array of n integers n for i  0 to n  1 do n s  X[0] n for j  1 to i do 1  2  …  (n  1) s  s  X[j] 1  2  …  (n  1) A[i]  s  (i  1) n return A 1 36/38

37. Arithmetic Progression The running time of prefixAverages1 is O(1  2  …  n) The sum of the first n integers is n(n  1)  2 Thus, algorithm prefixAverages1 runs in O(n 2 ) time 37/38

38. Prefix Averages (Linear) The following algorithm computes prefix averages in linear time by keeping a running sum Algorithm prefixAverages2(X, n) Input array X of n integers Output array A of prefix averages of X #operations A  new array of n integersn s  0 1 for i  0 to n  1 don s  s  X[i]n A[i]  s  (i  1) n return A 1 Algorithm prefixAverages2 runs in O(n) time 38/38