Free mpich 1.4.0 software for linux

MP-MPICH provides a Multi-platform MPI implementation.

MP-MICH is a Multi-platform uniform MPI implementation, based on MPICH and SCI-MPICH, resulting in a high performance, consistent MPI across both ethernet and SCI networks in a hybrid environment. There is a single, standardized source tree for all platforms. It is compliant with the MPI-1 standard.

MP-MPICH uses one common source tree for this purpose. It has a new device for Windows NT/2000/2003 to communicate via sockets, and an adapted shared memory device for SMP systems. Additionally, MP-MPICH is a superset of SCI-MPICH, that means that it includes another new device to support direct communication via a fast SCI interconnect. With SCI-MPICH, inter-process message latencies for small messages (for processes running on separate nodes) below 4 us are achieved, and the current measured maximum inter-node (PingPong-)bandwidth is at about 310 MB/s.

In fact, the development of MP-MPICH started when the first release of SCI-MPICH was finished. This release was designed for Solaris and Linux, but since it uses our SMI library which is also available for Windows NT, we thought it would be fun to port SCI-MPICH to NT. The initial port took only 4 hours and we were up and running with SCI-MPICH for NT. The additional/modified devices which are necessary to use MPICH on NT without these extremely fast SCI boards required more time to develop.

MPICH2 is a robust and flexible implementation of the MPI (Message Passing Interface). Message Passing Interface is often used with parallel or distributed computing projects.

MPICH2 is a multi-platform, configurable system (development, execution, libraries, etc) for MPI. It can acheive parallelism using networked machines or using mulitasking on a single machine.

BibShelf is a book organizer integrating well with the GNOME desktop environment.
BibShelf project helps you to keep track of your book collection. You can fill in such things as the book summary, review, rating and the ISBN.

Never forget when it was that you read a book, BibShelf lets you save the date so you do no longer need to waste your brain capacity for storing this information.

mpiBLAST is an MPI based parallel implementation of NCBI BLAST. The project consists of a pair of programs that replace formatdb and blastall with versions that execute BLAST jobs in parallel on a cluster of computers with MPI installed. There are two primary advantages to using mpiBLAST versus traditional BLAST.

First, mpiBLAST splits the database across each node in the cluster. Because each nodes segment of the database is smaller it can usually reside in the buffer-cache, yielding a significant speedup due to the elimination of disk I/O. Second, it allows BLAST users to take advantage of efficient, low-cost Beowulf clusters because interprocessor communication demands are low.

mpiBLAST achieves super-linear speedup in situations where the database is too large to fit into RAM, and near linear speedup in other situations. It does not require a dedicated cluster.

c-ares project is a C library that resolves names asynchronously.
Enhancements:
- ares_save_options, ares_destroy_options, ares_process_fd, and ares_parse_ns_reply were added.
- The transaction IDs were made "secure".
- A few parsing issues and minor bugs were fixed.

Oggasm is a program that makes converting your mp3 collection into oggs a all but painless process.

Using oggenc and mpg321, with perl glueing it all together, oggasm is able to go through an entire collection, identify id3 tags and then convert those mp3s into oggs while keeping the id3 tags intact.

TODO:

server-client model: When oggasm is started I want it to creat a list of jobs that need to be done and then assign those jobs to various clients that could either be running on the same machine or on other machines connected via a network.

Im of two minds on how to do this. Either I learn how to use sockets and develop my own communication protocol to tell the clients what to do, or I create physical files that are grabed by the client via ftp or samba. Each one has its advantages and disadvantages and I hope to look into it more soon.

One thing that is very important is that a client machines need to be able to come and go as necessary. So oggasm might start with 2 clients, be at 5 later in the day, and then down to 1 when it all finishes.

network functionality: How this will look will rest largly on how the server-client model ends up looking. But most likely the it will involve using ftp or samba to grab files from the server machine, convert them, and then send them back to the server. After that the
client will be assigned a new job.

improvments to user interface: This will be a on going process. As I continue to get more feedback on how people felt their experience with oggasm was I can improve how it the interface looks. Recent changes with 1.3 will allow updates to the interface to be much smother than before.

more encoder/decoder options: certainly oggenc will remain the primary encoder, however other free codecs might come along someday, and it would be nice if oggasm was modular enough to beable to plug in different encoders. I would also like to support different decoders as not everyone has mpg321 (however I will NOT provide support of non-free decoders).

innotop project is a MySQL and InnoDB monitor that lets you view and manage whats happening inside your MySQL servers.

Features include a top-like query list, a top-like InnoDB transaction list, and much more. This tool gives you a high level of insight into the inner workings of InnoDB.