comment on

Dear Perlmonks, I have not yet had time to delve into BioPerl (although I can't wait!).

Here's a brief introduction to Bioperl for you:

#!/usr/bin/perl -w

use strict;
use Bio::SeqIO;

my @files   = <*.seq>;
my $pattern = '[AN]{10}';

foreach my $file (@files) {
   my $seqio = Bio::SeqIO->new( -file => $file );
   while ( my $seqobj = $seqio->next_seq() ) {
      my $raw_seq = $seqobj->seq();
      if ( $raw_seq =~ /$pattern/o ) {
         print "Found a polyA tail in $file.\n";
      }
   }
}
[download]

This seems to work for me.

If you have any questions about how it works, just ask. I made a few assumptions:

If there were a sequence file with 4 sequences, two of which had poly-A tails, the program would print:
```
Found a polyA tail in myfile
Found a polyA tail in myfile
[download]
```
I'm assuming that you're using some sort of format that Bioperl supports.

Also, is there community interest in an Intro to Bioperl Tutorial? The documentation at doc.bioperl.org seems to be very geared towards developers and other experienced Bioperl users. If there is interest I'd be happy to write it, alhough I might need some help (I'm a long time reader of PM, short time member).

In reply to Re: BioInformatics - polyA tail search by biosysadmin
in thread BioInformatics - polyA tail search by MiamiGenome

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks