Haym Hirsh (Instructor)
Contact Information: For all main course correspondance, please email: firstname.lastname@example.org. This email contacts both Prof. Hirsh and graduate TAs. It will facilitate better (and hopefully quicker!) communication between you and the staff. If your issue is something you prefer to discuss only with Prof. Hirsh, his email is found on his website.
Office Hours: office hours for 4701 will be posted on the 4700 Course Calendar. Please note hours for 4701 will start with "4701: XXX"; please do not attend 4700 hours. Office hours will be updated week-to-week; check the calendar before you attend!
Quick Link to Schedule & Calendar Page
Schedule & Calendar
Prerequisites: While CS4700 is listed as a co-requisite for CS4701, you are strongly encouraged to take CS4701 only after having completed 4700, 4740, or 4780.
Online discussion: We will be using Piazza for class discussions.
Assignment submissions:You will be submitting assignments via Gradescope (Entry Code: M2PN2K)
Location: 4701 does not have a reoccuring meeting time. When there are class meetings (see course calendar), they will be in Gates G01 from 9:05 - 9:55am on Fridays. The first organizational meeting will be at 9:20am on Friday, January 25th.
Enrollment information: If you are interested in this class and are not enrolled, please get on the waitlist.
There will be a single programming project for CS 4701. The goal is to exercise knowledge you acquire from your AI courses (CS 4700 or others in our curriculum) through the development of a large-scale system. The major effort of the project should involve AI, as opposed to user-interface design, clientserver software, etc. These can certainly be part of your system, but it should not be where most of the work takes place – beware, it is very easy to get sucked into programming effort that is not central to the goal of 4701.
Students should work in teams of 3; to work in groups of other sizes, you must receive permission from the instructor.
Your project will milestones/assignments as part of the schedule. The only thing that will be graded are final submissions; however, points will be deducted if you do not follow the instructions concerning submissions for the milestones – many of them require you to do more than one thing as part of your submission, so please pay attention!
Please follow this link for the schedule, which outlines milestones/assignments for 470 and the course calendar.
The course calendar is for 4700 and 4701. Hours for 4701 will be marked "4701: XXX"; please only attend 4701 hours with 4701 questions. Specific timing may change week to week, so please check the calendar before you go to office hours.
From Cornell's code of academic integrity:
Absolute integrity is expected of every Cornell student in all academic undertakings. Integrity entails a firm adherence to a set of values, and the values most essential to an academic community are grounded on the concept of honesty with respect to the intellectual efforts of oneself and others. Academic integrity is expected not only in formal coursework situations, but in all University relationships and interactions connected to the educational process, including the use of University resources. ... A Cornell student's submission of work for academic credit indicates that the work is the student's own. All outside assistance should be acknowledged, and the student's academic position truthfully reported at all times. In addition, Cornell students have a right to expect academic integrity from each of their peers.
This course complies with the Cornell University policy and equal access laws to ensure that students with disabilities can still participate fully in this course. Requests for academic accommodations should be made during the first three weeks of the semester, except for unusual circumstances, so arrangements can be made as soon as possible. Students are encouraged to register with Student Disability Services, as we may require verification of eligibility to provide appropriate accommodations.
Everyone, the instructor, TAs, and students, must be respectful of everyone else in this class. All communication, in class and online, will be held to a high standard for thoughtfulness and inclusiveness: it may never target individuals or groups for harassment, and it may not exclude specific groups. That includes everything from outright animosity to the subtle ways we phrase things and even our timing.
If any of the communication in this class doesn't meet these standards, please don't escalate it by responding in kind. Instead, contact the instructor as early as possible; if for whatever reason you don't feel comfortable discussing something directly with the instructor please contact your advising office or the department chair.
Website layout inspired by UCSD's Compiler Construction.