Free grey software for linux

WoodPusher is a chess application written in C# for the Mono framework.

While in early development, the intention is for WoodPusher to become a full-featured chess application, including the ability to connect to ICS (Internet Chess Servers), play against engines such as Crafty, Phalanx, and gnuchess, and lookup positions in move databases.

Initially Were focusing on its ICS client abilities. This is a great project to get involved with if you want to get your hands dirty with some C# and Gtk#.

Volumevis displays pixel-based 3-dimensional datasets. 3-D pixel datasets mostly come from 3-D computer tomography (CT) and magnetic resonance (MR) images. These datasets usually come in the form of a set of 2-D picture files each being a slice of the 3D dataset.
To be displayed by volumevis, the files have to be ordered with identical names except for a number somwhere in the name corresponding to the slice number. Most image formats (jpg, tiff, dicom, etc ..) are supported.
Volumevis is a tool for visualizing 3D dimensional pixel-based datasets. Most computer 3D visualization in the world is with surfaced-based visualization. This is true for most 3D games, CAD tool, etc.
By stating it simply, surface-based rendering works by dividing a predefined surface into small triangles, and then sending those triangles along with their color to graphicscard to be rendered. For example,if you want to render a sphere in 3D, you would create a surface of the sphere, divide it into triangles, send the triangles to the graphics card, which would then turn the triangles into pixels and displaythem.
The unfortunate side-effect of this is, that if you happen to cut the sphere, or go inside it, you will see that its in fact hollow. Also, you cannot see any of the details that might be inside of the sphere.
Volume visualization is the equivalent in 3D of displaying a photo in 2D. The surface 3D visualizations on the other hand, are the equivalent of reducing a photo to a representation of lines (such as the outlines of people and houses) and drawing the lines on screen. Obviously a lot of information goes lost in the line representation.
The visualization works like this. In openGL (a graphics programming API), all fragments (3D equivalent of pixels) have an alpha value. The alpha value corresponds to the opacity of the fragment. If the fragment has a small alpha value, it will be easy to see through it and see the fragments behind it.
If the alpha value is high, the fragments behind it will be obscured. A 3D dataset is simply a block of data in the shape of a cube. Somewhere in the image there is an object which is white or grey. All the other places in the image are black. To render the object, all the pixels which are black are assigned and alpha value of 0 (meaning they are transparent). Therefore we dont see the black pixels.
The fragments belonging to the object are white and have an alpha value higher than zero. Therefore its not possible to see through them, and we perceive the location of the object fragment to be the surface of the object. Depending on the alpha value of the fragment, we might also be able to see some of the fragments behind it a bit (see inside the object).
At the moment, Volumevis only supports black/white images (which is fine for most CT and MRI datasets).
Enhancements:
- A bug with slice loading of textures which are not a power of two was fixed.
- Movie recording, cropping, and file saving for slices were fixed.
- Various feature improvements were made.

FreeType 1 is a portable and highly efficient TrueType rendering engine, that is now successfully used to bring TrueType support to a very large variety of platforms and environments, be they font servers, graphics libraries or embedded systems.
FreeType 1 is a clean-room implementation that is not derived from the original TrueType engine developed by Apple and Microsoft. It has been created with the sole help of the published TrueType specifications, which to our great surprise (and pain) turned out to be extremely poor and misleading in critical areas. Much hard work has been undertaken to solve ambiguities. The end result is a portable and fast renderer.
Note that FreeType 1 is a library. It is not a font server for your favorite platform, even though it was designed to be used in many of them. Note also that it is not a complete text-rendering library. Its purpose is simply to open and manage font files, as well as load, hint and render individual glyphs efficiently. You can also see it as a "TrueType driver" for a higher-level library, though rendering text with it is easy, as demonstrated by the test programs.
Its quality matches these of Windows and the Macintosh, while its memory foot-print and code size (between 48 and 55 kByte of Intel code) remain modest. A thing that cannot be said for most other commercial engines available.
Main features:
- Supports TrueType files (TTF) and collections (TTC). Doesnt support GX or OpenType fonts, but these can be opened and used as normal TTF files by the library. (With the exception of OTF OpenType fonts which really embed a Type 1 font file within a TrueType storage).
- Modular design: Memory and I/O operations can be very easily tailored to your own platform/system (the standard release comes with ANSI libc support).
- Font smoothing, a.k.a. gray-scaling. Just like Win95, the renderer only smoothes the parts of a glyph which need it (i.e., diagonals and curves).
- Support for all character mappings defined in the TrueType specification. The client application can select whichever pleases it.
- A full-featured and efficient TrueType bytecode interpreter. The engine is able to produce excellent output at small point sizes. This component has been extremely difficult to get right, due to the ambiguous and misleadings TrueType specifications. However, we now match Windows and Mac qualities.
- Written in portable ANSI C (and Pascal, for older FreeType 1 versions). Should compile well on all kinds of systems (tested on 16, 32 and 64 bits processors). With full source code available.
- Open Source License. FreeType can be included in all kinds of commercial systems and software.
- Provides test programs to "show-off" the library, runnable on the following platforms: Dos, Unix, OS/2, Win95, and Amiga. Any porters for other systems are welcome and should contact the developers team.
- Support for extensions. These are separately linkable units which can be used to enhance the engines functionalities without recompiling it. They can be written to access additional TrueType tables, or even GX and/or OpenType ones (the latter is already available).
- Kerning support: The TrueType kerning data is available through one of the standard extensions that comes in this release. However, it is up to the application to "interpret" the data, as many different `formats are supported.
- Support for vertical metrics. The engine is able to provide client applications with vertical glyph metrics if they are found in font files (usually in CJKV fonts). If not present, it synthetizes metrics from the horizontal values, ascender, and descender metrics. This means that it is possible to render vertical text correctly.
- Standard extensions are provided to access and load the glyph names in the Postscript table.

AlienDrive Live CD is a linux distribution based on the SLAX Operating System.

It is sometimes affectionately referred to by the people who love it as "The Alien". It was designed specifically to function as a Digital Audio Workstation and Pre/Post Video Production platform.

The system core is based on a compressed module design that has been carefully tuned to reach a level of performance so advanced, it is thought to have come from the enigmatic Gray Aliens We hope you enjoy meeting The Alien

Live CD login username: root password: toor

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details

Jaaa is short from JACK and ALSA Audio Analyser, is an audio signal generator and spectrum analyser designed to make accurate measurements.

Frequency and Amplitude

These two sets of buttons set the display view. One of these six buttons, or Bandw, Peak, or Noise discussed below, has an orange LED at its left side. The LED indicates the currenty selected parameter that usually can be modified in three ways:

- by typing a new value into the text widget, followed by ENTER,
- by using the < or > buttons to decrement or increment,
- by mouse gestures.

Frequency:

Min and Max set the min and max displayed frequencies. If either of these is selected then

a horizontal Drag Left changes Min,
a horizontal Drag Right changes Max.

Cent is the frequency at the middle of the x-axis.
Span is Max - Min, changing this value preserves Cent.
If either of these is selected then

a horizontal Drag Left changes Cent,
a horizontal Drag Right changes Span.

Cent can also be set by Clicking in the frequency axis scale.

Amplitude:

Max is the maximum value on the y-axis.
Range is the range of the y-axis.
If either of these is selected then

a vertical Drag Left changes Max,
a vertical Drag Right changes Range,

So for the last four mouse gestures, a Drag Left will scroll the display, while a Drag Right will zoom in or out. Maybe I will add and automatic selection of the axis based on the direction of the mouse gesture.

Analyser

The analyser is based on a windowed FFT. Actually the windowing is performed by convolution after the FFT, and combined with interpolation. The windowing and interpolation ensure that displayed peaks will be accurate to 0.25 dB even if the peak falls between the FFT bins. More accurate measurements can be made using the markers (see below).

Bandw sets the FFT length, and hence the bandwidth of the analyser. Depending
on this value, the size of the display and the frequency range, you may sometimes
see two traces. This happens when the resolution of the analyser is better than the
display, so that one pixel contains more than one analyser value. In that case, the
blue trace is the peak value over the frequency range represented by each pixel, and
the gray one is the average value. The first one is correct for discrete frequencies,
and the latter should be used to read noise densities. There is no mouse gesture to change the bandwidth.

VidAv or video average, when switched on, averages the measured energy over time.

This is mainly used to measure noise. The averaging lenght increases over time, to
a maxumum of 1000 iterations. Changing the input or bandwidth resets and restarts
the averaging.

Freeze freezes the analyser, but not the display, so you can still scroll and zoom or use the markers discussed below.

Markers

Markers are used in order to accurately read off values in the display. There can be
up to two markers, set by clicking at the desired frequency inside the display.

When there are two markers, the second one will move with each click, while the first
remains fixed. Measured values for the two markers, and their difference in frequency
and level are displayed in the upper left corner of the display.

Clear clears the markers.

When Peak is selected, clicking inside the display will set a marker at the nearest
peak. The exact frequency and level of the peak are found by interpolation, so the
frequency can be much more accurate than the FFT step, and the level corresponds to the true peak value regardless of display or analyser resolution.

When Noise is selected, clicking inside the display will set a noise marker. The noise density (energy per Hz) is calculated and displayed.

BCCD - Bootable Cluster CD was created to facilitate instruction of parallel computing aspects and paradigms. Part of the difficulty instructors face is lack of dedicated resources to explore distributed computing aspects lack of time to preconfigure and test the supporting environment.

The BCCD image addresses this problem by providing a non-destructive overlay way to run a full-fledged parallel computing environment on just about any workstation-class system...Were happy to say that this now includes the MAC too!

The BCCD does share similarities with a few diskless solutions for clustering, such as the Warewulf project, the thin-OSCAR approach, Cluster Knoppix (only an openMosix system, no MPI/LAM/PVM build tools, ...), and so on. This is definitely the trend in HPC. But the main differences are that the BCCD will always fit in your pocket, be highly customizable for specific institutions needs, and will always be geared toward education and not dedicated clusters.

The "gar" build system also sets the BCCD apart from other projects. "gar" is a mix between BSDs "ports" system, Linux from scratch, and gentoo Linux. With gar, you can build an entire BCCD image from net-fetched sources in about two hours (assuming you have a primed ccache!).

The BCCD is also distinctly different from NPACI-Rocks, OSCAR, Cluster in a box or other type of mass-imaging clustering project for two reasons:

1. Its a non-destructive overlay on top of the current hardware. Once a system is rebooted, it reverts back to its original state. It is intended to be booted "over top" of a currently-configured Windows/Linux/BSD/etc. system.
2. Its focus in on educational aspects of High-Performance Computing (HPC) instead of the HPC core. Students will have a much better appreciation and understanding of how to tweak an MTU setting or wire the topology across a cluster if they understand how a distributed computation is laid out! Emphasis is placed upon building, configuring, and running distributed applications.

Imagero Reader is a Java library for reading image files. Supported file types include BMP, GIF, TIFF, PNG, JNG, MNG, JPEG (including 12-bit grey), PSD, PBM, PGM, PPM, TGA, EPS, EPSI, and EPSF.
The following RAW file types are also supported, at least partially: MRW, CRW, NEF, DCR, and DNG. It can read thumbnails, read metadata (IPTC, EXIF, and XMP), edit metadata, get image width and height, get the number of images contained in a file, define an area to read, add a ProgressListener, choose an image channel to read, set a scale factor, set subsampling (JPEG only), and read an image (or channel) directly into an array.
Supported file types are:
- BMP 1, 4, 8, 16, 24 and 32 bit uncompressed; 4 and 8 bit compressed
- GIF
- TIFF 1, 4, 8, 16, 32, 48 and 64 bit per pixel; bilevel, grayscale, palette, RGB, CMYC, Cie Lab, YCrCb color spaces; CCIT1D, G3, G4, ZIP, JPEG, LZW and PackBits compression
- PNG, JNG, MNG
- JPEG inclusive CMYC and 12-bit grey
- PSD
- PBM, PGM, PPM
- TGA
- read embedded images from EPS, EPSI, EPSF
Supported RAW files:
- MRW
- CRW*, CR2*, THM
- NEF*
- DCR*
- DNG*
- Full resolution image cant be yet read, but thumbnail, preview and metadata can be read.
Main features:
- read thumbnails
- read/edit metadata
- any metadata contained in ImageResourceBlock ( PSD, JPEG, TIFF) and ImageFileDirectrory entry ( TIFF, NEF, DNG, DCR) can be edited full control over JPEG metadata
- get image width and height
- get number of images, contained in file
- define an area to read
- add a ProgressListener
- estimate JPEG compression/quality
- read an image channel
- set a scale factor
- set subsampling (JPEG only)
- read an image (or channel) directly into an array
- easy IPTC handling with IPTCParser and IPTCEditor
Whats New in 1.9.6 Stable Release:
- The EPS parser was partially rewritten and made more generic and easy to use.
- It may be used now to parse nearly every kind of data (as a programmable parser).
- Thumbnails are read from AI (Illustrator) files.
- Disc based image caching was implemented (but is beta).
- New methods were added to TiffUtils: insert IFDEntry, remove IFDEntry, and create and insert IFDEntry with IPTC data.
- Two utility classes were added for creating and adding EXIF and GPS data to TIFF images.
- An important bug in XMPApp1 concerning wrong field length was fixed.
Whats New in 2.0.0 RC3 Development Release:
- It is possible to write TIFF images now. TiffWriter can currently write RGB, ARGB, CMYK, and grayscale (8 bit) images.
- Supported compression schemes are uncompressed, PackBits, and ZIP.
- Bugfixes were made.