Syllabus
[Note: this webpage last modified Tuesday, 18-Oct-2011 23:02:11 EDT]
Always remember...
Computers are stupid! (more on this later...)
Work smarter not harder! (Actually, work smarter /and/ harder)
Table of Contents
General Information
Announcements
Purpose and Focus of Course
Grading, Assignments, and Expectations
Blackboard
Academic Integrity
Special Needs
Lecture: section 001 is TR 12:30-1:45pm, in A009 Root Hall.
section 002 is TR 11:00am-12:15pm in A009 Root Hall.
First class: Thursday August 25
Last class: Thursday December 8
Final exam: Tuesday December 13 for section 001, Thursday December
15 for section 002.
Office hours: I am generally in my office and available
most MWF's from about 8:30am-4pm. My official office hours are
Wednesdays 9:30-11:30am. My office is A-156 Root Hall.
Instructor: Jeff Kinne
Website:
http://cs.indstate.edu/~jkinne/cs151-f2011 (or browse for Jeff Kinne
on http://math.indstate.edu, or
search for Jeff Kinne on google, bing, yahoo, etc.
and find a link to the course website from my personal webpage)
GA Lab hours: We have two graduate assistants who will be in the computer science unix lab, room A-015 in the basement of Root Hall, for about 20 hours per week in total. You can go to this lab to work on your programs. The computers are unix machines, and you would need me to create a CS login for you to use them. If you are interested in that, send me an email (and then it may take about a day before you have a login to those machines). Otherwise, you can bring your laptop to work on. Either way, you can ask the graduate assistants to look at your programs, and you can work with any other CS 151 students that are there (you could use the lab as a regular meeting place to work with your classmates). The regular hours that the lab will be open are:
Wednesday 10am-2:00pm, 4pm-7pm
Thursday 9am-1pm, 4pm-7pm
Friday 8am-1:30pm.
If the GA's will not be in the lab during the normal hours for some reason (e.g., illness), I will plan to email the class list to let you know.
Required text: There is no required textbook. Readings will be assigned from online sources, and links will be made available from the syllabus and/or the course schedule website.
Information about Python: Official Python Web site, Python Tutorial, Python Language Reference, Python Language Library
Another reference: Think Python: How to Think Like a Computer Scientist by Allen Downey. This has been used as the text previously in 151 and is a good supplementary source of information. I may assign readings from the online version of this text.
There are very many online resources that you could find for learning to program with Python. You could search on youtube for videos, search the web, etc. You could look for other Python courses that have their information online, for example this one from MIT, or this one from MIT that has videos.
Another source similar to Think Python is the Python Programming Wikibook.
Software/Programming Environment:
First, DON'T PANIC! You do not need to get this software set up right now, on your own, before classes start. The first day or two of classes, I will explain what all this is about and walk you through what you need to do to get the software setup.
We will be using the Python software that can be downloaded from http://python.org/download/. You should download and install the latest 2.7.x version (currently version 2.7.2 as I write this webpage). We will also use some add-ons later in the semester; I will provide links to those when they are needed.
It is absolutely required that you have access to a working computer with Python installed that you have access to outside of class time. The biggest factor in your success in the course is how much time you spend programming outside of class. The computers in the Student Computing Center are supposed to have the Python software installed.
Online Storage: You can use http://isecure.indstate.edu to store your files when you are switching between computers. You should have enough storage to store all of your files for this course. The site allows you to upload/download.
Announcements regarding the course will be made both during class and via email to your @sycamores.indstate.edu email address. You should regularly check this email account or have it forwarded to an account that you check regularly. You can set the account to forward by logging into your indstate.edu email from Internet Explorer (the "light" version of the webmail client that opens up from Firefox or Chrome does not give the option to forward email).
This course is an introduction to programming in Python and is also the first course in computer science taken by those majoring or minoring in computer science. The primary goal of the course is that you learn the fundamentals of programming in Python. After taking this course (if you put in the time and earn a good grade), you should be able to write programs and solve problems using Python, and you should be able to read, understand, and modify Python code written by others.
Why Python? We have chosen Python as the programming language for this course because it is easier to learn than many other important programming languages such as C++ and Java. At the same time, Python is widely used in industry and a good language to know.
Example topics In addition to becoming familiar with Python, programming, and certain computer science ideas, I hope you have fun. Here are some examples of topics we will may cover and programs you will personally create!
- Pictures. We will make some of the functions that are in programs like Adobe Photoshop: grayscale, shading, zooming, rotation, ... Did you ever wonder how these are actually done in Photoshop?
- Games. We will make a few simple games. For a few of these (e.g., tic-tac-toe), we will write a computer to have the computer play the game optimally. Some potential games: tic-tac-toe, lower/higher, typing game, arithmetic game, checkers, ...
- Audio. We will make some of the functions that are provided by sound-editing programs: making echoes, changing the volume, splicing/clipping (make someone say whatever you want them to!), making music, ...
- Video. Similar to pictures and audio, we can make some simple video editing functions like fading, splicing, stick-figure animations, ...
- Internet/networking/messaging. We can make our own program to process web-pages, make a chat program, make our games internet-enabled, ...
- Animations. We can make cool animations - planetary simulation, fireworks, simple games, ...
- Drawing fractals.
- Plotting graphs (make-your-own-graphing-calculator!).
- Make-your-own-paint program.
- Encrypting messages so only you and your secret club can read the messages.
- Financial calculator.
- Computer science. The big goal of computer science is to come up with the best possible computer systems and programs to solve a program. If you want to sort a list of numbers, what is the fastest way to do this? How fast can you factor a 1000-digit number (if you can do it fast enough, you can break the encryption that is used on the internet)? Did you know that there are some problems that no computer, no matter how "super" can solve (e.g., the halting problem)? We will begin to look at how to answer these types of questions, though you'll have to take later CS courses (CS 201, 202, ...) to get into more depth.
We will not cover all of those topics, but that should give you an idea of the types of things we will look at. Hopefully there are some things there that sound exciting!
Extra practice: For some python fun, try out some online programming competition/game stuff. For example, Project Euler or The Python Challenge.
Grading, Assignments, and Expectations
The students of this course have the following responsibilities: read assigned readings before lecture, attend lecture, complete homework assignments, take exams, and complete a project. The final grade consists of:
Project: 20% of the final grade.
Homeworks: 35% total. There will be a programming homework assignment most weeks, and each will be weighted equally in adding up to 35% of the total grade. If you turn in the assignment late, I will grade it so you know how you did, but it will count as a 0. LATE HOMEWORKS WILL NOT BE ACCEPTED. NOTE: if you turn an assignment in more than one day early, I will look at it and give you feedback on any mistakes you might have - and if you resubmit before the due date I will grade the corrected version.
Exams: 35% total. We will have three exams. Each will be weighted equally in adding up to 35% of the total grade.
Class Attendance/Participation: 10% total. Attendance will be taken at the beginning of each class. Half of your attendance/participation score will consist solely of whether you were present when attendance was taken each day - the total number of days present divided by the number of lectures in the semester. The other half of your attendance/participation grade will be assigned at the end of the semester based on how attentive you were in class throughout the semester.
The class attendance grade serves the purpose of giving you credit for coming to class. You benefit from coming to class by seeing me present the new material, getting to ask questions, interacting with your classmates, keeping up on what is going on in the course, etc.
The exams serve as benchmarks of your ability to relatively quickly solve problems related to the material. This helps me assign a grade, and also gives you motivation to pay attention and keep up with the assignments.
The weekly programming homework assignments are designed to solidify your knowledge by having you write programs.
The final project will be discussed further after the first few weeks of the semester. Students will choose a larger programming project that will be completed by the end of the semester and presented to the class.
Expectations. My expectation is that an average student will spend 6-9 hours OUTSIDE of class each week (that is in addition to class time) WORKING PRODUCTIVELY/EFFICIENTLY (not just starring at the computer) to complete their coursework for this class. Some students may spend less time than this, and some students will spend more.
Classroom conduct. You may not use cell phones, iPods/music players, etc. during class. You should be civil and respectful to both the instructor and your classmates, and you should arrive to class a few minutes before the scheduled lecture so you are ready for lecture to begin on time. You may use your laptop during class if you are using it to follow along with the programming examples that are being discussed. You may not check email, facebook, work on other courses, etc. during class.
Important Note. If you wait until the last minute to begin your homework assignments, I will not be available to answer questions if you have problems. Programming assignments are notorious in the sense that oftentimes most of the time completing the assignment occurs after you thought you had the problem solved. This is called debugging (and testing), and is typically most of the effort in completing a program. So you MUST start your homework early. I suggest attempting the assignment the day it is given, or the day after, so that if you have a problem you can ask early. If you continue to have problems in trying to complete the assignment, you will have time to ask again. Working on programming assignments is much less stressful if you start early!
Grade cutoffs
I make no promise ahead of time what the exact cutoff will be in terms of the number of points to achieve an A+, A, A-, etc. These will depend on how the course goes. I will use the guidelines below in assigning letter grades. After the first few weeks, I will include a "letter grade if the semester ended today" in your grades. You can keep track of how you are doing in the course with the grades on the blackboard site for this course.
The following is roughly what I would expect by the end of the semester to earn a particular grade. This may not mean too much to you now, so you may want to check this again a few weeks into the semester.
A+/A Superior. You have a good understanding of all of the concepts. You can write programs from scratch on your own by the end, and can trace through what even modestly complicated programs do just by working it out on paper. You have a good understanding of all the aspects of the Python language we talk about in class. An A+/A student should be able to continue learning about Python (and other programming languages) on their own after completing the course.
A-/B+ Excellent. You understood most of the concepts, but may have one or two gaps. Still, you can normally write your own program from scratch and follow along in most of the program examples from class. But you may need a slight bit of guidance getting started working on a program. You also could probably keep learning more Python and programming on your own, though it will probably take you more effort.
B/B- Good. You have done well on some assignments but not as well on others. You may have trouble getting started on a program without guidance, but given hints and an outline you can normally write a correct program. Likewise with understanding a program given to you, you may need some help in understanding it. You would likely have difficulty learning more programming after the course on your own; you should be fine to keep learning in a classroom setting but should make sure to get a good start on your next CS/programming course.
C+/C/C- Adequate. You have basic understanding of Python programming but have modest gaps in your knowledge of the language syntax and how to use it effectively. You may have difficulty tracing through even a simple program that you have not seen before, but you are able to trace through a program that is similar to one you have seen before. You are minimally prepared to take another course in CS/programming. You should definitely consult the instructor of the next course you take about whether you are prepared to take the course, and you should consider repeating some of the homework assignments to continue to improve your understanding.
D+/D/D- Poor. You have some shown some ability to write programs and trace through code given to you, but you are often unable to write a program from scratch and produce programs that are not correct. You are not prepared to take another CS/programming course. You should retake CS 151 before taking CS 201.
F Failing. For much of the material in the course, you do not even know the basic information or have not turned in assignments. Most of your programs probably do not run at all, let alone correctly.
Grading Programs
For each programming assignment, I will assign a grade based on correctness and style. The exact breakdown may vary slightly from one assignment to another. In general, 60-70% of the points for an assignment will be given based on whether it is correct. The remaining 30-40% will be given based on good programming style: (i) choosing variable and function names that are descriptive/appropriate, (ii) writing code that is easy to understand and efficient, (iii) including documentation at the top of each file about what is in that file and how to use it, (iv) including documentation with each function describing what the function does (including what should be input to the function and what the function outputs), (v) documentation throughout each function describing the flow of the program. For portions of the code that are given to you, you do not need to add documentation to those parts of the code; if I give you partially completed code, you are responsible only for documenting the code that you add.
The course has a blackboard site. Click here to go to blackboard. You should see CS 151 listed under your courses for the current term. The blackboard site is used only for giving you your grades. All course content, schedule, etc. is kept on the instructor's webpage (which you are currently viewing).
Please follow these guidelines to avoid problems with academic misconduct in this course:
Homeworks: You may discuss the homework assignments, but should solve them on your own. To make sure you are not violating this, if you discuss with someone, you should DESTROY any work or evidence of the discussion, go your separate ways, SPEND at least an hour doing something completely unrelated to the assignment, and then you should be able to RECREATE the program/solution on your own, then turn that in. If you cannot recreate the solution on your own, then it is not your work, and you should not turn it in.
Note on sources: if you use some other source, the web or whatever, you better cite it! Not doing so is plagiarism.
Exams: This should be clear - no cheating during exams. The exams will be closed-book, closed-notes, no computer, and no calculator.
Projects: You should not copy code from the internet or anywhere else. The project should be your own work. It will be fairly obvious to me if you do copy code from the internet, and the consequences will be at the least a 0 on the project.
If cheating is observed, you will at the least receive a 0 for the assignment (and may receive an F for the course), and I will file a Notification of Academic Integrity Violation Report with Student Judicial Programs, as required by the university's policy on Academic Integrity. A student who is caught cheating twice (whether in a single course or different courses) is likely to be brought before the All-University Court hearing panel, which can impose sanctions up to and including suspension/expulsion. See the Student Code of Conduct and Academic Integrity Resources for more information.
Please ask the instructor if you have doubts about what is considered cheating in this course.
If you have special needs for the classroom environment, homeworks, or quizzes, please inform the instructor during the first week of classes. If you have any such needs, you should go to the Student Academic Services Center to coordinate this. See Student Academic Services Center - Disabled Student Services for more information.