Gos4j is a way of organising processing priorities based on goals. Each goal is prioritised to be processed based on its time to complete and its progress towards that goal. Deadlines are used to act as the target completion time for a goal, and can be expressed in either relative or absolute terms. It can be used to support an unknown processing environment with real time constraints. A typical example of this would be in an application programming set-up, where user code would run alongside your code, and so fixed priority scheduling may not be efficient. Gos4j can easily reschedule threads to meet as many of the specified constraints as possible, so overall performance will degrade gracefully and conflicting time constraints will be handled equitably.
Japha is an effort to implement the major functionality of the Java library in PHP. The functionality captured in the JPI includes I/O, utility classes such as data structures, Web service architecture, and reflection classes, lang classes for implementing a standardized API, bean classes for creating a standard bean implementation, SQL classes for database persistence (via the Web service architecture), and database abstraction as well as Object-Relational mapping, networking functionality, and even some complex math.
Antipodes.Cubes is a BPM system for visual modeling and automation of processes. Processes are designed visually as block diagrams in a graphical environment called WfArchitect. The logic and flow of the processes are reflected in the different containers (blocks or shapes) and the connections between them. It supports task, condition, user decision, code, timer, and scheduler containersm and allows for the inclusion of subprocesses in processes and also recursive use of subprocesses.
DIET Agents is a multi-agent platform in Java. A bottom-up design is used to ensure that the platform is lightweight, scalable, robust, adaptive, and extensible. It is especially suitable for rapidly developing peer-to-peer prototype applications and/or adaptive, distributed applications that use bottom-up, nature-inspired techniques.
Blitz is an open source JavaSpaces implementation designed to ease development and deployment of JavaSpaces technology. It is Jini 2.0 enabled, and uses established VM principles. It also implements smart indexing, tuneable persistence, and active/passive lease cleanup. It is designed with experimentation and expansion in mind.
nexB OpenAssets is a tool for inventorying, managing, and monitoring applications, software, hardware, networks, and generally any IT asset. It is designed so that system administrators, IT, and finance can determine what they have, how it is configured, what it is used for, and how much it is being used, so that informed decisions can be made. It complements existing network management software, integrates with a growing number of protocols and tools, and features no-agent discovery and inventory, configuration management including dependencies and correlation, monitoring, and reporting. It makes extensive and innovative use of XML, Xpath, and Xquery.
RapidMiner (formerly YALE) is a flexible Java environment for knowledge discovery in databases, machine learning, and data mining. Many nestable learning and preprocessing operators (including Weka) are provided. It features an XML-based graphical user interface, a plugin mechanism, and high-dimensional plotting, and provides an easy-to-use extension mechanism that makes it possible to integrate new operators and adapt the system to your personal requirements. A command line version is also included.
Madison is a ongoing effort to provide high quality access to modern and effective computer technology for individuals who are blind and have a severe limit on mobility or control which limits the use of standard input technologies. It bases input on a joystick and three switches. The joystick can be thought of as a navigation aid like the cursor keys up, down, left, and right. An expanded Morse (eMorse) code is used to replace the keyboard; the three buttons represent dot, dash, and meta. Applications are installed on a graph filesystem. Each filesystem node has up to four vertices, named north, south, east, and west. Navigation is done via joystick or eMorse input. Applications are deployed as jar files which are retrieved by the Web or local disk.