CSE105

Instructors

Professor Daniele Micciancio
Office Hours
When:	Usually Mondays 10-12; see Google calendar above.
Where:	EBU3b (CSE) 4214

Professor Mia Minnes
Office Hours
When:	Usually Mondays 12-2; see Google calendar above.
Where:	EBU3b (CSE) 4206

Contact

To contact the CSE 105 instructional team, please post on Piazza. Confidential questions to the instructional team can be made as "private posts".

Office hours and any changes in schedule will be posted on Google calendar above.

Teaching Assistants and Tutors

TAs

Marco Carmosino

Benjamin Cosman

Elaine Hwang

Aditya Suresh Kumar

Justin Lazarow

Edward Wong

Kevin Yin

Tutors

Alec Brickner

Abhishek Goyal

Madhu Krishnan

Lucy Li

Grant Lin

David Luu

Purag Moumdjian

Becky Zhou

Contact

TAs and tutors will be available for group office hours as posted on the Google calendar above. There will also be some 1-1 tutoring slots available for sign-up (first come first serve) TBA.

The instructional team is regularly available on Piazza. Confidential questions to the instructional team can be made as "private posts".

Course Description

Welcome to CSE 105! This course addresses fundamental questions about computing:

• What problems are computers capable of solving?
• What resources are needed to solve a problem?
• Are some problems harder than others?

You'll see how the answers to these questions shape many aspects of computer science. You'll also be developing and practicing essential skills of computer scientists, including writing mathematically sound and clear arguments (from formal proofs to more informal explanations), using visualization and testing tools, and dabbling in a new programming language.

In this course, we will explore what it means to be "computable". We begin with a very simple model of computation, and work our way to the most powerful, the Turing machine, named after Alan Turing, who formalized the notion of "algorithm" in this last model. You'll also learn about the relationship of these models to some essential tools in a computer scientist's toolkit, such as regular expressions and context-free grammars. Finally, you'll develop your technical communication skills in writing formal arguments and proofs.

See also: Course Catalog description of CSE 105.

The lectures for this course meet three times a week (for Sections A and C) or twice a week (for Section B) and will include many opportunities for active learning using clickers, peer instruction, and opportunities to ask questions to the instructor, TAs, and tutors. Podcasts for each lecture section can be found at podcast.ucsd.edu. There will also be weekly discussion sections which will review the week's concepts and help you get started on homework (see schedule). Seven homework assignments will stretch and deepen your understanding of the concepts: you will submit these assignments and receive feedback on them via gradescope. Additional (optional) programming assignments will give you the opportunity to implement the theory with Haskell. These assignments will be submitted through scripts on ieng6. There are three 50-minute exams during the quarter and a final exam during exam week. Gradescope will also be used to distribute exam grades and feedback. Piazza, our discussion and announcements board, will also be used for announcements and distributing some files.

Course grades will be computed using the following weights.

Grading
Exams     MAX ( (Final 26%, Exam 1 13%, Exam 2 13%, Exam 3 13%), (Final 39%, Best Exam 13%, Second Best Exam 13%))	65%
Homework     5% for each of top six homework assignments aka "drop the lowest HW score"	30%
Class Participation and Preparation     MAX ( Clicker score, Discussion Attendance, Haskell projects )	5% (or more)

After your weighted average is calculated, final letter grades will be assigned no stricter than the following grading scale, except that you must get a passing grade on the final exam in order to pass the course (regardless of total percentage):

A	B	C	D	F
90 - 100	80 - 89.9	70 - 79.9	60 - 69.9	< 60

Plus and minus to a letter grade will be assigned at the instructor's discretion. This includes but is not limited to: consideration of improvement over the course of the quarter, active class participation, and natural "breaks" in the distribution of scores. We may adjust the above scale to be more lenient (depending on the overall class performance), but we guarantee that we will not adjust the scale to make it harder to get a better grade.

Standards for evaluation Your homework and exams in this class will be evaluated not only on the correctness of your answers, but on your ability to present your ideas clearly and logically. You should always explain how you arrived at your conclusions, using mathematically sound reasoning. Whether you use formal proof techniques or write a more informal argument for why something is true, your answers should always be well-supported. Your goal should be to convince the reader that your results and methods are sound.

Exam policies

• Exams will include all material covered up to the day of the exam, unless otherwise noted.
• No makeup tests will be given.
• You should go to the examination room for your class section.
• You must sit in your own assigned seat for exams, as specified in posted seat maps before each exam.
• No electronic devices, books, or written notes are allowed for these examinations except for one (double-sided) handwritten standard sized (3 inch by 5 inch) index card.
• Sharing of index cards during the exam is not allowed, and will be considered a violation of academic integrity.
• You must have a score of at least 50% on the final exam to pass the course.
• The final exam will cover all material from the whole quarter, though more emphasis will be given to material covered after the last in-class exam.

Homework policies

• Homework is due roughly every week, the schedule and assignments will be posted below.
• Homework is due at midnight on the day it is due. No late submissions will be accepted for any reason.
• You may solve and write up each of the seven homework assignments in groups of size one to three . Your homework partners can be enrolled in any of the three Fall 2016 sections of CSE 105, and you can change your homework group with each assignment.
• Members of a group are responsible for all parts of any assignment with their names on it. Problems should be solved by the group, and not divided up between group members. It is highly recommended that each member of the group try solving the problems individually on their own, before meeting as a group. Each member of a group should participate in discussions about each problem. To encourage full homework participation by all members, each exam will include one problem similar to a homework problem from the two most recent assignments prior to the exam.
• Homework must be typed and the names of all group members should appear at the top of every page of the homework submitted. The homework should be submitted via gradescope by a single representative of the group. For step-by-step instructions on scanning and uploading your homework, see this handout: make sure to select all group members' names when you "Add Group Members" to the submission; it's not enough to just list their names on the page.
• You may submit updated versions of your homework up until the deadline.
• Depending on staff support, one or more of the homework problems on a graded assignment may be graded only for completeness and fair effort.
• When computing the homework portion of the course grade, the lowest of your seven graded homework scores will be dropped and the average computed using the remaining six assignments.
• Homework must be completed through the independent fair effort of the group members. You should not look for answers to homework problems in other references (i.e. anything other than the course textbook and class notes) or other sources (e.g. wikipedia, Internet, discussion groups). Discussion of the homework problems should be heard only by group members from a single group, unless it is in instructor or TA/tutor office hours. Not giving an acknowledgment of any other source you use is academic dishonesty, and will be treated as such. As well, students should not share answers to homework problems with others or on the internet.

Class Participation and Preparation

Solving new and challenging problems and regularly working with the concepts in this course is the best way to learn the material. There will be ample opportunity to do this throughout the quarter, and the Class Participation and Preparation component of your grade gives credit for the work you do in this regard. While we highly recommend actively participating in class, attending discussion, and completing the Haskell projects, we know your class preparation time is limited. Therefore, completing the work in ANY ONE of these categories will satisfy your class preparation requirement. Note that your class preparation grade component is the MAX of your clicker participation score, your discussion attendance score, and your Haskell project score; it is not their SUM. Moreover, your three highest-scoring Haskell projects will each be weighted 2% towards your final score: three perfect scores will earn you 6% (a 1% bonus in addition to the participation score).

• You must register your iClickers on iClicker by the end of the second week (October 7, 2016).
• Clicker questions will be graded for participation only and not correctness of the response, unless otherwise noted.
• Full credit for clicker points for a given day will be awarded for clicking in at least 80/% of the time that day.
• One week's worth of clicker participation points will be automatically dropped: that is your three lowest lecture participation days if you're enrolled in Lecture A or Lecture C, or your two lowest lecture participation days if you're enrolled in Lecture B.
• Forgetting your clicker counts as missing a class, so please remember to bring it!
• New! You must attend the lecture section in which you are enrolled to earn participation credit.
• Discussion sections (scheduled on Fridays) are designed to ease your start on the homework problems or to review material for an upcoming exam. We highly recommend that you attend one of the five Friday discussion sections each week. Each will cover identical material, and you need only attend one session fully and submit your discussion worksheet to get credit for that week.
• New! The discussion section scheduled for Tuesdays will be dedicated to answering Haskell related questions, specifically for the Haskell-based programming projects. Participation in the Tuesday discussion sections does not count towards the discussion participation score. All students are welcome to attend the Tuesday discussion section.
• One discussion section grade will be dropped from your overall discussion participation grade.
• There are four Haskell-based programming projects. The lowest score will be dropped and the top three projects will each be weighted 2% towards the final score, towards a maximum score of 6%.

Regrades

• All grades are fixed 3 days after being reported in gradescope.
• Regrade requests should be made through the Gradescope regrade tool and should only be used if you believe there was an error in the grading. Requests for clarification of the rubric or how it was applied should be made in person in office hours or by private post to the instructors using our Piazza site, with subject "HW Grade Inquiry".
• Regrades requests will be handled by the instructors. To avoid overwhelming volume of regrade requests, requests will be tagged as valid (if they truly stemmed from an error in grading) or invalid. Each student is limited to three invalid regrade requests each quarter. Regrade requests in excess of this budget will result in point deductions from the Class Participation and Preparation score.

Accommodations

The Office for Students with Disabilities (OSD), an Academic Affairs department, is responsible for the review of medical documentation and the determination of reasonable accommodations based on a disability. Authorization for Accommodation (AFA) letters are issued by the OSD and given to undergraduate, graduate, and Professional School students directly. If you have an AFA letter, meet with the CSE Student Affairs representative, and schedule an appointment with your instructor by Monday of Week 3 to ensure that reasonable accommodations can be arranged.

Academic Integrity

The guidelines for this class may be different from other courses and professors, and may prohibit things that you personally don't think of as "cheating." If you have any questions about what is acceptable or not under this class' guidelines, please ask before it is too late. UCSD's policy is that "I didn't know" is not an excuse.

• The only legitimate sources of help on submitted homework problems are:
  • Your designated homework partner or partners
  • the associated sections in the course textbook and/or provided course readings, and
  • class instructors, TAs, tutors and Piazza discussion.
• Other websites, materials from previous classes, or assistance from other individuals listed above are not to be used in any way, not even for consultation prior to writing up your solution.
• Do not share written solutions or partial solutions with others outside your group, or on the Internet.
• Do not attempt to falsify clicker or discussion participation. This is considered a violation of academic integrity.
• Haskell projects must be submitted individually. You may consult with others about the idea of the implementation, but you must code your solution yourself without having looked at or specifically discussed anyone else's solution code.

The Jacobs School of Engineering code of Academic Integrity, the UCSD Policy on Integrity of Scholarship and this syllabus list some of the standards by which you are expected to complete your academic work, but your good ethical judgment (or asking us for advice) is also expected as we cannot list every behavior that is unethical or not in the spirit of academic integrity. You should make yourself aware of what is and is not acceptable by reading these documents. Ignorance of the rules will not excuse you from any violations. If you have any doubt as to whether a conversation you wish to have with someone or other activity might cross the line, please stop and go to the discussion forum on Piazza, where we will be happy to help you, and where the integrity of the discussion can be monitored for everyone's protection.

Academic integrity violations will be taken seriously and reported immediately. If you are suspected of not following the guidelines, your case will be referred to the Dean of your college. Consequences may include an F in the course, no matter how small the affected assignment or exam question. Be aware that TritonLink will block you from dropping the course if your case is in process with the Dean, so you will not be able to avoid consequences by dropping.

Top