Format

The exam will be held during your lab double-period on Tuesday, April 2.

The exam is designed as a 50-minute exam but you may use as much of the 2-hour lab period as needed.

This will be a written exam with no computers/calculators/etc allowed.

The only allowed aid is one study sheet. Here are the restrictions/requirements on this study sheet:

• Two sides of a single letter-sized piece of paper.

  (Note, you might want to just use the other side of your 6-week study sheet.)

• Hand-written and prepared by you.

• Write your name clearly on the top of the sheet. It will be handed in along with your exam (and returned back to you later).

The time you take to look over your notes, think about what to write down, and create your study sheet, is very valuable in studying and preparing for the exam — probably more than the actual info actual info will be useful to you during the exam time. For this reason, simply copying what someone else has on their sheet is probably a waste of your time.

Coverage

The 12-week exam will cover everything in the class so far, mostly focusing on units 5–8.

The best things to review are:

• Your own notes from class
• The readings from each unit
• The homework assignments so far. (These are probably the best guide for the kinds of problems you can expect to see on the exam!)

A brief summary (not exhaustive!) of topics and concepts that may appear on the exam is as follows.

• Computing concepts

  • How git works (local copy, local repo, remote repo)
  • Major hardware components (Processor, Memory, Disk, I/O)
  • Memory hierarchy: Registers, cache, RAM, disk, cloud
  • Processor instructions (Arithmetic, load/store, branching)
  • What is an operating system and what does it do
  • What is a program vs a process
  • Compiled vs interpreted programs
  • Compiled Python libraries such as numpy and pandas
  • Computing bottlenecks: CPU, memory, I/O
  • Running multiple processes at once
  • Multithreading vs Multiprocessing advantages and disadvantages
  • CPU-bound vs I/O-bound programs
  • Shared memory in multithreading, copied memory in multiprocessing
  • “Real”/“Wall-clock” time vs CPU time

• Data science concepts

  • Data science pipeline (review from SD211, still important!)
  • Missing data
  • Mis-formatted data
  • Erroneous data

• Python skills

  • Reading and writing to/from csv files
  • Checking for, removing, or replacing missing DataFrame entries
  • Combining multiple dataframes
  • Sorting dataframes by one or more columns
  • (Review from earlier, but still important): Selecting rows or columns of a dataframe based on indexes, names, or simple conditions
  • Writing a multi-threaded program
  • Writing a multi-processing progarm
  • Dividing a computational task into sub-tasks for separate threads or processes
  • Using global variables to communicate between threads
  • Using SimpleQueue for inter-process communication

• Command-line (bash) skills

  • Data cleaning with sed, grep, cut, pipelines, and regular expressions
  • Viewing processes with ps; understanding PID and PPID
  • Running in the background with & and wait
  • Checking real and CPU execution time with time
  • Using git commands like add, commit, push, fetch, merge, pull