Cufflinks Ouput Tracking-File Status
1
1
Entering edit mode
12.6 years ago
Stevelor ▴ 310

Hi,

does anyone of you know the exact definition for 'FAIL','LODATA', 'HIDATA' etc. in the output tracking files cufflinks produces....

Thanks!!

Steve

cufflinks • 3.2k views
ADD COMMENT
2
Entering edit mode
12.6 years ago
Marina Manrique ★ 1.3k

Hi,

AFAIK those tags appear in the quantification status of each object of each sample. I got this from the cufflinks manual http://cufflinks.cbcb.umd.edu/manual.html#tracking_format

Quantification status for the object in sample 1. Can be one of OK (deconvolution successful), LOWDATA (too complex or shallowly sequenced), HIDATA (too many fragments in locus), or FAIL, when an ill-conditioned covariance matrix or other numerical exception prevents deconvolution

it seems only objects with 'OK' should be taken into account but I don't know...

HTH,

marina

ADD COMMENT
1
Entering edit mode

I had a detailed look at the 'FAIL' tag....only genes with different isoforms have this tag :/ Some are okay some not...so this means that cufflinks can not calculate exactly the abundance for all isoforms?? There is no 'FAIL' tag for genes with only one transcript variant!!

ADD REPLY
0
Entering edit mode

That's what I also found in the manual....but there is no exact definition! Because if i have a look at these genes in the genome browser some of them look really ok...not shallowly sequenced....bit strange :(

For example PE 2x65bp one condition mapped and quantified with tophat and cufflinks:
ACTG1 - - ACTG1 ACTG1 TSS22993 chr17:79476996-79479892 - - 1599.66 0 1866.02 FAIL

http://imageshack.us/photo/my-images/813/actg1.png/

does this look like a fail??

ADD REPLY
0
Entering edit mode

Could you edit tyour question adding the command you used? The isoforms with the FAIL tag have really low abundance?

ADD REPLY

Login before adding your answer.

Traffic: 3088 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6