This course is governed by an academic honesty policy that enforces academic integrity (e.g. no cheating). See https://academicintegrity.ucsd.edu/forms/form-scholarship-agreement.html for an overview of what constitutes an academic integrity violation in a CSE course. Assignments will be clear on when they are intended to be collaborative versus individual work.
You can submit programming assignments up to 24 hours late for a 20% deduction. Reading assignments cannot be completed late for credit.
Lecture notes will be posted in advance of each lecture, along with a (short) online quiz. To get credit for a reading quiz, you need to get at least half the questions right. The quiz might address the current reading or any past reading.
We’ll be using clickers for in class exercises, and you’re expected to participate (it’s a portion of your grade). You can buy them at the bookstore, and you can use either version.
Note that the clicker id may be an A followed by 7 alphanumeric characters; the student id should be one longer. To register your clicker once you have it, go to https://www1.iclicker.com/register-clicker/ and fill out the form. Your student id should look like A12345678 (an A followed by 8 digits), and you should use your @ucsd.edu email address. You don’t need to re-register if you’ve registered at https://iclicker.com before.
There’s evidence that sitting and listening passively to lecture probably isn’t the best way to teach or learn science. I like to ask questions during class, give you a chance to discuss them, and attach some value to your engagement. We’ll use clickers to do this.
Typically, there will be 1-2 clicker questions per lecture, based on what we’re discussing or working through. Sometimes you’ll have to read some code and pick the code that does the right thing, or choose a strategy for a program, or figure out what’s wrong with a program on the board. I’m asking for participation, not correctness – sometimes a clicker question won’t have a right answer or will be to stimulate discussion.
Your proportion of the 10% of clicker points is simply the proportion of clicker questions you answer with 5 missed days worth of clicker points allowed. You are not encouraged to miss 5 lectures; this policy is mainly intended to capture in a broad and fair way various issues with logistics, clicker technology, and reasonable absences.
The formula for calculating this is:
Math.min(totalClickerLectures - 5, yourClickerPoints) / (totalClickerLectures - 5)
You get a clicker point for each day you participate in clicker questions in lecture (usually doing one or two is sufficient). So yourClickerPoints (which is the number reported in GradeSource) is essentially the number of days you showed up and clicked.
The formula above produces a number between 0 and 1, which is the proportion of the 10% of your score you’ll get from clickers. The most likely value for totalClickerLectures is in the high 20’s, but this could change due to cancellations, altered schedules, etc.
You will have a number of programming assignments in this course. Each will be released about a week in advance of its due date. Due dates will be clearly posted on each asssignment, which will usually (but not always) be on Tuesdays by 11:59pm. Assignments will use ACMS accounts and machines, and we’ll do handin via a service called Vocareum; an early assignment will come with instructions for getting these accounts set up.
Assignments will clearly post when they are to be done individually, vs. being done in pairs.
Your grade will consist of:
(10%) Participation via clickers
(10%) Reading quizzes
(45%) Programming assignments
(15%) Midterm exam
(20%) Final exam
In addition, you must get half of the points on the final exam to pass the course.
Above 90% is guaranteed some kind of A, above 80% is some kind of B, and above 70% is some kind of C. These thresholds may be lowered, but won’t be raised.