CS17700 Fall 2015

Welcome to CS17700: Programming with Multimedia Objects.

• An introduction to programming using Python

• Aditya Dhingra
• Jeremy W Lehman
• Avirbhaw Rakesh
• Manmohit Sehgal
• Mark Williams

Time: 04:30 pm-05:20 pm - Tuesday and Thursday
Location: FRNY G140

Class: We will use iClicker. If you miss more than 4 classes, you will lose 2.5% of the total course score.
Recitation: We will take attendance in the recitations. If you miss more than 4 classes, you will lose 2.5% of the total course score.
Labs: You are already being graded by submitting your lab. You should be present in all labs for your submissions to be graded.

Python Programming: An Introduction to Computer Science (Second Edition) John Zelle, ISBN 978-1-59028-241-0-9, Franklin, Beedle & Associates Inc., 2004.

Buy it on Amazon

We will be using Python 3.4.2 in this semester. You can download it from:

https://www.python.org/downloads/release/python-342/

You will need this graphics library in the graphics examples if you want to work with your own computer.

http://mcsp.wartburg.edu/zelle/python/

Purdue Emergency Preparedness
Course Policies

We will be using Piazza to facilitate discussions for the class. See the top sidebar link for instructions on Piazza. Once you joined the class, you can use the link on the lower sidebar link and simply log on.

Sign up by visiting CS17700 on Piazza.

The Piazza discussion forum is intended only for technical discussions related to the class. That is, questions about labs, assignments, lectures, language features of Python, etc. It is NOT to be a place for flaming or complaining. If you have a problem with something in the class, please talk to your Lab Instructor, Recitation Instructor, Instructional Coordinator, or Lab Administrator.

You can post public questions visible to the entire class or private questions visible only to the instructors. You may post questions including small snippets of code (using the <code> tag), but do not post extensive pieces of code publicly.

(1) You should direct questions concerning a lab or project to a staff member, rather than a classmate. But, when you come to us, be sure that you have specific questions and can show evidence that you have spent some time on your own attempting to solve your problem.

(2) This is a four credit hour class. Purdue University regulations state that we may ask as much as 3 hours of your time per credit hour in an average week. Accordingly, you should plan on spending an average of TWELVE hours per week on this course. We are aware that this represents a large part of your available time, but we feel that it is worth it!

(3) ATTENDANCE IN CS 177 IS MANDATORY! You should plan on attending EVERY lecture, EVERY recitation, and EVERY lab meeting. Past experience has shown us that students who attend lecture, recitation, and lab regularly do better on labs, assignments, and exams – even those who think they already know the material or who think they can learn it on their own. Missed labs and recitations CANNOT be made up, unless the absence is excused. Lab and recitation absences MAY be excused for reasons of serious illness, family emergency, or official university commitments, but only if appropriate documentation is provided to your Lab Instructor (for lab) or your Recitation Instructor (for recitation). For planned absences (band trips, other course field trips, etc.), you must inform your instructor ahead of time, or the absence will not be excused.

(4) You should read the material in the textbook according to the class syllabus. In most cases, you will read about a concept in the book, then we will cover it in class, then you will use it in lab, then it will be discussed in recitation, then it will be used on a project, and finally it will be tested on an exam.

(5) Computers may become heavily loaded as a project deadline nears. Waiting until the last minute to work on your project is dangerous! Our CS 177 policy is NOT to extend deadlines unless most available workstations are unavailable for an extended period (like 10-12 hours) near the end of a project.

(6) NO LATE projects or lab assignments will be accepted. There will be NO EXCEPTIONS to this rule except under extreme circumstances approved in advance by your Recitation Instructor or Lab Instructor. Failure to turn in a project results in a loss of all the points allocated for the project. The same holds true for a lab assignment.

(7) For each project, students are told to direct all project-related questions to one of the CS 177 Recitation Instructors using e-mail. That Recitation Instructor will answer all questions about the project and will post general interest questions and answers to the purdue.class.cs177 news group. We can answer questions asking for clarifications on the project. We can address problems that arise if the project handout is unclear or does not adequately address an area the project covers. However, that person should not be asked questions specific to your own individual program. Those kinds of questions should be taken to a CS 177 consultant or your own Recitation Instructor.

(8) In most cases no credit will be given for programs that do not compile (that is, execution is suppressed due to compilation errors). Programs which execute but are not correct or complete will be considered for partial credit. To receive full credit, your program must produce correct results, be well-designed, and be efficient.

(9) IMPORTANT – Requests to re-grade a lab or a project must be sent to the CS 177 Instructional Coordinator NO LATER THAN ONE WEEK AFTER THE POSTING OF THE GRADE IN BLACKBOARD.

(10) WE ALWAYS WELCOME YOUR CONSTRUCTIVE COMMENTS. Please do not hesitate to bring any shortcomings to our attention.

All CS 177 course work must be done individually. We encourage discussion of any CS 177 topic including ideas about how to do the projects. But, under no circumstances will exchange of code via written or electronic means be permitted between CS 177 students. It is considered dishonest either to read someone else's solution or to provide a classmate with a copy of your work. Do not make the mistake of thinking that superficial changes in a program (such as altering comments, changing variable names, or interchanging statements) will avoid detection. If you cannot do the work yourself, it is extremely unlikely that you will succeed in disguising someone else's work. We are adamant that cheating in any form will not be tolerated. Even the most trivial assignment is better not done than if you cheat to complete it.

All students in CS 177 must read and “sign” the Purdue University Department of Computer Science Academic Integrity Policy. This is available on the CS Department Website at the Computer Science Personal Portal. Click on the link “Academic Integrity Policy”. You will need your Purdue Career Account login and password to access this page. There, after reading the policy, you will indicate that you have read and understand both the policy and its consequences. There is also information about some implementation details.

IMPORTANT: CS 177 students will not be allowed to take Exam 1 if they have not read and accepted this policy.

Penalties

In CS 177 a first instance of academic dishonesty will result in a zero for that assignment plus a letter grade deduction at the end of the semester.

A second instance of academic dishonesty will result in a grade of F.

In accordance with the Purdue University Department of Computer Science Academic Integrity Policy, any instance of academic dishonesty on an exam, project, or lab assignment will be reported to the Dean of Students Office.