CS777 Course News

News Pages: [ 1 | 2 ] next ->>

TextWeb

Are you looking for the Basic Course Information page?

Sun, 07 May 2006
More Details on P3...

Please make yourself a handin directory in ~cs777-1/public/P3-Handin.

I will put a signup sheet for final meeting times downstairs on the door to the graphics lab tomorrow (Monday) morning. There will be meeting times Thursday afternoon, Friday morning, and Friday afternoon.

Remember, everything must be handed in by 3:30pm on Wednesday. (It was supposed to be 3:30pm on Tuesday, but since I made a typo in the original announcement, you can have the extra time).

Fri, 05 May 2006
Self-Evals

Information on doing the self-eval is /Assignments/self-eval.txt

Please answer the 7 questions.

Fri, 28 Apr 2006
The P3 Requirements

First, the presentations:
You are expected to give a "formal" presentation (complete with slides). Please turn in your slides (powerpoint or whatever) with the rest of your handin materials (see below).

Timing:

  • For the P2 discussions, please keep things under 10 minutes.
  • Everyone else should shoot for 15 minues, except for David and Feng who have a semester's worth of stuff to discuss, so they can grow to 20 minutes.

Handing stuff in:
University rules say that everything is supposed to be due before exam week, so that the official due date is Friday, May 5th, at 5pm. However, (unofficially) there is a grace period so that as long as you turn in everything by 3:30pm on Wednesday, May 10th, its OK. Note: this is a hard deadline.

Before May 10th, you must arrange a time to meet with me on either May 11th or May 12th, so we can discuss things.

What to turn in:

  • A web page describing your project. Be sure to explain what problem you were trying to solve, the methods you use to solve it, how successful you were, what you accomplished, what your results are, ... Include citations/references.

    You should include pictures, movies, ...

  • As a seperate text file, a self evaluation. Details to be given later. But I'd like your opinion on how you did both on this project, and on the previous aspects of the course.

  • Any presentation materials you used.

The documentation of your project (both the write-up and the presentation) ARE part of your grade for the project.

I would also like to ask that everyone write the peer mini-reviews like we did for the project 1 talks. I think that there was a lot of good, constructive feedback last time and would like to do it again.

Mon, 17 Apr 2006
Class moved to 3310CS

On Wednesday 4/19 and Monday 4/24 we'll have class in 3310CS rather than 4310CS.

Thu, 30 Mar 2006
Feedback on the "Lamp" Assignment

Wow! You all did a great job with the lamp assignment. It looks like people put a lot of thought and effort into it.

I hope this was an instructive excersize. It seems to have had its intended purpose of getting people to really seriously think about how film "works."

The amazing thing to me is how much thought went into this very short piece of film. Of course, one of the interesting things about commercials is that their budget per amount of time can be quite high.

Projectlet 2 and 3 Info

If you notice on the calendar, Projectlet 2 is "due" (whatever that means) next Friday, and projectlet 3 is right on its heels.

What needs to happen - I need to get an idea of what you've done for projectlet 2, how things went, ... - We need to decide what you'll do for projectlet 3

For some of you, I have a good idea of what's going on, either because I've been talking to you all along, or you have a "deadline" like a class lecture to give. For others I know less...

What I'd like you to do:

  • I would like everyone to send me an email with a rough idea of what you are going to propose to do for project 3 by Monday. This will prepare me for the next step.
  • I would like to meet with everyone (preferably during office hours) next week to discuss what you will do. To make more time to meet with people, I will cut class short on Wednesday.
  • For Friday's Projectlet 2 handin, I have made a subdirectory in the summaries directory. Please write a brief description of what you've done over the 4 week time period.
  • For Monday (April 10), I'd like everyone to write a "proposal" about what they intend to accomplish by the end of the semester. Again, I've made a folder in the Summaries directory for people to put things in.
Wed, 08 Mar 2006
Handin Directory for P1

A handin directory has been created at:

~cs777-1/public/P1-Handin

which is the same as:

/p/course/cs777-gleicher/public/P1-Handin

Please create a directory there for yourself and put all of the required stuff in.

Note: There is a different place to put the P2 proposals (those go in a subdirectory of the Summaries web)

Thu, 02 Mar 2006
Handin Instructions for P1 (and P2 Proposals)

Instructions for the P1 Demo session, handins, and the P2 Proposals are described at /Projects/P1-Demos.txt

Be aware that there are several "deliverables" described here:

  • you must give a presentation in class (3/8)
  • you must comment on everyone else's presentation (3/9)
  • you must hand in materials from your project (3/8)
  • you must do a proposal for project 2 (3/8, 3/10)
Fri, 17 Feb 2006
Animation Assignment Results

I never actually took the time to thank everyone for the animations. I appreciate how much effort went into them, and I really appreciate the creativity in trying to do something fun.

If you want to look at what everyone did, everything is in http://www.cs.wisc.edu/graphics/Courses/777-s2006/Movies/ (although I never made a web page for it)

Wed, 08 Feb 2006
New System for Summaries

As discussed in class, I would like you to write each of your summaries in a seperate text file and to place them all in a drop box such that my web scripts can show them.

The directories are of the form:

p:/course/cs777-gleicher/public/Summaries/Week02

(of course, replace 02 with an appropraite week).

Please name your files:

login-paperid.txt

Where login is your login, and paperid is a short string that I will give you for each paper. Yes, the filename does have to end in .txt, and things are case-sensitive (I'm not that great of a PERL hacker yet!).

For an idea of what this looks like, check out:
/Summaries/Week02

For week 4 (this week) look at:
/Summaries/Week04

Your files get run through a text processor called MarkDown http://daringfireball.net/projects/markdown/ - it should be the case that your place text documents just look OK, but if you want to spruce them up you can.

Format for P1 Proposals

Is desribed at /Projects/p1-form.txt

This is another experiment of using my spiffy new homemade web infrastructure.

Tue, 07 Feb 2006
Handins for Movies

A "drop box" for movies has been created at

/afs/cs.wisc.edu/p/course/cs777-gleicher/public/html/Movies

that everyone in class should be able to write to.

Please place your movie file (an avi, please use reasonable compression!) and a still image (approx 320x240) in this directory.

Wed, 01 Feb 2006
Ideas for Projects

Here are some thoughts for project 1 ideas. None are fully fleshed out. If there's something that interests you (wheter its on this list or not), we should talk about it first. Preferably before Wednesday when we have the class discussion on projects. http://www.cs.wisc.edu/~cs777-1/TextWeb/textweb.pl/Projects/p1-ideas.txt

BTW: I encourage you to work in pairs.

Wed, 25 Jan 2006
Multi-Perspective Backgrounds

The concept of having "multi-perspective" backgrounds so that moving the 2D animation camera leads to 3D movements is best described in a SIGGRAPH paper Multiperspective Panoramas for Cel Animation http://grail.cs.washington.edu/projects/multirama/

The idea of multi-perspective images appear periodically in graphics and vision. They offer a way to put lots of information into a single picture. It could be a potential source of project ideas.

Tue, 24 Jan 2006
Looking Ahead

I have filled in the calendar with the topics and major deadlines for the first part of class.

The calendar has links to the syllabus which lists readings and whatnot (click on the week to link to the syllabus). For anything beyond mid-February, its still blank, but I've at least planned out the next two weeks http://www.cs.wisc.edu/graphics/Courses/777-s2006/TextWeb/textweb.pl/Syllabus/week03-04.txt

Mon, 23 Jan 2006
How to do Reading Summaries

Each week, you are supposed to do summaries of the papers that you've read. Since these are due on Friday, they will not include the "after class" readings for Friday (put those on the following week).

Until I develop a better scheme, please email your summaries to yu-chi before class on Friday.

The suggestion for how to write summaries is listed under Jan 18th or is http://www.cs.wisc.edu/graphics/Courses/777-s2006/TextWeb/textweb.pl/Assignments/Reading-Summary-Fortmat.txt

To make this easier for you, I will try to keep a list of all the papers that you should have read. You should know these from the Syllabus, but in case you forgot. http://www.cs.wisc.edu/graphics/Courses/777-s2006/TextWeb/textweb.pl/Syllabus/readings.txt

Fri, 20 Jan 2006
Assignment 2 posted

I've posted the famous "art assignment" http://www.cs.wisc.edu/~cs777-1/TextWeb/textweb.pl/Assignments/Assignment02-Use-A-System.txt

This should be fun.

Note: you are strongly encouraged to work in pairs

Thu, 19 Jan 2006
Week 2 Syllabus

The syllabus for next week (including topics and readings) is available http://www.cs.wisc.edu/graphics/Courses/777-s2006/TextWeb/textweb.pl/Syllabus/week-01-02.txt

I am still experimenting with the easiest way to make these kinds of pages, so bear with me. Hopefully, this won't be too confusing.

Wed, 18 Jan 2006
Assignment 1

Since there's no web navigation yet (I've spent too much of my time playing with formatting), the only way to find Assignment 1 is to go to http://www.cs.wisc.edu/~cs777-1/TextWeb/Assignments/Assignment01-Topics.html

Format for weekly readings

Each week, I would like you to send me a summary of the papers that you have read for the class. This should include the required readings, as well as any of the recommended readings that you've done (and each week you must read at least 1 related paper beyond the minimum of what's required).

Mike Swift's page for 736 readings provides lots of good food for thought on how to do this. I highly recommend reading it: http://www.cs.wisc.edu/~cs736-1/reading.html

One other thing to think about as you read the paper (and this will often be the first question I will ask to open the discussion) is: Why did I ask you to read this paper?

As an initial guess on how to do summaries, I would like to suggest that you answer these questions (you should only need a sentence or two for each)

  1. A one or two sentence summary of the paper.
  2. A one or two sentence description of the problem the paper is trying to solve.
  3. A one of two sentence description of the method used to solve the problem.
  4. A list of short (approx one sentence) descriptions of the key ideas of the paper.
  5. A list of short (approx one sentence) descriptions of the contributions of the paper.
  6. Any questions that the paper raises for you. This might be some flaw that they do not address, something that is unclear, some piece of background knowledge that you don't have that would help you understand the paper, ...

I am fine with you preparing these summaries with a partner (you only need to send me one copy), as long as you really prepare them as a team effort and use this process as an opportunity to discuss the paper.