Class 39 — Friday April 24

We know you can

You are ready now – For problem solving prowess – Your best will be shown

---

Updates

• If they arise, any typos or corrections will be put here.

• Do not modify or delete any of the tester code in the modules we provided.

---

Zoom

• Link

---

Look both ways

• Back and ahead

---

Agenda

• Show your abilities

---

Test 2

• Do not download the test until you are ready to start.

• Your ninety minutes begins upon downloading.

• Is available here.

---

Resources

• Information sheet

• Built-in functions

• Module str

• Module list

• Module random

• Module dict

• Module Pillow

---

Important

• Remember the University accepted you because you are an outstanding student.

• Based on your past educational achievements, I expect you to do well on this test.

---

Notices

• You have 90 minutes to complete. People with accomodations have 90 minutes times their multiplier: 135 minutes (1.5) and 180 (2).

• Answer the questions in any order that you want.

• I suggest you do things the easiest way possible. There are no intended trick questions. Each module has a straight-forward answer.

• To make things go smoother, you are strongly encouraged to submit as you go along.

---

Test rules

• You must use my download files.

• Before completing the exam check that you uploaded all of your solutions. Do not ask afterwards whether you can submit a forgotten solution.

• This pledged exam is closed notes. The only device you may access during the test is your laptop.

• Subsequent uploading after you finished the test indicates you knowingly violated the honor code.

• Any form of cheating indicates you knowingly violated the honor code.

• Do not access class examples, web solutions, or your own past assignments during the test; that is, the only code you may access or view are ones that you develop for this test.

• The only windows to be open on your computer are PyCharm and a single browser with tabs reachable from the class website.

• With regard to your functions:

• Comments including header identifying comments are not necessary.

• You should follow other class style practices; e.g., whitespace, identifier naming, etc.

• Only do what is requested.

• None of the functions should get input or produce output.

• Unless you are told to do so, your functions should not modify their parameters in any way.

• Whether a function is testable (compiles) is important.

---

Downloads (available shortly before 2PM EDT)

• Module duck.py

• Tester test2.py

• Module atad.py

• Module can.py

• Module com.py

• Module cre.py

• Module mm.py

• Module spin.py

• Module tog.py

• Module wid.py

---

 

---

 

© 2020 Jim Cohoon

Resources from previous semesters are available.