Tue, 25 Nov 1997 12:14:52 -0500
Should a BLAST module be All-encompassing? (like a CGI.pm)
or would a set of BLAST modules be better. (like CGI::*.pms)
Here is some of the functionality I was thinking should go into the module(s).
run_remote method (use LWP to run against another machine (or even NCBI??))
Able to handle traditional BLAST, Gapped BLAST and PSI-BLAST
This may be tricky because BLAST outputs are subject to change
("The BLAST report is not intended to be a parseable document. It is subject to
change with little or no notice.
This is perhaps a reason to separate a BLAST::Parse module out of the main
Be able to retrieve an Array of sequences from BLAST report and get at their
source_databases, accession_numbers, locus, def_line, high_score, E-Value,
Unfortunately, my boss is not so keen on the idea of me spending a lot of time
on a module. I am willing to spend some free time to this project. I am
interested in seeing what functionality Chris (Dagdigian) has already built
into his module and going from there.
National Human Genome Research Institute
===== Bioperl Project General Mailing List Message Footer =======
Project URL: http://www.techfak.uni-bielefeld.de/bcd/Perl/Bio/
For info about how to (un)subscribe, where messages are archived, etc: