Professor: Susan Rodger
|
|
Graduate TA: Barrett Ames
|
|
Graduate TA: Bo Shi
|
|
HEAD Undergraduate TAs (UTAs)
| Elizabeth Dowd | Ademola Olayinka | Ellen Yuan |
 |
 |
 |
All Undergraduate TAs (UTAs)
See pictures of the UTAs here.
|
|
Course Meeting Time
Lecture:
| Section/Time | Location |
|---|---|
|
SEC 001: Tuesday and Thursday LSRC B101 10:05am-11:20am Lecture UTAs: |
|
|
SEC 002 : Tuesday and Thursday LSRC B101 1:25pm-2:40pm Lecture UTAs: |
|
Lab Sections:
You should be signed up for one lab. Labs are on Wednesdays and Thursdays. Labs start August 31, the first week.
| Section | Day/Time | Room | UTA |
|---|---|---|---|
| 01 | Wed 11:45pm-1:00pm | Bio Sci 130 | Benyamin Yang, Elizabeth Dowd |
| 02 | Wed 1:25pm-2:40pm | Perkins Link 071 | Ellen Yuan, Laura Guo |
| 03 | Wed 3:05pm-4:20pm | LSRC A156 | Sarah Cogan, Adia Coley |
| 04 | Wed 4:40pm-5:55pm | Soc Sci 119 | Austin Gartside, Ethan Lampert |
| 05/15 | Wed 6:15pm-7:30pm | Allen 326 | Jake Sumner, Stephanie Ding |
| 06 | Thu 11:45-1:00pm | Soc Sci 126 | Hari Rajan, Alexi Kontos |
| 07 | Thu 3:05-4:20pm | Gray 220 | Ashka Stephen, Isabella Jones |
| 08/09 | Thu 4:40-5:55pm | LSRC A156 | Andreas Santos, Tevin Brown |
| 11 | Wed 11:45-1:00pm | Friedl Bldg 126 | Ademola Olayinka, Alex Park |
| 12 | Wed 1:25-2:40pm | Gross Hall 104 | Catherine Grasse, Spencer Steinberg |
| 13 | Wed 3:05-4:20pm | Bio Sci 063 | Diane Hadley, Matthew Feng |
| 14 | Wed 4:40-5:55pm | Soc Psych 126 | Sam Curtis, Samantha McLendon |
| 16 | Wed 6:15-7:30pm | Soc Psych 129 | Frank Wang, Tahia Emran |
| 17 | Thu 3:05-4:20pm | Soc Sci 311 | Divya Koyyalagunta, Njideka Nwosu |
| 18/19 | Thu 4:40-5:55pm | Soc Psych 129 | Mitchell Gladstone, Archana Ahlwat |
Backup UTAs: Richard Asfour, Clara Forrestal, Rachel Buchanan, Gabriel Valladares
Web page
Many of the materials for this course (including this page) are available onhttp://www.cs.duke.edu/courses/fall16/compsci101/
Bulletin Board
THE PIAZZA SITE will be created the first week of class. We will use Piazza for the class bulletin board. Look here for announcements, hints, and information relevant to this class. You can also post questions here. You should check this page at least once a day!This site will be created around Aug 28-30. If you are registered for the course, you will automatically be added to it. If you add the course after we create it, you will need to add yourself to it.
Note that you can post anonymously. We also encourage students to answer other student's questions and we will endorse correct answers!
Text (Required)
How To Think Like a Computer Scientist - Learning with Python: Interactive Edition 2.0
by Jeffrey Elkner, Allen B. Downey, and Chris Meyer
How to get the book:
- This book is an electronic book and is free, however, please note that we
could have assigned a $200 textbook, but we didn't (Whew!). However, it costs money to run
the server for this electronic book.
This book will allow you to experiment with python examples right in the
book.
Strongly encourage giving a donation to help support the book, we suggest at least $15 . - You will need to sign up for a free account and use a specific code to get our version of the book. Look on the Sakai site under announcements for the code to use.
Reading/Reading Quizzes
You will be assigned reading from How to Think Like a Computer Scientist. Readings will be posted on the calendar page for each lecture on the course website. In general you should read the text to be prepared to participate actively in class. If you've looked at material before it's discussed in class you'll get much more out of the class discussion.
There may be either reading or knowledge quizzes on Sakai due at 10am on the day of lecture. These reading quizzes will be listed on the course website if there is one due. Quizzes on Sakai must be completed by 10AM on the day of lecture, you will not be able to complete them after 10:00 AM on the day they are due. You cannot makeup missed quizzes!
Lecture and Classwork
In each class the active lecture is designed to provide important and useful information that will allow you to learn concepts and complete the assignments that you are working on (APTs and programming assignments). Class typically includes questions that you may complete individually or in groups, this class work contributes to your final grade, but more importantly being an active participant in class will help foster community in class as well as help you learn and master the concepts related to programming and computer science. Bring a laptop to class if you have one.
If you fill out the lecture google forms outside of class or not near the time of the exercise we do in lecture, you will not receive credit.
If you are absent, even if you have a valid excuse, you cannot make up the lecture class participation, because you were not there to participate! We assume you may have to miss a few lectures, so we will drop a few lecture points at the end of the semester. Missing more than a few lectures may impact your grade.
Grading
The table below shows how the categories of work done in class are used to calculate your grade in Compsci 101. Grading is done on an absolute, but adjustable scale. This means that there is no curve. Anyone earning 90% or more of the total number of points available will receive a grade in the A range (A+,A,A-); 80% = B range, 70% = C range, 60% = D. This scale may go down, i.e., we could make the A- cut off at 88%. However, the scale will not go up. So if everyone gets 90% or above, then everyone will get an A- or above (this has not happened at Duke, but could!)
You cannot earn a grade above A- without earning a grade of 85% or above on the final exam.
| Labs | 10% |
| Reading Quizzes | 5% |
| Class/Group work | 5% |
| Apts | 10% |
| Programming Assignments | 10% |
| APT Quizzes | 5% |
| Two Midterm Exams | 30% |
| final exam | 25% |
The tests and final exam will be closed-book.
FINAL EXAMS:
- SECTION 001, (lecture meets Tues/Thur 10:05am)
Your FINAL EXAM is Monday, Dec 19 2PM-5PM - SECTION 002, (lecture meets Tue/Thur 1:25pm)
Your FINAL EXAM is THURSDAY, Dec 15, 7PM-10PM
Labs
You are required to attend the lab for which you've registered in taking Compsci 101. You will work with a partner during lab. You will submit lab work electronically. Please bring a laptop to lab if you have one.
You will submit the lab work, either alone or as part of a pair as dictated by the lab. You must submit your work by Sunday 11:59pm of that week.
If you cannot attend your lab section in a given week, you are expected to still complete the material on your own and submit the lab by the end of the Sunday of that week for partial credit. No lab submissions will be accepted after Sunday. It is important to do each lab as they provide practice for the concepts you will be learning.
You will work in groups of two during lab. At least one person from each pair must bring a laptop to lab each week. When working in a pair you must be present and an active participant in the lab for your name to be included in submitting lab work. Your lab work will be graded on a 4 point scale and based on how complete the answers are: complete and well done, reasonable effort but not well done/not complete, minimally complete, not done. If you are not in lab, but complete the lab on your own, you can earn three out of the four points, i.e., one point is for attending the lab and working there.
There are no exceptions, if you miss lab you can only earn up to 3 of the 4 points for the lab. We will drop a few points at the end of the semester, so if you miss a few labs you should be fine as long as you turn them all in.Collaboration on Programming Assignments and Tests/Quizzes
You must adhere to the Duke Community Standard in all the work you do in Compsci 101. Please be sure you've read the standard carefully.
Work on tests, final exam and APT quizzes must be your own work, you may not collaborate in completing these.
In working on and completing programming assignments and APTs you may collaborate and you may use online resources. However, we have designed the APT quizzes and the course midterms and final so that doing assignments and APTs largely on your own will help you do well on the work that must be done individually. Working with someone is a good way to learn about programming and to succeed. Copying someone else's program is not a good way to learn the material and to succeed in doing well in Compsci 101. We ask that in helping others you help them by discussion rather than by simply sharing code. Although sharing your code by simply providing it to others is not considered a violation of Duke's community standard in Compsci 101, we think it goes against the spirit of doing work collaboratively and learning together that we are working to create in the course.
README form
When you complete a set of APTs or a programming assignment you must turn in a README form that will ask you to provide information including: how much time it took you to complete the assignment, your thoughts about the work you did and the assignment, a list of people you worked with or consulted with and a list of those people you helped in completing the assignment, a list of online/web resources you used outside of the the course website and text book. Completing the README when you turn in these assignments is required, and your assignment will not be considered as complete and on-time unless the README form is turned in on-time.
Individual Work Reflected in Performance
We will design tests and APT quizzes so that a thorough understanding of APTs and assignments will ensure that you can succeed in these assessments that must be completed individually and without collaboration or assistance. Although you may collaborate and discuss programming assignments and APTs, we think that you will not be able to program well on your own and you will not succeed in doing well on the assessments unless you have worked by yourself with significant effort in completing the programming assignments.
Late Policy: Assignments and APTs
Assignments and APTs are typically due on Tuesdays or Thursdays. To be considered ontime, submission must be received by 2:00 AM of the next day, so that you have two hours after midnight on the day the assignment is due for it to be considered as turned in ontime.
Assignments received up to one-day late will receive a 10% penalty. Assignments turned in up-to one week late will receive a 30% penalty. No assignments are accepted after one week. STINFs and excused absences can effect the one day late penalty and provide three days of no penalty, after that the 30% penalty will be applied. If you completed a STINF or think you have a valid excuse, you must fill out the extension form on the forms page to receive the three days of no penalty.
Web Sites This Course uses
We will use several course web sites for this course.
- CompSci 101 Course web site
The syllabus, class notes, readings, assignments, apts, labs and other resources are available here. - Sakai
Grades, reading/knowledge quizzes and announcements will be here. - Runestone Interactive Books (gmail or facebook login required)
The course textbook is online and interactive! It includes practice exercises that we may assign during the semester. The code you use to sign up for the book is posted as an announcement on Sakai. - APT site APT Problems will be hosted at this site.
- WebSubmit (standard Duke NetID required)
The place to submit your programming projects. Note, this site is an alternative to using Eclipse directly. - Piazza Discussion Board (standard Duke NetID required)
If you have any questions about the course, post your questions here because it is seen by all the course staff as well as all the students. - Python Tutor (no log in required)
This site is a useful tool for seeing exactly what your program is doing when it is run. Additionally, you may want to paste your code there to help debug more complex issues --- always make sure your most current version is saved on your computer within Eclipse.