http://www.perlmonks.org?node_id=1020986


in reply to Re^2: intron length
in thread intron length

It isn't clear what you are using here to determine the intron lengths. What was initially "posted" was output from cufflinks, which has your gene/transcript information and FPKM scores for each. Your newly posted script reads in a fasta file and determines the sequence length for each entry in the fasta file. Easy enough. The introns aren't marked in a fasta file, so I'm guessing that you'll use transcript information from the refFlat file from the UCSC genome browser or ensembl, etc. If you wanted to know the length of all exons combined for a given transcript (and ignoring any splicing variants, etc.) then you'll want to use the refFlat.txt file that can be downloaded from UCSC. It's easy to parse, and you can use the table browser to help figure out what values are in what columns (it notes where each exon begins and ends, for instance). You can import the data into a hash with the gene symbol or the accession number as a key and then calculate the exon/intron lengths for only the transcripts that you are interested in.

In the future, I'd try to post a bit more information and be careful to format it better on the site. People here are willing to help, but are less likely to do so if it annoys them. I can look at what you posted and see exactly what you are doing because I work with this type of data all day long; others may not but still have invaluable input in writing your scripts properly, so try to help them get on board. Good luck!

Bioinformatics

Replies are listed 'Best First'.
Re^4: intron length
by bioinformatics (Friar) on Feb 28, 2013 at 04:46 UTC
    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 :).

    Bioinformatics