Free automated microscopes software for linux

Aargh is a code generator, written in C++ and licensed under the terms of the GNU General Public License (GPL). It generates C++ code to parse a command line, using the getopt() facility available in UNIX and UNIX-like environments.
Automated Argument Helper project supports command-line options with integer arguments, string arguments, and no arguments. The generated code is commented and carefully indented for readability.
Its nice to have lots of command line options, but its a real pain to code for them.
Not that its difficult. Its just tedious, time-consuming, error prone, and no fun. I used to wince at the thought of adding command line options.
Not any more. All I have to do is define the options I want in a small XML file, and run it through aargh. Instantly I have C++ source code that I can compile and link into my program.
If I need to add another option, or otherwise change the rules, I can edit the XML and regenerate the code. No muss, no fuss. Now I can spend more time on the interesting parts of the project.
To use aargh, write an XML file to describe the options you want. When aargh reads the file, it generates two C++ files.
One file is a header that declares a class to represent the options. By default this class is named "Opts," but you can specify a different name. The other file is the implementation of Opts, or whatever you decide to call it. The Opts class provides member functions to parse the command line and return the results.
In your own code, declare an instance of Opts and call Opts::get() to parse the command line, passing it the argc and argv arguments from main(). Opts::get() returns zero if the command line follows the rules that you have outlined in the XML file, or non-zero otherwise. If the parsing is successful, the Opts object stores the results and makes them available to your program by a series of accessor functions.
Main features:
- You can enforce upper and/or lower limits on the number of non-option arguments.
- You can distinguish between options that take arguments and those that dont.
- You can specify that an option is required.
- You can require that the argument to an option be a non-negative integer.
- For an integer argument you can enforce upper and/or lower limits.
- For a string argument you can enforce upper and/or lower limits on the string length.
- For a string argument you can call a function of your own to validate the argument.
- You can allow multiple occurrences of the same option. In that case the generated code builds an STL vector to hold the arguments. By default the generated software allows only one occurrence of any given option.
Enhancements:
- You can now specify the location of the generated header file independently of its name.
- This feature may make it easier to incorporate aargh into complex build environments.

Automated support for compound RPC calls is a project which augments RPCGEN to support NFSv4-style compound procedures.

NFSv4 specifies that the RPC calls be batched into a "compound" call. There is no support for this in RPCGEN.

By rearranging the ONC IDL for NFSv4 into AutoGen definitions, these templates will emit the original IDL *plus* all the code to package, send, distribute, collect, return, and dispatch the results.

The distributed program author merely needs to call and supply server procedures for the routines specified in the IDL.

Templates for these calls and service routines is provided, too. The NFSv4 definitions are included.

Njudge is an automated judge for Diplomacy games, based on Ken Lowe software.
Installation:
1. Create a system user account (i.e. judge) and its home directory
(i.e. /home/judge) It is recommended to lock the password for this
account as you should never need to login as this user.
2. `cd to the directory containing the packages source code and type
`./configure to configure the package for your system. If youre
using `csh on an old version of System V, you might need to type
`sh ./configure instead to prevent `csh from trying to execute
`configure itself.
By default it will set up the judge in /home/judge as user judge with
an email address of judge@localhost and sendmail in /usr/sbin.
If you chose a different user and directory in step 1, or if judge
email should come from a different domain, you can give the configure
script flags to override the defaults. The flags are:
--with-dir=DIR
--with-user=NAME
--with-domain=DOMAIN
--with-sendmail=SENDMAIL
for example to set up the judge in /home/jaldhar/dip as user
jaldhar and email judge@braincells.com and sendmail in /usr/ucb, you
would do:
./configure --with-dir=/home/jaldhar/dip --with-user=jaldhar --with-domain=braincells.com --with-sendmail=/usr/ucb
There are many other flags you can give (type ./configure --help
for a full list) but these are the main ones youre likely to use.
Running `configure takes awhile. While running, it prints some
messages telling which features it is checking for.
3. Type `make to compile the package.
4. If this is a new install:
Type `make install to install the programs, any data files and
documentation. You will have to edit a few configuration files
before the judge will become operation.
If this is an upgrade from an older version;
Type make upgrade to install the new programs only.
*Note* compiled programs will not be stripped of debug and other extra
information. If you want to make compiled programs a little smaller,
you can type make install-strip or make upgrade-strip instead. This
may give a few harmless errors (when it tries to strip scripts) but you
can ignore them.
If you just want to rebuild the map files (because e.g. you added a new
variant,) type make remap.
5. You can remove the program binaries and object files from the
source code directory by typing `make clean. To also remove the
files that `configure created (so you can compile the package for
a different kind of computer), type `make distclean.
Enhancements:
- Major bugfixes

lamefwd provides an easy-to-use single process port forwarder.
lamefwd is an easy-to-use single process port forwarder, handling both TCP and UDP protocols. It is intended to be a fast and lightweight alternative to portfwd.
Usage
On BSD and Linux use "./configure ; make", on Windows run the installer. Then just edit lamefwd.cfg before starting the program:
#
# example config file for lamefwd
#
# localport remotehost remoteport protocol
#
5000 test.host.se 50 tcp
5005 test.host.se 55 udp
Enhancements:
- This release adds support for automated building using "./configure ; make" on *BSD, Linux, and Cygwin systems.

mangleme provides an automated broken HTML generator and browser tester.

mangleme is an automated broken HTML generator and browser tester, originally used to find dozens of security and reliability problems in all major Web browsers (Mozilla / Firefox / Netscape, Konqueror / Safari, MSIE, lynx, [e]links, w3m, elvis, etc), as reported on BUGTRAQ.

A trivial utility to automatically check for HTML parsing flaws. Generates
a basic set of badly mangled tags on request, with auto-refresh back to the
script, so that you can point a browser to it once, and let it run until
it crashes.

Put it in your cgi-bin directory or any other Apache folder with ExecCGI option enabled, then visit the URL http:// / /mangleme.cgi.

When the browser crashes, error-log should be examined for the last matching entry generated by mangle.cgi; extract the hexadecimal value, then invoke remangle.cgi?hex_value from the browser again. If it crashes, youve reproduced the problem, and can save the remangle.cgi page using wget or such.

Test-AutoBuild is a framework for performing continuous, unattended, automated software builds.
Test-AutoBuild pulls code from source control repositories (CVS, Perforce, and GNU Arch are currently supported), calculates inter-module dependencies, builds each module, and then generates HTML status pages, copies binary packages to Web/FTP server roots, and sends email status alerts. It is written with flexibility and extensibility in mind to make it easy to integrate with a wide range of development tools and languages.
Enhancements:
- The backend build engine has been refactored into a modular workflow engine.
- Support for Mercurial SCM repos has been added, and existing SCM implementations extended to allow extraction of changelogs.
- Performance and scalability are improved by hard linking files instead of copying.
- Error reporting and logging has been enhanced to make debugging of crashes/problems simpler.
- Major work has been done on documentating the tools, configuration file format, and developer APIs.
- The coverage of the test suite has been increased to cover a large portion of the critical code sub-systems.