<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://www.communities.hp.com/online/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Security Printing and Imaging : authentication, imaging</title><link>http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/authentication/imaging/default.aspx</link><description>Tags: authentication, imaging</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP1 (Build: 31106.3070)</generator><item><title>Imaging Challenges, Part Deux</title><link>http://www.communities.hp.com/online/blogs/securityprinting/archive/2008/09/20/imaging-challenges-part-deux.aspx</link><pubDate>Sat, 20 Sep 2008 11:30:00 GMT</pubDate><guid isPermaLink="false">964d1d0f-bea0-4201-a2aa-8aa369a35a46:84840</guid><dc:creator>StevenSimske</dc:creator><slash:comments>0</slash:comments><comments>http://www.communities.hp.com/online/blogs/securityprinting/archive/2008/09/20/imaging-challenges-part-deux.aspx#comments</comments><description>&lt;p&gt;In a blog post earlier on this busy blogging week (hard to tell I&amp;#39;m spending a lot of time rotting in airports/hotels, no?), I introduced some of the difficulties in image clustering, or aggregation. This post introduces some of the broad approaches used to solve such imaging challenges.&lt;/p&gt;
&lt;p&gt;Broadly, there are at least three classes of image analysis technologies used to compare photos (more broadly termed &amp;quot;images&amp;quot; to include scanners, cameras, inspection systems, video, and all other forms of &amp;quot;image capture&amp;quot;):&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;1. Machine vision/pattern recognition&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;2. Segmentation-based approach&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;3. Image modeling&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;There is some overlap among these three approaches, but they are distinct enough to proceed.&lt;/p&gt;
&lt;p&gt;1. &lt;strong&gt;Machine vision/pattern recognition&lt;/strong&gt;: This approach typically uses correlation (a statistical measure of image similarity) to compare two images. Correlation can be used to compare texture, frequency, color, shape and/or other content in the two images compared. The use of frequency-based (looking for how an image varies spatially in one or more directions) comparisons allows images of different scale (size of features) to be readily compared by simply scaling the frequency outputs relative to one another. Best matches provide the scale differences and subsequent alignment of the relatively scaled images. Machine vision systems usually are initialized through &amp;quot;training&amp;quot; the system by capturing one or more images of a calibrating (or &amp;quot;ground truth&amp;quot;) feature to which the other image(s) is(are) compared. Clearly, such pattern recognition or &amp;quot;machine vision&amp;quot; based systems are especially amenable to inspection, wherein many images are to be compared to the calibration image. This type of comparison is especially effective for comparing Pictures #1 and #2 in the &amp;quot;Imaging Challenges&amp;quot; post of two days past.&lt;/p&gt;
&lt;p&gt;2. &lt;strong&gt;Segmentation-based approach&lt;/strong&gt;. Image &amp;quot;segmentation&amp;quot; is the process by which an image is divided into regions, called segments, which can&amp;nbsp;thereafter be used as individual images for comparison. Therefore, this approach is recursive inasmuch as it affords refined segmentation, or sub-segmentation, as further information needs to be extracted. Images which contain steganographic (hidden) information such as digital watermarks, fiducial marks, and the like, are effectively analyzed by these approaches. Note that this approach is also taken on the &amp;quot;storage&amp;quot; side for many compression approches, such as tiled JPEGs. This segmentation-based approach can be used to cluster Picture #3 in the &amp;quot;Imaging Challenges&amp;quot; post with Pictures #1 and #2.&lt;/p&gt;
&lt;p&gt;3. &lt;strong&gt;Image modeling&lt;/strong&gt;. An image model is a description of salient features for the image analysis algorithm&amp;nbsp;to find in the image. This may be conveyed through a template (description of layout), a feature set, or other means. An &amp;quot;image model&amp;quot; assumes that the image processing system is capable of &amp;quot;image understanding&amp;quot;, meaning it is capable of accurately deciding whether or not an image contains a match to the model defined. Such a system relies on powerful statistical classifiers to decide on a &amp;quot;yes&amp;quot; or &amp;quot;no&amp;quot; for the match. Clearly, the goal is to have 0% false positives (no regions identified as matching that actually are not matches) and 0% false negatives (no regions that actually are matches but are missed, or unidentified). In reality, though, the system is tuned to provide the best overall accuracy based on the task at hand. If the cost of a false positive is much higher than the cost of a false negative, then the system should be tuned to favor false negatives (miss some matches) but have very high confidence in the matches. This is usually the case for the reading of security-related information [in future blogs, I will discuss classification in greater detail]. Note that, if each GPS location has a &amp;quot;model&amp;quot; for the images that can be captured (such as a 3-D panoramic), there is the possibility that Picture #4 in the &amp;quot;Imaging Challenges&amp;quot; post could be aggregated with Pictures #1-#3 (even though the content in the Picture has no overlap with the other 3). Currently, however, except in expensive systems for high-security locations, these models do not yet exist. But, they will in the future (think about 3-D video games, for example, in which a 3-D panoramic model is created for various &amp;quot;rooms&amp;quot; in the game).&lt;/p&gt;
&lt;p&gt;-Steve&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://www.communities.hp.com/online/aggbug.aspx?PostID=84840" width="1" height="1"&gt;</description><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/security/default.aspx">security</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/authentication/default.aspx">authentication</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/forensics/default.aspx">forensics</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/inspection/default.aspx">inspection</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/imaging/default.aspx">imaging</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/image+transformation/default.aspx">image transformation</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/exposure/default.aspx">exposure</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/contrast/default.aspx">contrast</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/machine+vision/default.aspx">machine vision</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/pattern+matching/default.aspx">pattern matching</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/image+modeling/default.aspx">image modeling</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/segmentation/default.aspx">segmentation</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/image+processing/default.aspx">image processing</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/templates/default.aspx">templates</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/steganography/default.aspx">steganography</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/image+understanding/default.aspx">image understanding</category></item><item><title>Imaging Challenges</title><link>http://www.communities.hp.com/online/blogs/securityprinting/archive/2008/09/18/imaging-challenges.aspx</link><pubDate>Thu, 18 Sep 2008 11:57:00 GMT</pubDate><guid isPermaLink="false">964d1d0f-bea0-4201-a2aa-8aa369a35a46:84794</guid><dc:creator>StevenSimske</dc:creator><slash:comments>0</slash:comments><comments>http://www.communities.hp.com/online/blogs/securityprinting/archive/2008/09/18/imaging-challenges.aspx#comments</comments><description>&lt;p&gt;&amp;quot;Imaging&amp;quot; is a broad term meaning the ability to transform, interpret and/or associate an image. Sounds pretty easy, right? But when you consider what is actually involved, it&amp;#39;s&amp;nbsp;pretty hard. Most modern digital cameras (and other photo-capture devices) are packed with a host of &amp;quot;automatic&amp;quot; imaging, such as noise removal, contrast/exposure enhancement, etc., up to red-eye removal and photo album aggregation. All of which implies there are (hopefully reliable!) algorithms available to improve the quality of an image (and thus improve its value).&lt;/p&gt;
&lt;p&gt;However, the&amp;nbsp;way you will use an image (called its &amp;quot;workflow&amp;quot;)&amp;nbsp;impacts what algorithms you will use to clean it up, improve its quality, and otherwise transform it. Normal metrics for &amp;quot;image quality&amp;quot;, for example, are not as important in security printing and imaging as are the more arcane concepts of inspectability, authenticability and forensics-capability. Consider, as an exemplar, if I have added information--such as a 2D bar code or a digital watermark [hidden, or &amp;quot;steganographic&amp;quot; information]--to an image, then whatever I do with my imaging should be focused on helping me reliably extract that information rather than improving the aesthetics of the image.&lt;/p&gt;
&lt;p&gt;How hard can that be, you ask? Let&amp;#39;s look at four photos that each contain one set of identical information; namely, the GPS location that the image was taken from.&lt;/p&gt;
&lt;p&gt;Picture 1 is the new Sao Paulo bridge by day, from the 31st floor:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;img height="144" alt="" src="http://images2.snapfish.com/232323232%7Ffp533%3B2%3Evq%3D3365%3E48%3B%3E837%3EWSNRCG%3D3238%3C3%3C%3B%3C895%3Bvq0mrj" width="192" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;Picture 2 is the same bridge, from the same floor, with a different aspect ratio:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;img height="192" alt="" src="http://images2b.snapfish.com/232323232%7Ffp53459%3Evq%3D3365%3E48%3B%3E837%3EWSNRCG%3D3238%3C3%3C%3B%3C895%3Avq0mrj" width="144" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;The third is taken from the same GPS location, 30 floors lower, and at dark:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;img height="144" alt="" src="http://images2.snapfish.com/232323232%7Ffp533%3A%3B%3Evq%3D3365%3E48%3B%3E837%3EWSNRCG%3D3238%3C3%3C%3B%3C8%3C24vq0mrj" width="192" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;And the last image is taken from the same GPS location, 6 stories up, in the opposite direction:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;img height="192" alt="" src="http://images2.snapfish.com/232323232%7Ffp533%3B4%3Evq%3D3365%3E48%3B%3E837%3EWSNRCG%3D3238%3C3%3C%3B%3C8%3C25vq0mrj" width="144" border="0" /&gt;&lt;/p&gt;
&lt;p&gt;What information do these pictures have in common aside from the GPS location? Picture 1 and 2 are pretty similar to the human viewer, but to the imaging algorithm have a number of distinctions. Perspective, aspect ratio, contrast and exposure all differ considerably. Most image-clustering technologies, however, can aggregate (find similar) these two. But if the bridge were watermarked, would the photos equally represent those watermarks? Would the same bridge in Picture 3 also aggregate with Pictures 1 and 2?&amp;nbsp; Humans would say yes, but machine algorithms are not so sure. Picture 4, not a chance for the machine (or for any human who did not have the memory of both images), without the GPS information.&lt;/p&gt;
&lt;p&gt;This represents (somewhat figuratively)&amp;nbsp;some of the challenge involved in security imaging. In practice, we are not usually required to associate Picture #4 with Pictures 1-3 except through metadata (image header) search. In future blogs, I will discuss how the imaging is actually able to work (and work well!) on Pictures 1-3.&lt;/p&gt;
&lt;p&gt;-Steve&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://www.communities.hp.com/online/aggbug.aspx?PostID=84794" width="1" height="1"&gt;</description><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/security/default.aspx">security</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/authentication/default.aspx">authentication</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/forensics/default.aspx">forensics</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/inspection/default.aspx">inspection</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/imaging/default.aspx">imaging</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/Sao+Paulo/default.aspx">Sao Paulo</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/Morumbi+bridge/default.aspx">Morumbi bridge</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/GPS/default.aspx">GPS</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/image+transformation/default.aspx">image transformation</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/exposure/default.aspx">exposure</category><category domain="http://www.communities.hp.com/online/blogs/securityprinting/archive/tags/contrast/default.aspx">contrast</category></item></channel></rss>