Free programmable software for linux

Streamline is a high-speed networking subsystem for commodity operating systems. It increases performance by moving processing tasks to the fastest location. Streamline supports in-kernel execution, but also dedicated hardware (NICs) and even remote machines. An implementation of Streamline for Linux 2.6.13 and higher is made publicly available.
The goal of Streamline is to make fast network processing viable for common tasks. Many advanced processing schemes so far fail to make it into OSes, because they are difficult to combine with the socket(..) API or only applicable in a few situations. Our goal is to integrate known as well as develop new methods that replace sockets(..). without burdening application developers and end-users. Streamline achieves this by constructing a tailored dataplane for each application at runtime from an extensible set of functions.
Applications request information streams by specifying a series of abstract functions that need to be performed on incoming data (e.g., select tcp packets for port 80, reassemble into a stream, filter out known attacks). At runtime, streamline searches for implementations of these functions. These can be found in the kernel, in the application library, or in dedicated hardware such as programmable network cards or asymmetric multicores. When all functions are found, interconnecting datapaths are setup. Paths may need to cross the PCI bus, userspace/kernelspace barrier or even LANs. Optimisation of these paths is one of the factors that contributes to Streamlines performance.
The base system comes bundled with functions for pattern matching (Aho Corasick, RegEx), accounting, filtering (among others BPF), stream reassembly, rewriting, inspection, and more. Obvious uses are intrusion detection, network address translation, media streaming and realtime (pre)processing of scientific data.
Enhancements:
- This is mostly a stabilization release, which adds support for Linux kernels up to 2.6.22 and Fedora Core installations.
- The only truly new feature is a virtual filesystem interface (like sysfs) to streamline.
- With this "netmonfs" you can inspect live datastreams as if youre reading local files.
- Setting up streams and filters is easily accomplished through mkdir, open, and other well-known tools.
- Note that netmonfs is still beta quality software.

PSIworld stands for Programmable Scalable Interactive World. This framework provides a set of libraries, utilities and applications in order to ease the implementation of dynamic Artificial Intelligence environments. Specifically, the development of Multi-Agent applications is targeted.

This project is designed in a generic manner, so that various kinds of applications can use and take advantage of the services provided by ProjectPSI. Primarily developed under GNU/Linux using various OpenSource tools, ProjectPSI modules are released under GNU GPL and LGPL licenses. This framework does not only include pure algorithm libraries for AI computation tasks, but also a C/C++ library for distributed computation. A server-client model also involves various, concurrent visualization methods of distinct Agents or Societies.

PAPI aims to provide the tool designer and application engineer with a consistent interface and methodology for use of the performance counter hardware found in most major microprocessors.
PAPI enables software engineers to see, in near real time, the relation between software performance and processor events.
The Performance API (PAPI) project specifies a standard application programming interface (API) for accessing hardware performance counters available on most modern microprocessors.
These counters exist as a small set of registers that count Events, occurrences of specific signals related to the processors function. Monitoring these events facilitates correlation between the structure of source/object code and the efficiency of the mapping of that code to the underlying architecture.
This correlation has a variety of uses in performance analysis including hand tuning, compiler optimization, debugging, benchmarking, monitoring and performance modeling. In addition, it is hoped that this information will prove useful in the development of new compilation technology as well as in steering architectural development towards alleviating commonly occurring bottlenecks in high performance computing.
PAPI provides two interfaces to the underlying counter hardware; a simple, high level interface for the acquisition of simple measurements and a fully programmable, low level interface directed towards users with more sophisticated needs.
The low level PAPI interface deals with hardware events in groups called EventSets. EventSets reflect how the counters are most frequently used, such as taking simultaneous measurements of different hardware events and relating them to one another.
For example, relating cycles to memory references or flops to level 1 cache misses can indicate poor locality and memory management. In addition, EventSets allow a highly efficient implementation which translates to more detailed and accurate measurements.
EventSets are fully programmable and have features such as guaranteed thread safety, writing of counter values, multiplexing and notification on threshold crossing, as well as processor specific features. The high level interface simply provides the ability to start, stop and read specific events, one at a time.
PAPI provides portability across different platforms. It uses the same routines with similar argument lists to control and access the counters for every architecture. As part of PAPI, we have predefined a set of events that we feel represents the lowest common denominator of every good counter implementation.
Our intent is that the same source code will count similar and possibly comparable events when run on different platforms. If the programmer chooses to use this set of standardized events, then the source code need not be changed and only a fresh compilation and link is necessary. However, should the developer wish to access machine specific events, the low level API provides access to all available events and counting modes.
If an event or feature does not exist on the current platform, PAPI returns an appropriate error code. This significantly reduces the porting effort of code using PAPI because the semantics of each call to PAPI remains the same, just the argument lists need updating. In addition to the standard set, each PAPI implementation supports all native events through the ability to directly accept platform specific counter numbers. Definitions for most, if not all of these, are included as conditional macros in the header file. In this way, PAPI avoids having inefficient code to translate all events for all platforms into a uniform representation and back again.
This translation is only done for the relatively few events defined in the standardized set. Some processors like those in the POWER series have counter groups. They enable access to specific groups of counters, instead of individual events. This presents a serious portability problem, thus PAPI abstracts hardware counters from their groups with a packed naming scheme. Each counter control value or event is made up of the counter group number and the number of the specific counter in that group.
PAPI can be divided into two layers of software. The upper layer consists of the API and machine independent support functions. The lower layer defines and exports a machine independent interface to machine dependent functions and data structures. These functions access the substrate, which may consist of the operating system, a kernel extension or assembly functions to directly access the processors registers.
PAPI tries to use the most efficient and flexible of the three, depending on what is available. Naturally, the functionality of the upper layers heavily depends on that provided by the substrate. In cases where the substrates do not provide highly desirable features, PAPI attempts to emulate them as described below.
PAPI makes sure the underlying operating system or library guards against overflow of counter values.
Each counter can potentially be incremented multiple times in a single clock cycle. This combined with increasing clock speeds and the small precision of some of the physical counters means that overflow is likely to occur.
One of the more advanced features of PAPI is to provide a portable implementation of asynchronous notification when counters exceed a user specified value.
This functionality provides the basis for PAPIs SVR4 compatible profiling calls, that generate an accurate histogram of performance interrupts based on hardware metrics, not on time. Such functionality provides the basis for all line level performance analysis software, from the antiquated days of AT&Ts prof to SGIs SpeedShop. Thus for any architecture with even the most rudimentary access to hardware performance counters, PAPI provides the foundation for a truly portable, source level, performance analysis tool based on real processor statistics.
Enhancements:
- The API was extended to decouple abstraction layers from hardware support and to provide initial support for different types of performance counters.

Heroes project is a Nibbles-like game, just better.
Heroes is similar to the "Tron" and "Nibbles" games of yore, but includes many graphical improvements and new game features.
In it, you must maneuver a small vehicle around a world and collect powerups while avoiding obstacles, your opponents trails, and even your own trail.
There are five game modes available. Quest is the classical Nibbles, in Death Match you start with very long tails and must kill your opponents, in Killem All you must run over lemmings moving on the ground, in Time Cash or Color modes you must collect money or pyramids of color. Heroes features 12 original sound tracks, 94 levels (in 10 different tile sets) plus a level editor.
Heroes source code (distributed under the GNU General Public Licence version 2) originates from an original MS-DOS game but has been heavily modified to enhance the portability. Some new features have been added and MS-DOS support has been lost by the meantime. The original MS-DOS version can still be found on the Internet but is unmaintained and should be considered obsolete.
The current development concentrates on cleaning the code and porting the game to the various operating systems available. Our objective is to release the version 1.0 as a clean and portable base that would allow significant additions such as network support or programmable vehicles.
Enhancements:
- Support for the heroes-hq-sound-tracks package.
Bug fixes:
- soundconf: failed to override aliases.
- Heroes GGI driver failed to report an error if no two-frame mode was available.
- Various code nits.

Alice is a functional programming language based on Standard ML, extended with rich support for concurrent, distributed, and constraint programming.
Main features:
- Futures: laziness and light-weight concurrency with data-flow synchronisation
- Higher-order modules: higher-order functors and abstract signatures
- Packages: integrating static with dynamic typing and first class modules
- Pickling: higher-order type-safe, generic & platform-independent persistence
- Components: platform-independence and type-safe dynamic loading of modules
- Distribution: type-safe cross-platform remote functions and network mobility
- Constraints: solving combinatorical problems using constraint propagation and programmable search
The Alice System is a rich open-source programming system featuring the following tools:
- Virtual machine: a portable VM with support for just-in-time compilation
- Interactive system: an interpreter-like interactive toplevel
- Batch compiler: separate compilation
- Static linker: type-safe bundling of components
- Inspector: a tool for interactively inspecting data structures
- Explorer: a tool for interactively investigating search problems
- Gtk+: a binding for the Gnome toolkit GUI library
- SQL: a library for accessing SQL databases
- XML: a simple library for parsing XML documents
Enhancements:
- Alice now incorporates some of the proposed extensions for Successor ML.
- The bytecode jitter is now the default execution unit.
- The documentation includes a constraint programming tutorial, and the constraint library now uses the current stable version of Gecode.

CIP/Ethernet Library for Linux is the worlds premiere Linux-based software library for communicating with Allen Bradley ControlLogix Programmable Logic Controllers.

I have successfully completed negotiations with LSN of Birmingham Alabama to transfer the complete ownership of all things CELL related to them.

My motivations here are quite simple. I havent worked directly with a ControlLogix in the past 3 years as I am no longer in the Machine Tool industry at all. In fact, I seriously doubt that I will ever return to the machine tool industry - an industry not exactly known for its stability here in Michigan of late.

Anyhow, about LSN: they make cost-effective data logging / data historian products for a variety of platforms including Linux and Windows. They also use the CELL platform for their Allen Bradley based products. They have retained my services for continued support of the CELL library for the time being so there will be some continuity.

What I cant tell you is if any newer versions of the CELL library will remain under the GNU LGPL license. Obviously, any previously released version of CELL that was under the LGPL will remain under the LGPL - nothing can or will change that.

Versions going forward will be licensed at the sole discretion of LNS - not me.

I will shortly post a link to LNSs website page for CELL. They are the SOLE contact for ANY/ALL support needs for CELL.

APLoader stands for Another Postgres Loader, is a front-end to the Postgresql COPY command written in Ruby.

Features include:

fault tolerance
a progress meter
failed batch logs
minimal requirements
a programmable API
excellent performance.

The APLoaderproject is a PostgreSQL Community project that is a part of the pgFoundry.