Fall 2021 CS305
Welcome to CS305, an introduction to machine learning
Indigenous Peoples' Day
The aim of this course is to enable students to engage in a world shaped by data and computation, so that students can understand, design, apply, and evaluate computational methods that learn with experience, that solve problems based on data, and that improve their performance as they are exposed to more examples.
Students who complete this course should be able to:
There is no required textbook for this course.
There will be online and written problem-solving exercises. The exercises provide hands-on practice with new material and with problems similar to the projects. For the exercises, students work at their own pace and can get help from the instructor. Normally, exercises will be completed in teams of two students each, with teams starting an exercise during class time and completing it outside of class. Exercises are due at 11pm on their due date.
Projects help students develop a working knowledge of the concepts presented in class. Projects are due at 11pm on their due date. Instructions for turning in each project will be included with the project. We ask students to keep track of the time they spend on each aspect of the project to help us design projects for future semesters and understand course work load levels. Each project will come with a final section with which students can report the times that they spent on the various problems.
Working with a partner on projects is optional. You may work with a partner on as many projects as you like. However, you can only work with a given partner on a single project during the semester. If you want to work on projects with a partner multiple times, you must choose a different partner for each such project. Rotating through partners is a good way to build community in the class and is helpful in avoiding situations where one individual feels pressured to continue working with another. If you would like to work with a partner, you may find your own partner or you may use this shared Google document to indicate your interest in working with a partner.
Many of the projects will be challenging. You should keep in mind that programming often consumes more time than expected. Start your projects early! This will give you time to think about the problems and ask questions if you hit an impasse.
Exercises and projects are due at 11pm on their due dates. It is beneficial to student learning for course work to be completed regularly throughout the semester. Since much of the material in the course builds off of previous content from earlier in the course, it is helpful to keep on schedule so that students have the necessary background to engage with the material as it is presented in class together with their classmates.
Sometimes, however, prioritizing completion of an assignment by the deadline may not be the right personal choice for you. To encourage you to learn from the assignments while also affording flexibility when it benefits your health and well-being, you may use either of the following mechanisms to submit late assignment (exercise and project) work without penalty:
The above extension mechanisms are subject to the following limitations:
We believe that collaboration fosters a healthy and enjoyable educational environment. For this reason, we encourage you to talk with other students about the course material and to form study groups.
For projects, students are allowed to discuss the problems with other students and exchange ideas about how to solve them. However, there is a thin line between collaboration and plagiarizing the work of others. Therefore, we require that each student must compose their own solution to each project. You may discuss strategies for approaching the programming problems with your classmates and may receive general debugging advice from them, but you are required to write and debug all of your own code. Furthermore, you should never look at another student's code. For example, it is OK to borrow code from a textbook, from materials discussed in class, and from other sources as long as you give proper credit. However it is unacceptable and constitutes a violation of the Honor Code (1) to write a program together (with someone else) and turn in two copies of the same program, (2) to copy code written by your classmates, (3) to read another student's code or (4) to view projects and solutions from previous terms of CS305.
In keeping with the standards of the scientific community, you must give credit where credit is due. If you make use of an idea that was developed by (or jointly with) others, please reference them appropriately in your work. It is unacceptable for students to work together but not to acknowledge each other in their write-ups.
For exercises, you will work with a partner as part of a two-person "team". Partners will be assigned by the instructor, so that each student works with different partners throughout the semester. The two team members must work closely together on the exercise and turn in a single submission of their exercise solutions for the team. The grade received on such a submission will be given to both team members.
For projects, you are encouraged but not required to form a two-person "team" with a partner. The two team members must work closely together on the project and turn in a single submission of their project solutions for the team. The grade received on such a submission will be given to both team members. When partnering for projects, you can only work with a given partner on at most one project during the semester. If you want to work with partners on multiple projects, which is encouraged, you must choose a different partner for each project. Rotating through partners is a good way to build community in the class and is helpful for avoiding situations where one individual feels pressured to continue working with another.
Team efforts on exercises and projects are subject to
the following ground rules:
The work must be a true collaboration in which each member of the team will carry their own weight. It is not acceptable for two team members to split the problems in the exercise/project between them and work on them independently. Instead, the two team members must actively work together on all parts of the exercise/project. In particular, almost all programming should be done with the two team members working at the same computer. It is strongly recommended that both team members share the responsibility of "driving" (i.e., typing at the keyboard), swapping every so often.
The grading for this course is mandatory credit/non. The reason for the use of this grading model is to focus attention on learning, rather than grades, and encourage innovation, risk-taking, and pursuit of your machine learning passions. You will receive all the same grading feedback and scores on assignments and assessments as you would in any course, but your transcript will indicate either CR (credit) or NCR (no credit).
Your final grade will be based on a weighted average of the following components:
At the end of the semester, we will compute a weighted average for each student and assign letter grades. In general, the mapping from numerical score to letter grades looks like this: >= 93.33 is an A, >= 90.00 is an A-, >= 86.67 is a B+, >= 83.33 is a B, >= 80.00 is a B-. >= 76.67 is a C+, >= 73.33 is a C, >= 70.00 is a C-, >= 60.00 is a D and < 60.00 is an F.
Depending on the overall performance of the class, we may adjust this mapping.
If a student receives a final grade of "C" or higher, i.e., greater than or equal to 73.33 in the abovementioned mapping, then the student will receive credit. If a student receive a final grade of "C-" or lower, i.e., less than 73.33 in the abovementioned mapping, then the student will receive no credit.
All programming in CS305 will be done using the Python programming
language. We will make heavy use in the course of Python libraries such as
As software, we will use Anaconda
with Python version 3.8 or higher.
Code will be developed and shared in the course using Jupyter
There is a CS305 Google Group named
This group has several purposes. We will use it to make
class announcements, such as corrections to projects and
clarifications of material discussed in class. We encourage you
to post questions or comments that are of interest to students
in the course. Please do not post Python code in your messages
on the Google group! The instructor will read messages
posted to the group on a regular basis and post
answers to questions found there. If you know the answer to a
classmate's question, feel free to post a reply yourself. The
course group is also a good place to find people to join
a study group. You should plan on reading group messages
on a regular basis.
Here is a form for providing anonymous feedback to the instructor. You must be logged in to a Wellesley account to use the form, however neither your email address nor any other identifying information will be recorded.
If you have a disability or condition, either long-term or temporary, and need reasonable academic adjustments in this course, please contact Accessibility and Disability Services (ADR) to get a letter outlining your accommodation needs, and submit that letter to me. You should request accommodations as early as possible in the semester, or before the semester begins, since some situations can require significant time for review and accommodation design. If you need immediate accommodations, please arrange to meet with me as soon as possible. If you are unsure but suspect you may have an undocumented need for accommodations, you are encouraged to contact ADR. They can provide assistance including screening and referral for assessments.
Disability Services can be reached at email@example.com, at 781-283-2434, by scheduling an appointment online at their website www.Wellesley.edu/disability , or by visiting their offices on the 3rd floor of Clapp Library, rooms 316 and 315.
Pursuant to Wellesley College policy, all employees, including faculty, are considered responsible employees. That means that any disclosure of discrimination, harassment, or sexual misconduct to a faculty member will need to be shared with the College's Director of Non-Discrimination Initiatives / Title IX and ADA / Section 504 Coordinator (781-283-2451; firstname.lastname@example.org). Students who do not wish to have these issues disclosed to the College should speak with confidential resources who are the only offices at the College that do not have this same reporting obligation. On campus, confidential resources include Health Services (781-283-2810 available 24/7), the Stone Center Counseling Services (781-283-2839 available 24/7) and the Office of Religious and Spiritual Life (781-283-2685). You should assume that any person employed on campus outside of these three confidential offices has an obligation to share information with Wellesley College through the Office of Non-Discrimination Initiatives.