Syllabus
All times are in Eastern times.
Professor: Susan Rodger
|
|
Teaching Associate: Ms. Yesenia Velasco
|
|
Graduate TA: Danyu Sun
|
|
Graduate TA: Yubo Ding
|
|
HEAD Undergraduate TAs (UTAs)
 |
 |
 |
| Ryan Iki Labs |
Connor Murphy Consulting Hours |
Gautam Sirdeshmukh Grading |
All Undergraduate TAs (UTAs)
See pictures of the UTAs here.Lab UTAs:
|
|
Grader UTAs:
|
Topics Covered
Here is a list of some of the topics we will likely cover this semester related to Python Programming (not necessarily in this order):
- Python Data, Variables, operators
- Functions
- Conditionals (if), logic operators
- Looping structions (for, while)
- Turtle Graphics
- Strings
- Lists, Tuples
- Files
- Sets, Dictionaries
- Recursion
Course Meeting Time
Lecture:
| Section/Time | Location |
|---|---|
|
Tuesday and Thursday 10:15am-11:30am |
 Griffin Theatre in Bryan Center |
Lab Sections:
You should be signed up for one lab. Labs are on Fridays.
| Section | Time | Room | UTAs |
|---|---|---|---|
| 01 | Fri 10:15am-11:30am | LSRC A155 | Allyson Ashekun, Marisol Mata Nevarez |
| 02 | Fri 10:15am-11:30am | Bio Sci 130 | Ryan Iki, Alex Glick |
| 03 | Fri 10:15am-11:30am | LSRC A247 | Megan Fong, Kevin Alvarenga |
| 04 | Fri 8:30am-9:45am | LSRC A155 | Connor Murphy, Terence Lee |
| 05 | Fri 12:00pm-1:15pm | Physics 047 | Caroline Cornett, Isha Shah |
| 06 | Fri 12:00pm-1:15pm | LSRC A155 | Brandon Lopez, Mariam Gvenetadze |
| 07 | Fri 12:00pm-1:15pm | LSRC A156 | Adrian Doan, Aayushi Patel |
| 08/10 | Fri 1:45pm-3:00pm | Bio Sci 063 | Michael Wang, Raffay Rana |
| 09 | Fri 1:45pm-3:00pm | LSRC A155 | Benjamin Goldstein, Zia Claros |
| 11/12 | Fri 3:30pm-4:45pm | Bio Sci 155 | Aloye Oshotse, Sai Siddiqi |
| 13 | Fri 10:15am-11:30am | Soc Sci 124 | Cayla Park, Piper Epstein |
Web page
Many of the materials for this course (including this page) are available onhttp://www.cs.duke.edu/courses/fall22/compsci101/
Ed: Bulletin Board
We will use the Ed discussion board that is in our Sakai site. 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!Note that you can post anonymously to other students (not anonymous to instructors). We also encourage students to answer other student's questions and we will endorse correct answers!
Text (Required)
[We have a special version of the book just for our course, see below how to get OUR VERSION of the textbook]
How To Think Like a Computer Scientist - Learning with Python: Interactive Edition
by Jeffrey Elkner, Allen B. Downey, and Chris Meyer
How to get the book:
- You will need to sign up for an account and use a specific Course Name to get our version of the book. Look on the Sakai site under announcements for the special course name to use.
- This book is an electronic book and is free, however, we urge everyone
to give a donation from $10-$20 when you sign up. That is a great price for
a textbook! We could
have assigned a $200 textbook, but we didn't (Whew!). However, it costs money to run
the server for this electronic book so give a donation.
This book will allow you to experiment with python examples right in the
book, and also get feedback on quizzes in the book. A great book!
- Follow these instructions
Here are instructions on how to sign up for the book. - Link to runestone:
How To Think Like a Computer Scientist - Learning with Python: Interactive Edition
Pre-Lecture Work: Reading/Videos/Quizzes
You will be assigned reading from How to Think Like a Computer Scientist and/or Videos to watch before each lecture. Readings and Videos 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 will be a quiz in Sakai based on the reading and/or videos that is due when lecture starts, at 10:15am on the day of lecture. These quizzes will be listed on the course website if there is one due. That means that you must SUBMIT the quiz by 10:15am, or you will not be able to submit it.
Exception: Due to drop/add, the first five quizzes QZ01-QZ05 will all turn off on Sept. 13 at 10:15am.
You get up to 3 tries on each quiz and we use your highest score. You cannot makeup missed quizzes! We do drop some quiz points at the end of the semester.
There will also be a Sakai quiz for each programming assignment. They will have different deadlines but are intended for you to take before you start programming the assignment to make sure you understand what you are to do.
Lecture
Lecture is on Tuesdays and Thursdays at 10:15am-11:30am. This lecture will have class participation activities called WOTOs (WOrking TOgether) that must be completed during lecture.
If you are absent, even if you have a valid excuse, you must complete the class participation activities such as WOTO forms by 11:30pm the next day.
We assume you may have to miss a few lectures, so we will drop a few WOTO 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 with 94% cutoff for A; 80% = B range, 70% = C range, 60% = D.
| Labs | 10% |
| Sakai Quizzes | 5% |
| Class Participation (WOTOs) | 5% |
| Apts | 10% |
| Programming Assignments | 10% |
| APT Quizzes | 10% |
| Three Exams(12% each) and Final(14%) | 50% |
Special Accommodations for Exams
If you get special accommodations for exams (for example extra time), then send your letter to Ms. Yesenia Velasco yvelasco@cs.duke.edu DO NOT SEND YOUR LETTER to Prof. Rodger.
FINAL EXAM:
NOTE: CompSci 101 has a block exam.
Your FINAL EXAM is Thursday, December 15, 7pm-10pm, in Bryan Center, Griffith Theatre.
Labs on Fridays
You are required to attend the lab for which you've registered in taking Compsci 101. Each lab UTA takes attendance.
You will work on the lab with a partner, but each person should submit the lab form. You must submit your lab form by the first Sunday 11:30pm that follows the lab day. Thus, if you do not finish during the lab, you have two days to finish it.
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 form by the end of the Sunday that follows the lab day 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.
Your lab work will be graded on a five point scale. Pre-lab is one point, attendance is worth two points, completing the work is worth two points. If there is no pre-lab that week, then that point will be awarded for completing the lab, so each lab is worth five points.Since most of the lab points are for completing it during the week, and because we drop three labs, you cannot earn the credit for attending a lab due to any absence, even if your absence is excused.
If you miss lab, you should still do the lab for partial credit (you will not get the attendance points) and fill out the online form by Sunday. No lab submissions will be accepted after Sunday.
APTS
Algorithmic Problem-solving Testing problems (APTs) will be given throughout the semester. You will be given a description of a problem and asked to write code to solve it. You can test the code online and see the results of the automated tests. You will submit the code for grading when you decide you are ready. We do not look at the source code when grading in terms of providing feedback, we run it and test it. However, we may discuss alternative solutions to help you be effective programmers. If your source code simply checks the input with a sequence of if statements, it will receive no credit.
APTs should be submitted by 11:30 pm on the due date. A 24 hour grace period allows you to turn in APTs the next day. Late APTs are not accepted. Keeping up with APTs ensures you understand the topics we are discussing in class.
APT Quizzes
APT Quizzes are your own work. There will be two APT quizzes during the semester. When you start an APT quiz, you will have a block of time to complete it. You will have at least a three-day window to complete APT quiz problems.
If you have a SDAO letter that allows for more time on the quiz, you must submit it to Ms. Yesenia Velasco before the APT quiz so you can have the extra time.
If your source code simply checks the input with a sequence of if statements, it will receive no credit.
[Discussing the quiz] You cannot discuss the quiz with anyone until we announce that it is okay to do so. If you have a question, you can ask it as a private post on ED Discussion. The staff may convert it to a public post if it is appropriate. However, keep in mind as a quiz the staff cannot help you with it beyond clarification questions. Also we are not on at all hours of the day, so we cannot guarantee we will be able to answer your question in time.
[Protect yourself when taking the quiz] Your quiz work must be your own and must not be seen by others. Therefore, we recommend finding a secure place (stay in your room and lock the door) where no one can see your work nor do you risk talking to someone while taking the quiz.
Programming Assignments
Assignments are due at 11:30 pm on their due date, typically Tuesday or Thursday. This allows you to access consulting hours up to the time an assignment is due. A grace period of 24 hours will allow you to turn in assignments until 11:30 pm the next day with no penalty (Note: There are no consulting hours on Friday and Saturday). Assignments turned in up to 3 days after the original due date will receive a 10% penalty (if the assignment is worth X, your grade will be calculated by subtracting .1X from your score). Assignments turned in after that, but up to a week later from the original due date will have a 30% penalty (subtract .3X from your score). No assignments will be accepted after the 30% penalty (one week late).Assignment 6 and Assignment 7 are both due around the last week of class. Assignment 6 has only one grace day and cannot be turned in after that. Assignment 7 has three grace days and cannot be turned in after that.
Points on assignments will vary. Assignments typically take more time and require more thought and analysis as the semester progresses.
We use Gradescope to offer automatic testing for your assignments while you are working on them. These tests are a work in progress and constantly being improved. However, these tests are checked before they are released and considered reasonably stable. Therefore, if your submission gets an error on Gradescope, you must confirm with a Grad TA or the Teaching Associate that the error is caused by Gradescope, not the submitted code. Only after getting this confirmation will your grade get special handling when it is moved from Gradescope to Sakai. The best way to do this is through Ed Discussion or office hours.
If you are having trouble, be sure to see a UTA/TA or Professor as far before the due date as possible. Do not give up. PLEASE ask for help.
Extensions on APTs and Assignments
A 2-day extension (two days beyond the grace day) will be granted for medical reasons (see the Short-term Incapacitation Notification policy), athletes travelings, pandemic related, or other circumstances beyond your control.
- If you are sick, fill out our extension form and also fill out the incapacitation form.
- If you are an athlete traveling, (we should have a letter from you), fill out our extension form.
- You may take up to 3 free two-day extensions total on either APTs or Assignments (except the last week). If you need more than 3, you must setup a meeting with Ms. Yesenia Velasco. You must fill out the extension form in order to take them. It is best to save them for the second half of the semester if you can.
Note that this is a tough course to catch up in if you get behind. We have several items due every week. You want to make every effort to catch up quickly if you start to get behind.
Exams and Final Exam
Exams are your own work.
[Missing Exam] If you miss a midterm for an excused absence, e.g., a Short-Term Incapacitation, you'll need to make up the exam within three class days.
[Discussing the exam] You cannot discuss the exams with anyone (except the professors for this course) until we announce that it is okay to do so.
Collaboration on Programming Assignments and Exams/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. Duke Community Standard
Work on exams, final exam and APT quizzes must be your own work, you may not collaborate in completing these.
Programming assignments and APTs. In working on and completing programming assignments and APTs you may collaborate and you may use online resources. 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 for assignments and APTs 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.
Note that we have designed the APT quizzes and the course exams and final exam so that doing assignments and APTs largely on your own will help you do well on the work that must be done individually.
Individual Work Reflected in Performance
We will design exams 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.
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.
- Ed Discussion Board (on our Sakai site)
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. - Reviewer App - A Duke created tool from Prof. Stephens-Martinez and Duke undergrads to practice topics taught in this course.