Apart from what other people have said, i thought i should add that many of the things you want to do are fairly standard and there is a lot of help out there already - check out perl and bioinformatics as a start.

On bioperl you will propbably find there are parsers for your format, and once you have your sequences as a standard object, there are many methods for retreiving subsequences / mathcing etc...

If you files are really that huge, i would say that you probably need to process them one record at a time, or use a database - again there is help on bioperl for doing this, but i think you probably won't need to go that far.

Let us see what you have so far in terms of code, and an example of input and desired output too. HTH.

Just a something something...

In reply to Re: Parsing file by BioLion
in thread Parsing file by maverick.usb

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.