|
1
|
- more panorama slots available now
- you can sign up for a 2nd time if you’d like
|
|
2
|
- Today’s Readings
- Szeliski Chapters 7.1, 7.2, 7.4
|
|
3
|
- Lots of uses
- Track object behavior
- Correct for camera jitter (stabilization)
- Align images (mosaics)
- 3D shape reconstruction
- Special effects
|
|
4
|
- Input: sequence of images
- Output: point correspondence
- Feature correspondence: “Feature
Tracking”
- we’ve seen this already (e.g., SIFT)
- can modify this to be more accurate/efficient if the images are in
sequence (e.g., video)
- Pixel (dense) correspondence:
“Optical Flow”
|
|
5
|
|
|
6
|
- How to estimate pixel motion from image H to image I?
|
|
7
|
- Let’s look at these constraints more closely
|
|
8
|
- Combining these two equations
|
|
9
|
- Combining these two equations
|
|
10
|
- Q: how many unknowns and
equations per pixel?
|
|
11
|
|
|
12
|
|
|
13
|
- Basic idea: assume motion field
is smooth
- Horn & Schunk: add smoothness
term
- Lucas & Kanade: assume
locally constant motion
- pretend the pixel’s neighbors have the same (u,v)
- Many other methods exist. Here’s
an overview:
- S. Baker, M. Black, J. P. Lewis, S. Roth, D. Scharstein, and R.
Szeliski. A database and evaluation methodology for optical flow. In
Proc. ICCV, 2007
- http://vision.middlebury.edu/flow/
|
|
14
|
- How to get more equations for a pixel?
- Basic idea: impose additional
constraints
- most common is to assume that the flow field is smooth locally
- one method: pretend the pixel’s
neighbors have the same (u,v)
- If we use a 5x5 window, that gives us 25 equations per pixel!
|
|
15
|
- How to get more equations for a pixel?
- Basic idea: impose additional
constraints
- most common is to assume that the flow field is smooth locally
- one method: pretend the pixel’s
neighbors have the same (u,v)
- If we use a 5x5 window, that gives us 25*3 equations per pixel!
|
|
16
|
- Prob: we have more equations than
unknowns
|
|
17
|
- Optimal (u, v) satisfies Lucas-Kanade equation
|
|
18
|
- This is a two image problem BUT
- Can measure sensitivity by just looking at one of the images!
- This tells us which pixels are easy to track, which are hard
- very useful for feature tracking...
|
|
19
|
- What are the potential causes of errors in this procedure?
- Suppose ATA is easily invertible
- Suppose there is not much noise in the image
|
|
20
|
- Recall our small motion assumption
|
|
21
|
|
|
22
|
- Is this motion small enough?
- Probably not—it’s much larger than one pixel (2nd order
terms dominate)
- How might we solve this problem?
|
|
23
|
|
|
24
|
|
|
25
|
|
|
26
|
|
|
27
|
- L-K minimizes a sum-of-squares error metric
- least squares techniques overly sensitive to outliers
|
|
28
|
- Robust Horn & Schunk
- Robust Lucas-Kanade
|
|
29
|
- Middlebury flow page
- http://vision.middlebury.edu/flow/
|
|
30
|
- Features are better for:
- Flow is better for:
|
|
31
|
- Particles: combining features and
flow
- Peter Sand et al.
- http://rvsn.csail.mit.edu/pv/
- State-of-the-art feature tracking/SLAM
- Georg Klein et al.
- http://www.robots.ox.ac.uk/~gk/
|