Free programmable thermostat software for linux

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.

Paranormal is an extremely customizable (pseudo-programmable) audio visualization library, based (conceptually) on Winamps AVS plugin. Paranormals goal is to be as flexible as possible by providing a number of actuators that perform various tasks involved in generating an image.

These actuators can then be combined to create a nearly unlimited number of effects. These combinations can be saved to a file to be brought back later.

GibberMonkey is a Javascript scriptable IRC bot that is programmable from the chat room. It is the result of a marriage between the SpiderMonkey engine and the SmartIrc4Net library.

SmartIrc4Net is a C# library providing an API for communicating with an IRC server. Part of the purpose of GibberMonkey is to be the usability testbed for the new generic object embedding in spidermonkey-dotnet. It is written in C#, and is maintained on both the .Net and Mono platforms.

The system can be used in the electronic world to keep track of your: Schematic, Printed Circuit Board, Front Plate, Programmable Logic Device numbers.
EDA index is programmed in PHP (and XHTML 1.0), using a MySQL database to store data, so its more or less OS independent, but a Linux server is recommended, since it already got most software installed as default, this configuration is also called LAMP (Linux Apache MySQL PHP)
Its also recommended that a local intranet server is used, since the system dont got a user login, so all data can be viewed without a password, but when you need to add or edit data a password is required. At first this approach might seem wierd, but its designed to allow quick lookups. Example:
You are sitting with a broken pcb with a number on it, and need to find the schematic (so you can repair it) on the computer or in the printed project (schematic) archive. EDA Index allow an quick lookup in the database, without you needing to login, so you get the job done faster.
As far as I know, there are no commercial (or free) program available that can do what EDA Index can, some companies may have created their own software, but how do that help you.
I have worked in an electronic department that had a self made application, but it lagged features like search.
This program is very usefull, if you are using numbers when:
Drawing electronic Schematics and PCBs using a CAD program like: Eagle, gEDA, Protel, Orcad, etc.
Creating Front Plate layouts in: GIMP, Coral Draw, Photoshop, AutoCAD, etc.
Programming Programmable Logic Devices like: PLD, EPLD, CPLD, PIC, APIC, PEEL, PAL, GAL, FPGA, Intel 80XX, Motorola 68XX, etc. Writing the code in: VHDL, Assambler, JEDEC, etc.
Enhancements:
- Included the bugfix to RC2.
- Updated online documentation.
- Updated INSTALL file.

Metronomos provides a programmable metronome.

Metronomos is a programmable metronome which can export to wav files.

It can vary the speed, time signature, note value, and click sound of its beats.

JGraphpad is a powerful, free diagram editor based on JGraph. It is currently available in English, French and German. With JGraphpad, you can create flow charts, maps, UML diagrams, and many other diagrams.
JGraphpad is provided as an example for the JGraph Swing component. Check out the JGraphpad applet and Web Start version.
JGraphpad is a versatile product that may be used to display and edit any type of diagram in the following fields:
- Knowledge Visualization
- Business Diagramming
- Software Engineering
- Monitoring and Configuration
- Transport Networks
- Workflow Systems
Main features:
- Supported Languages: English, French, German, Spanish, Japanese, Indonesian, Thai, Portuguese
- Flexible configuration, enable/disable features, toolbar buttons, add custom commands
- Programmable toolbar, GUI, and features (create your own toolbar buttons)
- Supports a wide range of platforms (Windows, Linux, Mac, Solaris)
- Copy and paste or drag and drop to and from Java and native applications
- Import/Export Text files, GXL, GIF, JPG, PNG, EPS, HTML Image maps, and GraphViz Dot
- Object library with flexible creation and management
- Shortest path and "spanning tree" selection
- 8 Different Automatic layouts
- Overview with Panning and Zoom
- Command History
- Printing and much more...
Enhancements:
- The release now compiles with JGraph 5.6.3, changing the use of graph references in various renderers.
- Some unused code was removed and various Javadocs were cleaned up.