<?xml version="1.0" encoding="utf-8" standalone="no"?>
<!DOCTYPE document PUBLIC "-//CNX//DTD CNXML 0.5 plus MathML//EN" "http://cnx.rice.edu/technology/cnxml/schema/dtd/0.5/cnxml_mathml.dtd">
<document xmlns="http://cnx.rice.edu/cnxml" xmlns:md="http://cnx.rice.edu/mdml/0.4" xmlns:bib="http://bibtexml.sf.net/" xmlns:m="http://www.w3.org/1998/Math/MathML" id="new">
  <name>Image Registration using Projective Flow</name>
  <metadata>
  <md:version>1.2</md:version>
  <md:created>2006/12/20 12:54:16 US/Central</md:created>
  <md:revised>2006/12/21 22:45:23.531 US/Central</md:revised>
  <md:authorlist>
      <md:author id="jryans">
      <md:firstname>J.</md:firstname>
      <md:othername>Ryan</md:othername>
      <md:surname>Stinnett</md:surname>
      <md:email>jryans@rice.edu</md:email>
    </md:author>
      <md:author id="jgillenw">
      <md:firstname>Jennifer</md:firstname>
      <md:othername>Ann</md:othername>
      <md:surname>Gillenwater</md:surname>
      <md:email>jgillenw@rice.edu</md:email>
    </md:author>
      <md:author id="elicas">
      <md:firstname>Elica</md:firstname>
      
      <md:surname>Skorcheva</md:surname>
      <md:email>elicas@rice.edu</md:email>
    </md:author>
  </md:authorlist>

  <md:maintainerlist>
    <md:maintainer id="jryans">
      <md:firstname>J.</md:firstname>
      <md:othername>Ryan</md:othername>
      <md:surname>Stinnett</md:surname>
      <md:email>jryans@rice.edu</md:email>
    </md:maintainer>
    <md:maintainer id="jgillenw">
      <md:firstname>Jennifer</md:firstname>
      <md:othername>Ann</md:othername>
      <md:surname>Gillenwater</md:surname>
      <md:email>jgillenw@rice.edu</md:email>
    </md:maintainer>
    <md:maintainer id="elicas">
      <md:firstname>Elica</md:firstname>
      
      <md:surname>Skorcheva</md:surname>
      <md:email>elicas@rice.edu</md:email>
    </md:maintainer>
    <md:maintainer id="richb">
      <md:firstname>Richard</md:firstname>
      <md:othername>G.</md:othername>
      <md:surname>Baraniuk</md:surname>
      <md:email>richb@rice.edu</md:email>
    </md:maintainer>
    <md:maintainer id="Markpanzee">
      <md:firstname>Mark</md:firstname>
      <md:othername>A.</md:othername>
      <md:surname>Davenport</md:surname>
      <md:email>md@rice.edu</md:email>
    </md:maintainer>
  </md:maintainerlist>
  
  <md:keywordlist>
    <md:keyword>flow</md:keyword>
    <md:keyword>image</md:keyword>
    <md:keyword>projective</md:keyword>
    <md:keyword>registration</md:keyword>
  </md:keywordlist>

  <md:abstract>Gives the highlights of the projective flow algorithm we used for image registration.</md:abstract>
</metadata>
  <content>
<section id="ov">
<name>Overview</name>
    <para id="element-76">Superresolution is based on the idea that images with slight shifts can be aligned and combined into a single, higher resolution image.  While aligning images with respect to one another may not seem too complex at first, there are a number of technical details that muddy the waters.  Additionally, superresolution requires registration results that are accurate to the subpixel level.  While an error of one or two pixels sounds just fine, it would lead to a poor quality image after combination.</para> 
</section>
<section id="mot">
<name>Motivation</name>
<para id="element-412">Let's first look at the impact of registration before delving into the details of the algorithm we chose.  Consider the following two test images:</para><figure id="element-437"><name>Registration Test Images</name>
<subfigure id="test1">
<media type="image/png" src="testa.png"/>
</subfigure>
<subfigure id="test2">
<media type="image/png" src="testb.png"/>
</subfigure>
<caption>Two slightly shifted images (Source: http://lcavwww.epfl.ch/software/superresolution/superresolution_dataset1.tar.gz)</caption></figure><para id="element-240">While these two images may appear to be the same, they are actually just slightly different from each other.  While we could try to combine the images as they are now, we need to register them first to achieve a better result.  Below two difference graphs illustrate the impact of registration, the first showing the difference before registration, and the other after.</para><figure id="element-836"><name>Difference Graphs</name>
<subfigure id="diff1">
<media type="image/png" src="prereg.png"/>
<caption>Before registration</caption>
</subfigure>
<subfigure id="diff2">
<media type="image/png" src="postreg.png"/>
<caption>After registration</caption>
</subfigure></figure><para id="element-103">Even though it is hard to see a visible difference when viewing the two images separately, the difference graphs above show how registration can still detect difference and account for them.</para></section>
<section id="algo">
<name>Algorithm</name>
<para id="element-273">While there are a number of different techniques that can be used to register images, many of them are <emphasis>feature-based</emphasis>.  They attempt to track the same set of points as they move from image to image.  This can work well, but only if the points are detect accurately each time.  Instead, we chose to use a <emphasis>featureless</emphasis> algorithm, which avoids feature points by using the flow of all pixels in the image.  It improves upon the optical flow concept discussed in a previous module by allowing for changes in translation, rotation, scale, pan, and tilt between each image.  The algorithm is detailed below.</para><list id="element-349" type="enumerated"><item>Calculate the vertical, horizontal, and time derivatives between the two images.  This is same process mentioned in <cnxn document="m14208">Optical Flow</cnxn>.</item>
<item>From these spatiotemporal derivatives, estimate an approximate model (q) of the projective parameters.  There are several models that can be used, such as bilinear and pseudo-projective.  The system used to estimate the bilinear model is shown below.
<figure id="bimod"><name>Bilinear Approximation Model</name>
<media type="image/png" src="bimodel.png"/>
<caption>System of equations that relates derivative to the bilinear approximation model (Source: 1)</caption></figure>
</item>
<item>Using the four corners of the image, calculate their new coordinates from the approximate model.  In the formulas for the bilinear model below, <m:math>
   <m:msub>
    <m:mi>u</m:mi>
    <m:mi>m</m:mi>
   </m:msub>
   <m:mo>+</m:mo><m:mi>x</m:mi>
</m:math>
and <m:math>
   <m:msub>
    <m:mi>v</m:mi>
    <m:mi>m</m:mi>
   </m:msub>
   <m:mo>+</m:mo><m:mi>y</m:mi>
</m:math> denote the new x and y coordinates respectively.
<figure id="coord"><name>Bilinear Coordinate Formulas</name>
<media type="image/png" src="newcoords.png"/>
<caption>Relates old and new coordinate via approximate (q) parameters (Source: 1)</caption></figure>
</item>
<item>These old and new coordinates now completely determine the projective parameters in the exact model (p).</item>
<item>Apply these new parameters (p) to one of the images and iterate until the difference is negligible.</item></list>
</section>
<section id="acc">
<name>Improving Accuracy</name>
<para id="element-858">To get better results, we can create a multi-resolution pyramid for each image first.  This means that we generate several levels of increasingly blurry images.  Starting at the blurriest level, we apply several iterations of the algorithm as described above.  Then, we move up to a less blurry level and repeat, but we carry over the result from the previous level and use that as our starting point.</para></section>
  </content>
  
</document>
