|CSE Home||140 Home|
Syllabus for CSE 140: Data Programming
Welcome to CSE 140!
Computational methods permeate the sciences, engineering, and even the humanities. You need a foundational understanding of computation and practical data analysis in order to be successful in science, engineering, business, and other professions.
CSE 140, “Introduction to Data Programming with Applications”, is an introductory programming class that meets this need. You will learn to write small programs in the Python programming language to solve real-world scientific and engineering problems. This will be useful in your classes, your research, and your jobs.
In CSE 140:
Why another programming class?
UW offers a variety of excellent introductory programming classes. No one of them is best for all students. We provide a webpage to help you decide among them. That webpage also contains information about substituting CSE 140 for other UW requirements.
Some characteristics of CSE 140 include:
Many programming languages and computational tools exist to help you analyze data. These include Excel, MATLAB, R, C/C++, Java, and others. Python is a particularly good choice. It is a complete programming language. It is simple to learn and easy to write and read. You can get started with it right away. It comes with excellent libraries that will simplify your programs.
The Goals section described the high-level goals of the class. Its real objective is to teach you basic problem analysis and computational thinking, and to enable you to apply them in practice to extract meaning from a dataset. Doing so requires you to logically organize data; to design algorithms; to formulate them in a way that computers can execute; to test, identify problems, and find solutions; and to communicate the results.
The only prerequisite for the class is high school math.
The class does not assume any previous programming experience. — in fact, if you have already taken any 300-level CSE class, you are not allowed to take CSE 140.
We assume that you are familiar with basic computer usage — you are comfortable running applications, navigating the file system (say, with a tool like Windows Explorer), editing documents with a word processor or text editor, and so forth.
Any student can succeed in CSE 140. But, CSE 140 is not an easy class. To succeed requires you to work diligently, to be organized and systematic, to follow and give instructions precisely, and to ask questions when you are confused. The staff knows you can succeed, and we will help you succeed.
Class logistics: times and staff
Lectures: MWF 1:30-2:20, in JHN 075
Forum (discussion board):
Email etiquette: When using the staff email alias (but NOT the Discussion Board), it is always a good idea to attach the current version of your code to your message, so that the staff can better understand and reproduce your problem. In every message, always be explicit about the exact thing you did, exactly what the result was, and what you had expected to happen. (For example, cut and paste or attach the exact output, rather than just saying “something went wrong” or describing it vaguely.) This will enable us to help you more effectively.
Discussion Board etiquette: You should never post the code to solve a homework assignment (in whole or in part) on the class discussion board. This includes posting partial code in progress in order to ask what is wrong with it.
Lecture etiquette: We encourage you to use your laptops during class for activities that help you get the most from lecture - following along with slides, typing Python code into the interpreter, taking notes. However talking and doing activites not relevant to lecture (e.g. checking emails, playing games, surfing the web) can be incredibly distracting to those around you. Please be respectful and avoid these activities during class.
Resources: books and software
The class uses three books. Two are freely available on the Internet, and the third is $25 at the bookstore.
Readings from all three books are assigned for each lecture — see the calendar or the lecture list for details. Please do the readings before the lecture, so that we can make better use of lecture time, answer your questions about the readings, and discuss more advanced topics. There is a brief reading quiz due before lecture (see each quiz for its exact due time), as a Catalyst survey that should take you only a few minutes to complete, if you have done the reading. We expect you to complete nearly all of them and to get a score above 50% on most of the quizzes. After the quiz closes, you can view the quiz again to see your score and the correct answers.
The assigned readings are a great place to get started, but you will also need to use other materials to master Python. We also encourage you to use the many Python resources that are available on the Web. Start with the official Python documentation, whose most useful components include a beginner's guide, a tutorial, a list of all the functions built into Python, and searchable online documentaton.
Software: Please see the CSE 140 computing resources webpage for information about using Python on UW computers or installing Python on your own computer.
Tools: Philip Guo's Python Tutor lets you execute a program line by line, and it draws the variables and data structures that the program creates during execution.
After CSE 140: If you wish to learn more beyond what CSE 140 teaches you, see the self-study suggestions.
Assignments and grading
Assignment submission forms are linked to on their respective specification documents.
Your grade is determined by:
You will complete approximately one programming assignment each week. There are often some written questions on each assignment as well. In addition to the weekly assignments, there are often finger exercises that you are required do before lecture, to prime you for the lecture and prompt questions.
We urge you in the strongest possible terms to get started on your assignments early. This approach will take you much less time overall than if you try to do all the work at once at the last minute. An efficient approach is to start work, then take a break when needed. This lets your subconscious continue to work on the problem, or enables you to return to it with a fresh perspective and renewed energy. Furthermore, you will be able to ask for and receive help.
The exam grade will be determined by:
You will complete a brief reading quiz before every lecture as a Catalyst survey. See the calendar or the lecture list for details. We expect you to complete nearly all of them and to get a score above 50% on most of the quizzes.
Your participation grade includes reading quiz grades as well as participation in activities during quiz section (attendance at quiz section is expected). Instructor discretion will also be used, particularly if the course staff feels your grades do not accurately reflect your true understanding of the material. If the course staff does not know who you are, this will not reflect well on your participation grade.
If you find an error in our grading, please bring it to our attention within one week of that item being returned.
Grading on a “curve”
Grading for this class is not curved in the sense that the average is set at (say) 3.0 and half of the class must receive a grade lower than that. If everyone does well and shows mastery of the material, everyone can receive an A. If no one does well (this is unlikely), then everyone can receive a C. Furthermore, your grade is not affected by someone else dropping the class — whether that person was doing better or worse than you.
Grading for this class is curved in the sense that we do not have a pre-defined mapping from homework and exam scores to a final GPA. There is no pre-determined score (e.g., 90% of all possible points) that earns a 4.0 or a 3.5 or a 2.0 or any other grade. Rather, the staff discusses each student individually. To determine the final grade, we will ask questions like “Did this student master the material?”, and the English descriptions in the Sample UW Grading Guidelines.
Assignments are generally due at 11pm on Thursdays, although this will vary for a few assignments. Due dates will be listed on each assignment and shown on the calendar.
Each student is permitted 5 late days to use during the quarter. Each late day permits you to submit an assignment up to 24 hours late. Each late day is atomic; for example, you cannot use 8 hours of a single late day on each of three assignments.
You may wish to reserve some late days in case of unexpected emergencies (please let us know about medical emergencies such as those involving hospitalization). If you have used up your late days, a penalty of 25% off per 24-hours late will be assessed. Regardless of the number of late days you have remaining, assignments will not be accepted more than three days after the original due date. For example, an assignment originally due Thursday at 11pm will not be accepted after Sunday at 11pm.
Important: To submit work late, email email@example.com before the due date (either original or extended by a previous late day) so we know you will be submitting work late.
Integrity is a crucial part of your character and is essential for a successful career. We expect you to demonstrate integrity in CSE 140 and elsewhere. In particular, your assignments must represent your own work and understanding. Academic misconduct such as plagiarism is grounds for failing the class and can be dealt with by a University committee.
The following guidelines apply unless an assignment specifically states otherwise. If you have any questions about acceptable behavior, please ask the course staff. We will be happy to answer your questions!
You are encouraged to talk to your classmates about problem solution ideas, and you may reuse those ideas, but you may not examine nor reuse any other student's code - this includes code from students who have taken this course in previous quarters. You are not allowed to copy code from any source — other students, acquaintances, the Web, etc. (Copying is forbidden via cut-and-paste, via dictation or transcription, via viewing and memorizing, etc.) Your solution may utilize Python libraries that are available in EPD (Enthought Python Distribution). You are encouraged to use books, the Internet, your friends, etc. to get solution ideas, but you may not copy/transcribe/transliterate code: get the idea, close the other resource, and then (after enough time that the idea is in your long-term, not short-term, memory) generate the code yourself based on your own understanding.
Examining other people's code
You may sometimes find it useful to do a web search to find snippets of Python code that performs some particular operation, and paste it into your own programs. This can be an acceptable short-term strategy if it helps you get past a particular roadblock. However, you must later go back, remove the code you did not write yourself, and write the replacement on your own, from scratch. Recall that the class policy is that you must write everything that you turn in. Violating this is academic dishonesty (cheating), which can lead to a variety of negative consequences for you, including failing the class and further disciplinary action.
It is your responsibility to understand everything that you turn in. We reserve the right to ask you to explain any part of your homework assignment. If you are not able to explain what it means and why you chose it, that is presumed evidence of copying/cheating.
Later, when you are writing your own programs after you complete CSE 140, it's fine to copy others' code if the license permits such use. (Copying one or two lines is usually acceptable regardless of the license.) However, in your future career, please remember two things:
The key idea in all this is that we want you to understand. Sometimes you can achieve that by examining and understanding other people's code. But you can never achieve that by copying alone.
Re-grade PolicyIf you have a question about an assignment or exam that was returned to you, please don't hesitate to ask a TA or the instructor about it during their office hours. Learning from our mistakes is often one of the most memorable ways of learning!
If after discussing your question with a TA or the instructor you feel that your work was misunderstood or otherwise should be looked at again to see if an appropriate grade was given we ask that you submit a written re-grade request as follows:
All of the information in this document is subject to change throughout the quarter. The course staff will announce any substantive changes.
Computer Science & Engineering|
University of Washington
Seattle, WA 98195-2350
(206) 543-1695 voice, (206) 543-2969 FAX
[comments to rea]