Class 33 — November 14

We know you can

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

---

Students with accomodations

• Please report to Rice 128.

My new favorite number

• -8268.3982

---

Look both ways

• Back and ahead

---

Downloads — all modules have built-in testers

• Module atse.py

• Module cd.py

• Module iee.py

• Module lwv.py

• Module tobe.py

• Module xmum.py

---

Test resources

• Information sheet

• Built-in functions

• Module str

• Module list

---

Agenda

• Show your abilities

---

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

• 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 (e.g., my modules all together had less than fifty lines of code).

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

---

Test rules

• You must use my download files.

• Before you leave the room 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.

• Uploading after you leave the room means you are withdrawing from the class.

• 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.

• PyCharm can be used for developing the modules to be submitted. It cannot be used for the short answer questions.

• 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.

• Functions should not modify their parameters in any way.

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

• Any form of cheating on a test can result in expulsion from the class and the incident being referred to the Honor Committee.

---

 

---

 

 

 
   
   
   
 

© 2019 Jim Cohoon

Resources from previous semesters are available.