Ports Search

Phred reads DNA sequencer trace data, calls bases, assigns quality values to the bases, and writes the base calls and quality values to output files. Trace data is read from chromatogram files in the SCF, ABI, and EST formats, even if they were compressed using gzip, bzip2, or UNIX compress. Quality values are written to FASTA format files or PHD files, which can be used by the Phrap sequence assembly program in order to increase the accuracy of the assembled sequence. Base calling and quality value accuracies tested for: ABI models 373, 377, and 3700 Molecular Dynamics MegaBACE LI-COR 4000 Base calling accuracies tested for: ABI model 3100 Beckman CEQ It contains also a data evaluation program called 'daev'. See DAEV.DOC for more information. You must obtain the tarball via e-mail to build. See the web site below.

This is a port of btoa version 5.2, written by Paul Rutter, Joe Orost & Stefan Parmark. btoa converts 4 binary characters to 5 ascii ones, causing a 25% expansion. (btoa is thus more efficient than uuencode, which causes a 33% expansion.) Spaces will not be used, which should make it safe to send files over e-mail or Usenet without risking that blanks become tabs. Each resulting row of text has a single-byte checksum for error detection. A diagnosis file provides a list of errors found this way, which could then be used to retransmit only the failing lines. Patch 1 is an unofficial, non-platform-specific patch to version 5.2 of btoa. It allows for automatic decoding of btoa files if the program is invoked as "atob" (no -a argument necessary). It also outfits the Makefile to do clean and install.

This package contains a base64 encoder/decoder and a quoted-printable encoder/decoder. These encoding methods are specified in RFC 2045 - MIME (Multipurpose Internet Mail Extensions). The base64 encoding is designed to represent arbitrary sequences of octets in a form that need not be humanly readable. A 65-character subset ([A-Za-z0-9+/=]) of US-ASCII is used, enabling 6 bits to be represented per printable character. The quoted-printable encoding is intended to represent data that largely consists of bytes that correspond to printable characters in the ASCII character set. Non-printable characters are represented by a triplet consisting of the character "=" followed by two hexadecimal digits. The MIME::Base64 and MIME::QuotedPrint modules used to be part of libwww-perl package. They are now distributed separately (this package). The main improvement is that the base64 encoder/decoder is implemented by XS functions. This makes it about 20 times faster than the old implementation in perl.

GNU Data Access (GDA) is an attempt to provide uniform access to different kinds of data sources (databases, information servers, mail spools, etc). It is a complete architecture that provides all you need to access your data, defined by a set of CORBA interfaces as generic as possible (but very powerful at the same time) so that any kind of data source can be accessed through them. libgda is an interface to the GDA architecture, providing a nice wrapper around the CORBA interfaces, for both the client and the server parts. It also provides a bunch of tools to help you both in the development and management of your data sources, all done through the GDA model's set of CORBA interfaces. libgda was part of the GNOME-DB project, but has been separated from it to allow non-GNOME applications to be developed based on it.

GNU Data Access (GDA) is an attempt to provide uniform access to different kinds of data sources (databases, information servers, mail spools, etc). It is a complete architecture that provides all you need to access your data, defined by a set of CORBA interfaces as generic as possible (but very powerful at the same time) so that any kind of data source can be accessed through them. libgda is an interface to the GDA architecture, providing a nice wrapper around the CORBA interfaces, for both the client and the server parts. It also provides a bunch of tools to help you both in the development and management of your data sources, all done through the GDA model's set of CORBA interfaces. libgda was part of the GNOME-DB project, but has been separated from it to allow non-GNOME applications to be developed based on it.

This is gpaint, a small-scale painting program for GNOME, the GNU Desktop. Gpaint does not attempt to compete with GIMP. Think of GIMP is like Photoshop as gpaint is like Windows Paint. Gpaint is still work in progress and many features are still being developed. However, gpaint is useable already for small image markups. A large part of gpaint is derived from xpaint 2.4.9, authored by David Koblas and later Torsten Martinsen. Gpaint also uses the gtkscrolframe widget (taking from eog 0.5) by Federco Mena-Quintero. Future plans include the implementation of missing features, printing support, and turning gpaint into a Bonobo component for simple image editing tasks. For bugs or general comments please send mail to Andy Tai, atai@atai.org

The main purpose of LibMorph is loading (and saving) 3d models (3d modeller object files). Given loader is dynamically linked when format of requested file is recognized. The library is very young piece of software, so chances are high that some things don't work yet as they should or at all. If you have need for some particular feature, drop me a mail, I'll try to reprioritize my TODO list. LibMorph currently supports following formats (only loading at the moment): LWOB -- LightWave[TM], 3DS -- 3D Studio[TM], In future hopefully it'll support: ? -- Alias Wavefront[TM] MAX -- 3D Studio Max[TM] DXF -- CAD? ? -- Maya[TM] ? -- Soft Image[TM] SVG -- XML, 2d Vector files converted to 3d (via libart?) and more

Rancid monitors a router's (or device's) configuration, including software and hardware (cards, serial numbers, etc), using CVS. Rancid currently supports Bay routers, Cisco routers, Juniper routers, Catalyst switches, Foundry switches, Redback NASs, ADC EZT3 muxes, MRTd (and thus likely IRRd), Alteon switches, HP Procurve switches, Hitachi routers. Rancid logs into each of the devices in a router table file, runs various commands, chomps the output, and emails any differences from the previous collection to a mail list. A looking glass is also included with rancid, based on Ed Kern's in use on http://nitrous.digex.net/. Rancid version has added functions, supports Cisco, Juniper, and Foundry and uses the login scripts that come with rancid; so it can use rsh, telnet, or ssh to connect to your router(s).

Rancid monitors a router's (or device's) configuration, including software and hardware (cards, serial numbers, etc), using CVS. Rancid currently supports Bay routers, Cisco routers, Juniper routers, Catalyst switches, Foundry switches, Redback NASs, ADC EZT3 muxes, MRTd (and thus likely IRRd), Alteon switches, HP Procurve switches, Hitachi routers. Rancid logs into each of the devices in a router table file, runs various commands, chomps the output, and emails any differences from the previous collection to a mail list. A looking glass is also included with rancid, based on Ed Kern's in use on http://nitrous.digex.net/. Rancid version has added functions, supports Cisco, Juniper, and Foundry and uses the login scripts that come with rancid; so it can use rsh, telnet, or ssh to connect to your router(s).

Google::SAML::Response can be used to generate a signed XML document that is needed for logging your users into Google using SSO. You have some sort of web application that can identify and authenticate users. You want users to be able to use some sort of Google service such as Google mail. When using SSO with your Google partner account, your users will send a request to a Google URL. If the user isn't already logged in to Google, Google will redirect him to a URL that you can define. Behind this URL, you need to have a script that authenticates users in your original framework and generates a SAML response for Google that you send back to the user whose browser will then submit it back to Google. If everything works, users will then be logged into their Google account and they don't even have to know their usernames or passwords.