STAR error: EXITING because of FATAL ERROR in reads input: short read sequence line: 0
2
0
Entering edit mode
4.1 years ago
silas008 ▴ 160

Hey, guys. How are you doing?!

I am analysing a RNAseq. First of all I am doing a pre processing of the reads using fastx toolkit.

time fastq_quality_filter -v -q 20 -p 70 -Q33 -i sample.fastq -o sample_quality_filtered.fastq

and

time fastx_clipper -a AGATCGGAAGAGCACACGTCTGAACTCCAGTCA -v -Q33 -l 50 -i sample_quality_filtered.fastq -o sample_clipped.fastq

And then the mapping:

time STAR --runThreadN 4 --genomeDir --readFilesIn sample_R1.fastq.gz sample_R2.fastq.gz --sjdbGTFfile --outFilterMultimapNmax 20 --outFileNamePrefix --outSAMtype BAM SortedByCoordinate --quantMode GeneCounts --readFilesCommand gunzip -c

It's a paired-end data. Curiosly, when I map the reads using STAR aligner, I get this error: EXITING because of FATAL ERROR in reads input: short read sequence line: 0. But if I map the pairs separately or if I map them without pre processing I do not get the error.

I think that, for some reason, when I trim the data I am deleting one of the pairs, them the aligner can not find the pairs of some reads and I get the error.

Do you think this is the problem?

Any suggestion for processing to avoid this error?

Thank you, guys

RNA-Seq • 4.3k views
ADD COMMENT
1
Entering edit mode
4.1 years ago

I think that, for some reason, when I trim the data I am deleting one of the pairs, them the aligner can not find the pairs of some reads and I get the error.

Specifically, I think what's happening is that you are trimming some reads to zero length.

If your trimming steps are messing things up while only affecting a small percentage of reads, I'd skip those steps. I've had good luck with STAR when I had large unexpected adapter seqeunces; STAR is probably going to align reads fine; it will soft trim adapter if it has to. If a read is poor enough quality that it won't align, then it won't align, that's not going to mess anything up.

ADD COMMENT
0
Entering edit mode
3.7 years ago
ruiyan_hou • 0

Hi, I think you can check the length of your reads after cutting adapter. If your one pair read's length is not equal , this error may happen.

ADD COMMENT

Login before adding your answer.

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