Ross Beveridge
Office: 348 CS Building
Office Hours: 10:00-11:00 Mon, 2:00-3:00 Wed
Lecture Time and Place:
9:00-10:15, Mon Wed, CSB Room 425

CS 612 covers new state-of-the-art topics in computer vision. The course is typically structured around a reading list and semester project. The goal is to involve students in Ph.D.-level research, and to train them to become independent researchers in this area. The project will invovle the creation of a system that can respond to visual input, typically an object recognition task of some kind. The ultimate measure of success is when a student publishes a paper based on work done for this class.


CS 612 presumes the completion of CS 510 or rough equivalent taken elsewhere. As a research seminar, to move us into modern research areas students need familiarity with computer vision. Not all topics covered will have been highlighted in prior computer vision courses, but there must be a large enough foundation in place to allow time to catch on those areas that fall outside what has come through prior course work.

Semester Reading

The assigned reading in this course consists of a series of typically recent publications. Much of the work of the course is reflected in reading, summarizing, presenting and discussing these works.

Semester Research Project

Research is about developing, framing and answering questions. Part of the role of a seminar such as this one is to help develop this skill. Therefore, every student taking the class for credit will do a semester project. In general projects will focus on this semesters theme, which is video understanding with an emphasis on finding, interpreting and recognizing people. However, alternative topics may be negotiated with the instructor.

A sequence of intermediate milestones will be set forth over the course of the semester to encourage timely progress and refinement of topics. However, the bulk of the worth of a project will be assessed at the end of the semester based upon the final written report and in class presentation. All students should strive for a publication quality report and must submit their final report in a conference ready format. Any student whose project is published will automatically get an A in this course. More generally, being judeged of publication quality be the instructor is the simplest definition of what represents A level work in this seminar.

Class Meetings & Workload

The class will meet twice a week for 75 minute sessions. It should be noted that this is NOT a lecture course. Students will be responsible for reading material prior to class. In most classes, a student will present a brief presentation (30-45 minutes) on a topic, and then lead a class discussion for the remainder of the session.

This is typically a small seminar and students should not be surprised to find they are frequently presenting papers. Students will be graded on the quality of their presentations. To make sure that students are reading the material, students will submit roughly two paragraph synopses of papers in advance of the class sessions where they are being discussed. A student presenting a paper need not also write a synopsis. Synopses will be shared between students and the instructor in a common Google Doc generated by the instructor 24 hours prior to the class meeting.


Here are the formally graded elements of the course and associated weighting:

Activity Weight
Semester Project 50 %
In class presentations 30 %
Paper Summaries 10 %
Organization 10 %

Semester grades are determined by the weighted sum of points earned in each of these areas. A subjective curve (set by the instructor) is used to map points onto grades. Typically, the curve is set such that the class mean gets an B, one standard deviation above the mean is an A, one deviation below is a C, and so forth. However, the instructor retains the right to move the curve either direction. If the entire class is strong, the mean might be better than a B. Conversely, if the class as a whole is weak, the mean might be below a B...

Projects will be done individually and grades assigned on an individual basis. Further, students not already familiar with the CSU Honor Pledge should review this clear and simple pledge and always adhere to it.

Late and Makeup Policy

There is a lot of flexibility in a 600 level seminar in some matters, but not in others. In particular, presentations obviously have to be made on the day agreed upon. Further, paper synopses must be done prior to the class meeting where they are discussed. Doing them after the discussion is of little value. The semester project must be completed and turned in the last Friday of classes presentations of this work made in the prior week as announced at the time.

Professional Conduct

All students are expected to conduct themselves professionally. I assume you are familiar with the policies in the student information sheet for the department. Additionally, you are computing professionals, albeit perhaps just starting. You should be familiar with the code of conduct for the primary professional society, ACM. You can read the ACM Code of Conduct HERE.

We work to maintain an environment supportive of learning in the classroom and laboratory. Towards that end, we require that you be courteous to and respectful of your fellow participants (i.e., classmates, instructors). In particular: