Prelab 8 Due: 8:00AM on 2022-11-11

Note: This is not a paired lab, each student must work individually, both on the prelab and the lab itself.

Matplotlib

We will be using Matplotlib library in this lab. If you plan on working on your own computer, you’ll need to make sure that Matplotlib is installed before lab. Try import matplotlib in the Python console. If there are no messages, you are all set. If you get an error “No module named matplotlib”, you will need follow in the installation instructions in class. If you have trouble getting Matplotlib to work, please visit office hours or consult with the ASIs.

After you are able to import matplotlib, try out some of the simple examples from class to make sure it is working properly.

Program design

Read through the lab and make sure you understand what the program is supposed to be doing. Once you have a good feeling for the problem, your prelab for this week is to write a high-level, non-binding, design for your program. Your design must include the following information:

• The list of all of the functions you plan on implementing (not just the required functions). For each function, you should plan out the following (effectively write out the docstring):
  • One sentence description of the purpose of the function
  • The list of parameters
  • The return value
• In addition, include a brief description of any other aspects of your program (e.g., functionality not implemented within a function)

As you’re putting together your design, think about the following:

• What is the overall flow of the program and the flow of information? What needs to happen first? Second?
• What result(s) will each function generate and how will those results be used by other functions?
• Remember to keep functions as simple and as general as possible.
• If the function implements a computation, don’t also have it print out that result. Instead return it and print it out somewhere else. This allows you to reuse that function in other situations where printing isn’t desired.

You will be graded based on the detail that you provide in addition to how well you’ve thought through the problem. The more time you spend thinking about the organization of your code, the easier actually writing and testing the final code will be. Note, your plan is not binding, i.e. you can change your design as you go, but the more thoughtful you are the planning stage the less likely you will need to change your approach and the more efficient you will be.

What to turn in

Scan and submit your finished plan to Gradescope before the due date. Then bring your plan with you to lab. Gradescope has a helpful guide for scanning assignments.