This is fairly simplistic and quite slow as is, but it does a very good job of matching inverted, flipped and rotated images; pretty good on resized images; and it seems fairly effective on similar images in different formats.
It's currently not good at cropped; negative or greyscaled images, though 24-bit <-> 8-bit colour transforms in either direction seem to matched quite well.
The performance can be improved markedly by using PDL or similar.
#! perl -slw
use strict;
use Data::Dumper;
use List::Util qw[ reduce sum max min ];
use GD;
sub check {
my $img = GD::Image->new( shift() );
my( $iMin, $iMax, %freq ) = ( 0, 0 );
my( $xMax, $yMax ) = $img->getBounds;
for my $y ( 0 .. $yMax - 1 ) {
for my $x ( 0 .. $xMax - 1 ) {
my $i = reduce{ ($a<<8) + $b;} $img->rgb( $img->getPixel(
+$x, $y ) );
$freq{ $i }++;
$iMin = $iMin < $i ? $iMin : $i;
$iMax = $iMax > $i ? $iMax : $i;
}
}
my $count = $xMax * $yMax;
my $ex = 16777216 / ( $iMax - $iMin );
my %norm;
while( my( $i, $f ) = each %freq ) {
$norm{ ( ( $i - $iMin ) * $ex ) / 16777216 } = $f / $count;
}
return 100 * sum map{ $_ * $norm{ $_ } } keys %norm;
}
my %sums = map{ check( $_ ), $_ } map glob, @ARGV;
printf "%32s : %7.5f\n", $sums{ $_ }, $_ for sort { $a <=> $b } keys %
+sums;
__END__
I'd be interested to see pairs of disparate images that produce very close checksums--assuming you are comfortable sharing them:)
This isn't based upon any other algorithms that I am aware of--just made up as I went along--but if anyone see's a relationship between this and prior art I appreciate references.
Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algorithm, algorithm on the code side." - tachyon
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.