Free fusion protein 3d structure prediction software for linux

Erwin Data Structures is a library that is meant to be the ultimate data structure library for mixed usage of C and C++.

Arbitrary key and value types are implemented by template files that dont use C++ templates, but are instantiated by a Perl script.

This way, mixed usage in C and C++ is possible. However, a C++ interface is generated to support the advantages of the C++ language. No templates, no void*.
Erwin contains a number of tools, too, all of them written in Perl. The following list shows the data structures and tools, together with some typical examples.

GraphViz::Data::Structure can visualise data structures.

SYNOPSIS

use GraphViz::Data::Structure;

my $gvds = GraphViz:Data::Structure->new($data_structure);
print $gvds->graph()->as_png;

This module makes it easy to visualise data structures, even recursive or circular ones.
It is provided as an alternative to GraphViz::Data::Grapher. Differences:

GraphViz::Data::Structure handles structures of arbitrary depth and complexity, automatically following links using a standard graph traversal algorithm.
GraphViz::Data::Grapher creates graphics of indiividual substructures (arrays, scalars, hashes) which keep the substructure type and data together; GraphViz::Data::Structure does this by shape alone.
GraphViz::Data::Structure encapsulates object info (if any) directly into the node being used to represent the class.
GraphViz::Data::Grapher colors its graphs; GraphViz::Data::Structure doesnt by default.
GraphViz::Data:Structure can parse out globs and CODE references (almost as well as the debugger does).

FusionSound project is an audio sub system for multiple applications.
FusionSound is a very powerful audio sub system in the manner of DirectFB and a technical demonstration of Fusion.
FusionSound supports multiple applications using Fusion IPC. It provides streams, static sound buffers and control over any number of concurrent playbacks.
Sample data is always stored in shared memory, starting a playback simply adds an entry to the playlist of the mixer thread in the master application.
FusionSound currently is a module of DirectFB. The current API is fully implemented and the complete code is smaller than just the header file of DirectFB!
FusionSound future plans include interfaces for hardware/software codecs, hardware gain control, device configuration and different device backends (currently OSS only).
Enhancements:
- Fixed CDDB discid computation.
- Search for CDDB disc data iterating through all categories.

XML::Structured is a simple conversion API from XML to perl structures and back.

SYNOPSIS

use XML::Structured;

$dtd = [
element =>
attribute1,
attribute2,
[],
element1,
[ element2 ],
[ element3 =>
...
],
[[ element4 =>
...
]],
];

$hashref = XMLin($dtd, $xmlstring);
$hashref = XMLinfile($dtd, $filename_or_glob);
$xmlstring = XMLout($dtd, $hashref);

The XML::Structured module provides a way to convert xml data into a predefined perl data structure and back to xml. Unlike with modules like XML::Simple it is an error if the xml data does not match the provided skeleton (the "dtd"). Another advantage is that the order of the attributes and elements is taken from the dtd when converting back to xml.

Image::MetaData::JPEG::Structures is a Perl module that describes the structure of a JPEG file; it is an appendix to the main manual page of the Image::MetaData::JPEG module, which the reader should refer to for further details and the general scope.

THE STRUCTURE OF JPEG PICTURES

The JPEG (Joint Photographic Experts Group) ISO standard is a lossy image compression mechanism developed before 1990, designed for compressing colour or gray-scale photo-realistic images (it performs poorly on line-art drawings). The JPEG mechanism is designed to exploit known limitations of the human eye, in particular the fact that colour changes are perceived less accurately than changes in brightness.

Note that although the "baseline" JPEG format is patent-free, there are patents associated with some optional features, namely arithmetic coding and hierarchical storage. For this reason, these optional features are never used on the Web (good job, patent fans ...). JPEG refers only to a class of compression algorithms, not to a specific file format. In order to produce files with embedded JPEG streams, a number of file format (semi-)standards have been adapted or devised, some of which are listed in the format section. The structure of a well formed JPEG file can be described by the following pseudo production rules (for sake of simplicity, some additional constraints between tables and SOF segments are neglected).

JPEG --> (SOI)(misc)*(image)?(EOI)
(image) --> (hierarch.)|(non-hier.)
(hierarch.) --> (DHP)(frame)+
(frame) --> (misc)*(EXP)?(non-hier.)
(non-hier.) --> (SOF)(scan)+
(scan) --> (misc)*(SOS)(data)*(ECS)(DNL)?
(data) --> (ECS)(RST)
(misc) --> (DQT)|(DHT)|(DAC)|(DRI)|(COM)|(APP)

(SOI) = Start Of Image
(EOI) = End Of Image
(SOF) = Start Of Frame header (10 types)
(SOS) = Start Of Scan header
(ECS) = Entropy Coded Segment (row data, not a real segment)
(DNL) = Define Number of Lines segment
(DHP) = Define Hierarchical P??? segment
(EXP) = EXPansion segment
(RST) = ReSTart segment (8 types)
(DQT) = Define Quantisation Table
(DHT) = Define Huffman coding Table
(DAC) = Define Arithmetic coding Table
(DRI) = Define Restart Interval
(COM) = COMment segment
(APP) = APPlication segment

This package does not check that a JPEG file is really correct; it accepts a looser syntax, were segments and ECS blocks are just contiguous (basically, because it does not need to display the image!). All meta-data information is concentrated in the (COM*) and (APP) Segments, exception made for some records in the (SOF*) segment (e.g. image dimensions).

Reference: B< "Digital compression and coding of continuous-tone still
images: requirements and guidelines", CCITT recommend. T.81, 1992,
The International Telegraph and Telephone Consultative Committee,
standard ISO/IEC IS 10918-1 or ITU-T Recommendation T.81 >.
Also: B< "The JPEG still picture compression standard", G.K.Wallace,
1991, IEEE Transactions on Consumer Electronics >.

Bio::Tools::Run::PiseApplication::consensus is a Perl module.

Bioperl class for:

CONSENSUS Identification of consensus patterns in unaligned DNA and protein sequences (Hertz, Stormo)

References:

G.Z. Hertz and G.D. Stormo. Identification of consensus patterns in unaligned DNA and protein sequences: a large-deviation statistical basis for penalizing gaps. In: Proceedings of the Third International Conference on Bioinformatics and Genome Research (H.A. Lim, and C.R. Cantor, editors). World Scientific Publishing Co., Ltd. Singapore, 1995. pages 201--216.

Parameters:

(see also:
http://bioweb.pasteur.fr/seqanal/interfaces/consensus.html
for available values):


consensus (Excl)
Program to run

sequence (Sequence)
Sequences file (-f)
pipe: seqsfile

width (Integer)
Width of pattern (consensus only) (-L)

out (String)

consensus_matrix (String)

complement (Excl)
Complement of nucleic acid sequences (-c)

ascii_alphabet (InFile)
Alphabet and normalization information (if not DNA) (-a)

prior (Switch)
Use the designated prior probabilities of the letters to override the observed frequencies (-d)

dna (Switch)
Alphabet and normalization information for DNA

protein (Switch)
Alphabet and normalization information for protein

queue (Integer)
Maximum number of matrices to save between cycles of the program -- ie: queue size (-q)

standard_deviation (Float)
Number of standard deviations to lower the information content at each position before identifying information peaks (mandatory for wconsensus) (-s)

progeny (Excl)
Save the top progeny matrices (-pr1)

linearly (Switch)
Seed with the first sequence and proceed linearly through the list (-l)

max_cycle_nb (Integer)
Maximum repeat of the matrix building cycle (-n or -N)

max_cycle (Excl)
How many words per matrix for each sequence to contribute (-n or -N)

distance (Integer)
Minimum distance between the starting points of words within the same matrix pattern (-m)

terminate (Integer)
Terminate the program this number of cycles after the current most significant alignment is identified (-t)

terminal_gap (Excl)
Permit terminal gaps (-pg) (wconsensus only)

top_matrices (Integer)
Number of top matrices to print (-pt)

final_matrices (Integer)
Number of final matrices to print (-pf)

Structured Document Validator project implements a generalized method for validating both the structure and content of structured documents.

Any data format that can be deterministically divided into tags and data is classed as a structured document. This definition applies to a wide array of data formats, including XML, Java properties files, and delimited value files.

The application performs validations based on user-defined Structured Document Definitions (SDDs). It provides an environment for validation, SDD development, and document editing.

VXL (the Vision-something-Libraries) is a collection of C++ libraries designed for computer vision research and implementation. The project was created from TargetJr and the IUE with the aim of making a light, fast and consistent system. VXL is written in ANSI/ISO C++ and is designed to be portable over many platforms.

The core libraries in VXL are:

vnl (numerics): Numerical containers and algorithms. e.g. matrices, vectors, decompositions, optimisers.
vil (imaging): Loading, saving and manipulating images in many common file formats, including very large images.
vgl (geometry): Geometry for points, curves and other elementary objects in 1, 2 or 3 dimensions.
vsl (streaming I/O), vbl (basic templates), vul (utilities): Miscellaneous platform-independent functionality.

As well as the core libraries, there are libraries covering numerical algorithms, image processing, co-ordinate systems, camera geometry, stereo, video manipulation, structure recovery from motion, probability modelling, GUI design, classification, robust estimation, feature tracking, topology, structure manipulation, 3d imaging, and much more.

Each core library is lightweight, and can be used without reference to the other core libraries. Similarly, the non-core libraries dont depend on more than absolutely necessary, so you can compile and link just the libraries you really need.