CSC 400: Problem Seminar (Fall 2000)

Basic Info

• Catalogue description
• Prof.: Jason Eisner - jason@cs.rochester.edu - CSB 730 - x57230
• Class members: Matt Boutell, Samuel (Xiangchuan) Chen, Andy Learn, Tao Li, Stephen (Qi) Li, Scott Ligon, Proshanto Mukherji, Bill Scherer, Julie (Yutao) Zhong
• Class meetings: WF 11-12:15 in CSB 632, and M 11-12 in CSB 209.
• Office hours: W 2-3, or by appointment.
• Web page: http://www.cs.rochester.edu/u/jason/400
• Class mailing list: cs400@cs.rochester.edu
• Mailing list archive: cs.cs400 (newsgroup)

Policies

• Keeping Up
  • No lates: Assignments must be handed in on time. No "lates" or "incompletes." So start the writeup early even if you haven't finished the work yet. If you don't have time management skills, get some here and use this course to practice them.

  • Mailing list: You must read the class mailing list (or its archives on the newsgroup).

  • Other info: New resources and instructions will usually be linked from the syllabus or the assignments. I'll try to announce such additions at the top of this page.

• Collaboration and Plagiarism
  • Asking others for information: Encouraged.

  • Working together: Fine to work together (e.g., share the programming), but then you should do a correspondingly bigger project, and your report should indicate who you worked with.

  • Independent reports: Even if you worked with others, you must each write up your work independently.

  • No plagiarism: If you use anyone else's ideas, you must cite the source. If you use anyone else's words, you must indicate that you are quoting and give the source of the quote. Don't do this unless the wording of the quote is as significant as its content. (E.g., the quote is particularly funny or memorable, or you are going to attack it as unclear.)

• Grading
  • May vary: Since some of the assignments are written by other faculty (and you may choose to do a term project with any faculty member), there are no consistent grading policies. Do your best work and don't worry about it, but pay attention to all the feedback you get, including grades, comments, and advice.

  • How grades etc. are used:Your performance will be discussed at a full-faculty meeting in January. All the faculty are on the lookout for smart and hard-working advisees, and they use these discussions to make decisions.

  • What really matters: Your GPA will not ultimately be the measure of your success in grad school. What matters most is that you acquire real skills, publish influential papers, write a thesis, and get a job. This course is meant to speed you on your way. Good grades are the first signal to you and the faculty that you're on the right track.

• Evaluating Yourself: A Checklist
  • Can I communicate technical ideas clearly in writing?
  • Am I comfortable and effective at giving a technical talk?
  • Can I read academic papers and understand both the high-level idea and the details?
  • Can I use the local software tools fluently?
  • Do I understand the research, administrative and social structure of the department?
  • Do I know who to ask for career advice and technical advice?
  • Do I feel ready to start taking charge of my own career?

Syllabus