-
Notifications
You must be signed in to change notification settings - Fork 355
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cufflinks incompatibility to STAR output #1012
Comments
This issue likely has been fixed in a development release upstream. I will test it using the next data set I am running. I expect that the new |
Thanks @schelhorn for keeping an eye on this. |
Seems the bug was fixed and committed in development version of cufflinks. Is there anyway to replace current one in bcbio? or just embed the awk script mentioned above? just generate a special version bam file for cufflinks only, other tools use the original bam file? |
Hi @csardas, Are you seeing this same issue? |
Yes, I got same error message like " Error (GFaSeqGet): subsequence cannot be larger than 16569" in some cases (not every case) |
Ok-- I think there is a flag we can set in STAR that will make Cufflinks compatible files. What are you using Cufflinks for? We've been thinking about deprecating it for a while. |
I want to enable transcript-assemble function in RNAseq pipeline to find out novel transcript |
Hi @csardas, Gotcha. There has been some buzzing on the Cufflinks issue list of them releasing a fixed version soon. In the meantime, if you set the transcript_assembler to stringtie, that should work. |
OK, I will try it. Thanks for response. |
There seems to be an acknowledged incompatibility of the current
cufflinks 2.2.1
that makes it incompatible to certain (standard-compliant) SAM inputs. Specifically, one has to expect the criticalError (GFaSeqGet): subsequence cannot be larger than 16569
fromcufflinks
if bias modeling is turned on (as it should). This error results from the inability ofcufflinks
to model softclipped bases that extend over the end of the chromosome (a circumstance that is not forbidden in the SAM specs). Since STAR sometimes generates such outputs if a read best fits to the chromosomal end (this can happen in general and specifically in cancer genomes due to chromosomal rearrangements), there are two ways to post-process STAR BAMs to cut off the ends and makecufflinks
eat the input file. Still, I would like to avoid generating yet another copy of a BAM file just forcufflinks
in bcbio (since other quantitation methods deal with softclipped bases just fine), so that's why I am escalating the bug tocufflinks
and tracking the completion here.The text was updated successfully, but these errors were encountered: