transcript assembling problem by cufflinks
0
0
Entering edit mode
4.7 years ago

After alignment by hisat2 tool and generation of SAM ,BAM and sorted BAM files, I gave this command for transcripts assembling:

cufflinks -o SRR1131119.sam -G Homo_sapiens.GRCh38.97.gff3 --library-type fr-firststrand --no-update-check --upper-quartile-norm  SRR1131119_sorted.bam

Then this happened.. again and again. What to do? Please help!

[00:23:01] Loading reference annotation.
[00:23:14] Inspecting reads and determining fragment length distribution.
Processed 32972 loci.                        [*************************] 100%
Warning: Using default Gaussian distribution due to insufficient paired-end reads in open ranges.  It is recommended that correct parameters (--frag-len-mean and --frag-len-std-dev) be provided.
Map Properties:
Normalized Map Mass: 4040892.47
Raw Map Mass: 4040892.47
Fragment Length Distribution: Truncated Gaussian (default)
   Default Mean: 200
   Default Std Dev: 80
Segmentation fault (core dumped)
rna-seq • 965 views
ADD COMMENT
0
Entering edit mode

not an answer, but I'd recommend to switch to stringtie from cufflinks.

ADD REPLY
0
Entering edit mode

what difference would it make?? moreover during hisat2 alignmnt i used the command "--dta-cufflinks" which does the job specifically for cufflinks..

ADD REPLY
1
Entering edit mode

its is newer, faster, better maintained, and can save a lot of time and nerves in a long run.

ADD REPLY
0
Entering edit mode

The main function of the -dta-cufflinks in Hisat is to ensure only longer anchors are reported. You can enable that manually with --downstream-transcriptome-assembly. Which version of Cufflinks are you running?

ADD REPLY
0
Entering edit mode

i am using cufflinks version 2.2.1

ADD REPLY
0
Entering edit mode

Try post an issue on the Cufflinks github instead.

ADD REPLY

Login before adding your answer.

Traffic: 2555 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