• This will be a normal (not pass/fail) autograded lab with submissions via Autolab.  No limit on submissions, but please be reasonable and try to keep it at 6 or under.
• Work in a group of between 2 and 6 students.  Also, you may only work with one group (no bouncing between groups).
• If you do not know how to form a group, go to office hours (sooner is better) and the CA's will help students form into groups (who may then leave the cluster, depending on how crowded it is, and perhaps do their lab on the 3rd floor or in some other more spacious area).
• All the work for this lab must be done collaboratively.  No single-student submissions will be accepted!
• Unlike lab3, on this lab, each student will submit their own work independently.
• You may look at code, even solutions, from other members of your group, but you may not copy-paste that code, not directly copy it.  Instead, understand it, and then write your own solution using what you learned from their solution.  Even so, we understand that in this lab we would expect to see some very similar submissions between group members, and that is ok.
• If you are not reading this, then you are not carefully reading the instructions first.  This will make you very sad (it always does).
• If you have a high A already on hw3, you have an important role in this lab.  Do not just give away your answers, neither be dismissive of this process.  You should attend your group meeting and serve as a tutor of sorts, doing everything you can to help others in your group attain your level of mastery of the material.  Plus, you just might learn that there are other good ways to solve problems you already solved.  in any case, take this seriously, and don't let your group down!
• Contest1 problems will no longer count as bonus (there is no bonus on this lab).  Focus on really mastering the non-bonus material in hw3.
• We may grade for style, but if we do, it would be quite limited in scope.  We focus our style grading resources on the solo hw grading.
• Use the submit-lab4 script, and submit your work in the file lab4.py.  You can copy your hw3.py file to lab4.py to get started.

1. Logistics
   1. Group Members
      In a comment at the top of your lab4.py file, list all the group members you worked with.  List their names and andrew id's.  Do not skip this step.
       
2. Hw3 redux
   Collaboratively redo all the problems from hw3 (in the file lab4.py), sharing solutions among group members, discussing your alternative approaches, and settling on the most effective approach.  In fact, you may decide that none of your approaches were ideal, and instead collectively come up with some new and better approach.  For that, you may even talk between groups, but you may not share code between groups (only share ideas and general approaches, not code).
    
3. Optional (but strongly encouraged) review
   Optionally, but strongly encouraged:  as a group, work through some of the week 5 practice problems in preparation for hw4.

carpe diem   -   carpe diem   -   carpe diem   -   carpe diem   -   carpe diem   -   carpe diem   -   carpe diem   -   carpe diem   -   carpe diem