Ok, I missed parts at the bottom of the first post. Does your fasta file have transcript sequences? I'm assuming then you have transcript sequences that contain intronic regions that aren't spliced out? Or are these simply splicing variants and alternate exons? Either way, you can use regular expressions to grab the exon lengths in the cufflinks file, and you can compare this to the sequence length from the fasta file or other transcipt information files from the UCSC genome browser (or the GTF file that you are likely using from Illumina via the cufflinks webpage to annotate transcripts), etc. Again, you can store the transcript information in a hash and use the gene symbol or accession number as the key so that you are comparing the correct things.
Sorry for missing that, I need more coffee it seems :).
-
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.
|