Free matches malone software for linux

SnapMatcher provides an application to identify near-identical or similar images in large collections.
SnapMatcher is an application intended for photographers, artists, or image packrats who have very large collections of digital images, some of which may be duplicates or near duplicates.
By identifying images across multiple formats with the ability to filter out minor edits such as changes to contrast, brightness, color balance, resizing, or even the addition of text or borders, SnapMatcher can be a valuable tool in organizing/culling unwieldy collections.
Main features:
- Ability to create multiple image databases for later queries
- Customizable matching threshold allowing results to be generated anywhere from near exact matches only to identification of distinct images with very similar appearances
- Support of most standard image formats (JPEG, GIF, TIFF, PNG, and BMP by default, other formats possible using command line arguments)
- Ability to specify image types by extension in image DB creation process
- Output of match results into a simple text file
Install
Simply unzip SnapMatcher-src-0.1.tar.gz in an appropriate location. A directory
"snapmatcher" will be created containing the Python sources need to run the
application. Then run the application by executing:
# python SnapMatcher.py
inside the directory from your systems command line.vv
Enhancements:
- This release adds the ability to quickly match a small set of images against any image database.
- It re-fixes the bug preventing the directory scan process in database creation from working on Windows (the fix in version 0.3 was flawed).
- It adds PCX, PPM, XPM, and XBM to the previous default image extensions (JPG, JPEG, JPE, PNG, GIF, TIF, TIFF, and BMP) used when creating an image database.
- It improves reliability for the database and matches file updates by first writing updates to a temp file, so the original files are unmodified in the case of program interruption.
- It improves the efficiency of database updates.

Regexp::MatchContext is Perl module to replace (and improve) $MATCH, $PREMATCH, and $POSTMATCH

SYNOPSIS

use Regexp::MatchContext -vars;

$str = m/(?p) d+ /;

print "Before: $PREMATCHn";
print "Matched: $MATCHn";
print "After: $POSTMATCHn";

$MATCH = 2 * $MATCH; # substitute into original $str

The English.pm module provides named aliases for Perls built-in $`, $& and $ variables: $PREMATCH, $MATCH, and $POSTMATCH. Unfortunately, those aliases suffer the same problems as their originals: they degrade the performance of every single regex in your program, even if youre only using them to get information about a single match.

This module also provides $PREMATCH, $MATCH, and $POSTMATCH, but in a way that only impacts the performance of matches that you specify. That is, these three variables are only set if the most recently matched regex contained the special (non-standard) meta- flag: (?p).

That is:

use Regexp::MatchContext -vars;

$str = foobarbaz;

$str =~ /(?p) foo /x;

# $PREMATCH contains foo
# $MATCH contains bar
# $POSTMATCH contains baz

$str =~ / foo /x;

# $PREMATCH, $MATCH, and $POSTMATCH all undef

The (?p) marker can be placed anywhere within the regex and, except for setting the three context variables on a successful match, is otherwise totally ignored.

XSearch project bridges the gap between Beagle (simple interface, large search net) and find/grep (powerful searching, small search net).

What is XSearch?

A fast real-time search engine for displaying all regular expression matches within a file, across multiple directories.

Why XSearch?

Linux currently has two leading search methods:

1.Beagle – simple to use, but shows too many matches.
2.Find/Grep – hard to use, but provides exact matching.

XSearch tales the best features from both.

It provides a simple to use interface, but has the power of find and grep combined. In addition, the end search result is an easy to browse list of matching files, and matching lines.

Who would benefit from XSearch?

Software engineers mainly, but anyone who has a large number of pure text files will benefit.

Searching a large amount of source code, across many directories, is both tedious, and time consuming. Think of this tool as a helper to finding that needle in a haystack!
How many times as a software engineer do you find it essential to search code looking for specific functions, or declarations within the source code? Now with XSearch, you can quickly look-up the code locations, and often get the info without having to open the file in your editor.

Net::ACL::Match::IP is a class matching IP addresses against an IP or network.

SYNOPSIS

use Net::ACL::Match::IP;
# Constructor
$match = new Net::ACL::Match::IP(1,10.0.0.0/8);
# Accessor Methods
$netmaskobj = $match->net($netmaskobj);
$netmaskobj = $match->net($net);
$index = $match->index($index);
$rc = $match->match($ip);
__top

This module is just a wrapper of the Net::Netmask module to allow it to operate automatically with Net::ACL::Rule.

TDFinder is a widget to support preparing Go tournament registration.

SYNOPSIS

use Games::Go::TDFinder;
$tdFinder = $parent->Games::Go::TDFinder ( ? options ? );

TDFinder is a widget to assist in preparing a Go Tournament register.tde file in AGA (American Go Association) format. It consists of three main parts: a TDEntry widget at the bottom, a match list in the middle (which is an ROText widget), and the tde information at the top (A TextUndo widget).

The widget opens the TDLIST file for searching. Tournemant directors should download the most recent TDLIST from the AGA shortly before the tournament. The most recent TDLIST is available from the AGA at: http:www.usgo.org
Typing search keys into the TDEntry field causes the TDFinder to search through the TDLIST looking for matches.

When the number of matches is small enough to fit into the match list ROText widget, they are posted there. Individual TDLIST entries can be selected either by further refining the search keys, or by using the Up/Down arrow keys. Typing Enter, double clicking a match (BUGBUG: TBD), or dragging a match to the tde text widget (BUGBUG: TBD) transfers a match to the tde file.

The caller is responsible for make sure the final register.tde file corresponds to the information in the tde part of the TDFinder widget.

Championship Generator produces a list of all the meetings which must occur between the participants of a championship.

It can be used to produce the challenges between teams if competitions are not foreseen to directed elimination. Championship Generator project supports championships where it is necessary to consider the matches at home and away.

It can also try to avoid fights between the big teams in the first and last days. It also supports the case in which two teams have a mutual stadium, and therefore cannot simultaneously play at home or away.

Sanefile is a tool to easily and quickly clean and change a large number of filenames. The idea started when I started “ripping” my own CD’s and the filenames were all different and full of errors. When I started getting TV downloads from other sources, the issue became a problem.

I had to find an efficient way of changing a large number of filenames. Sanefile was the result. Simple, single-purpose and very efficient at it with total exploitation of Tcl’s rich Regular Expression capabilities.

What this tool is NOT: spy-ware, spam-ware, virus or any other crappy stuff.

With Sanefile, you can use the full power of regular expressions. For instance, imagine that you want to filter off all files starting with a A. To use the just A would remove from the list all the files with A in it. Not the solution. If you use ^A (Carat and A) it means that it has to match A only at the beginning of the text.

More examples:

^text matches "text" in the beginning of the name
text$ matches "text" in the END of the filename
. matches ANY character
[ ] range indicator as in:
[a-z] matches ONE letter "a" to "z"
[a-zA-Z] matches ONE letter "a" to "z" and "A" to "Z"
[0-9] matches ONE digit
[^range] (caret) matches if NOT in the range as in:
[^0-9] matches if it is NOT a digit
* operator for repetition
.* matches everything
[0-9]* multiple digits
[^a-zA-Z0-9]* a bunch of everything BUT a letter or digit
escape operator
t tab
( when you want to match (
. when you want to match .
when you want to match (RARELY DONE! Think why.)
() used to group expressions
ab* a followed with multiple bs
(ab)* multiple ab (different from above!)

^Doors.*([A-Z][0-9]*).*.mp3$ Matches all files starting with Doors, have somewhere in the middle a letter followed by digits and end in ".mp3"

Test::Cmd is a Perl module for portable testing of commands and scripts.

SYNOPSIS

use Test::Cmd;

$test = Test::Cmd->new(prog => program_or_script_to_test,
interpreter => script_interpreter,
string => identifier_string,
workdir => ,
subdir => dir,
match_sub => $code_ref,
verbose => 1);

$test->verbose(1);

$test->prog(program_or_script_to_test);

$test->basename(@suffixlist);

$test->interpreter(script_interpreter);

$test->string(identifier string);

$test->workdir(prefix);

$test->workpath(subdir, file);

$test->subdir(subdir, ...);
$test->subdir([sub, dir], ...);

$test->write(file, read($contents, [subdir, file]);
$test->read(@lines, [subdir, file]);

$test->writable(dir);
$test->writable(dir, $rwflag);
$test->writable(dir, $rwflag, %errors);

$test->preserve(condition, ...);

$test->cleanup(condition);

$test->run(prog => program_or_script_to_test,
interpreter => script_interpreter,
chdir => dir, args => arguments, stdin => pass(condition, &func);

$test->fail(condition);
$test->fail(condition, &func);
$test->fail(condition, &func, $caller);

$test->no_result(condition);
$test->no_result(condition, &func);
$test->no_result(condition, &func, $caller);

$test->stdout;
$test->stdout($run_number);

$test->stderr;
$test->stderr($run_number);

$test->match(@lines, @matches);
$test->match($lines, $matches);

$test->match_exact(@lines, @matches);
$test->match_exact($lines, $matches);

$test->match_regex(@lines, @regexes);
$test->match_regex($lines, $regexes);

$test->diff_exact(@lines, @matches, @output);
$test->diff_exact($lines, $matches, @output);

$test->diff_regex(@lines, @regexes, @output);
$test->diff_regex($lines, $regexes, @output);

sub func {
my ($self, $lines, $matches) = @_;
# code to match $lines and $matches
}
$test->match_sub(&func);
$test->match_sub(sub { code to match $_[1] and $_[2] });

$test->here;

The Test::Cmd module provides a low-level framework for portable automated testing of executable commands and scripts (in any language, not just Perl), especially commands and scripts that interact with the file system.

The Test::Cmd module makes no assumptions about what constitutes a successful or failed test. Attempting to read a file that doesnt exist, for example, may or may not be an error, depending on the software being tested.

Consequently, no Test::Cmd methods (including the new() method) exit, die or throw any other sorts of exceptions (but they all do return useful error indications). Exceptions or other error status should be handled by a higher layer: a subclass of Test::Cmd, or another testing framework such as the Test or Test::Simple Perl modules, or by the test itself.
(That said, see the Test::Cmd::Common module if you want a similar module that provides exception handling, either to use directly in your own tests, or as an example of how to use Test::Cmd.)

In addition to running tests and evaluating conditions, the Test::Cmd module manages and cleans up one or more temporary workspace directories, and provides methods for creating files and directories in those workspace directories from in-line data (that is, here-documents), allowing tests to be completely self-contained. When used in conjunction with another testing framework, the Test::Cmd module can function as a fixture (common startup code for multiple tests) for simple management of command execution and temporary workspaces.

The Test::Cmd module inherits File::Spec methods (file_name_is_absolute(), catfile(), etc.) to support writing tests portably across a variety of operating and file systems.

A Test::Cmd environment object is created via the usual invocation:

$test = Test::Cmd->new();

Arguments to the Test::Cmd::new method are keyword-value pairs that may be used to initialize the object, typically by invoking the same-named method as the keyword.