1 answer
R1 has twice as many reads as R2
That's very wrong. Alert the people who made the fastqs, that is not right at all.
It might be that something went wrong with the fastq generation. Like someone somehow generated only R1, and realized their mistake, and then regenerated both files, but the new R1 was appended to the existing one, instead of overwriting it.
Grab the first read name of the fastq, and see if it turns up twice. If it does, tell whoever made the fastq to start from scratch.
The command to check the first line would be
zcat my_file.fastq.gz | head -n 1
Then when you get the first line:
grep readname my_file.fastq.gz
Ans see how many lines it returns.
You are going to have to poke around to find a command to clean up the fastq if that is the problem; I'm not sure how to do it off the top of my head.
Also this data was generated years ago and I may not be able to contact the person that originally created the fastq file. Is there anyway for me to fix this error myself? I am not a bioinformatician. I only dabble in it to help out my lab. Thanks again for your help.
Log in to answer this question.
-
How to do preprocessing from fastqc
written by Lulu •
-
Increasing per base G content in QC sequencing files
written by robertsr •
-
original single cell data downloaded from GEO yielded only two files with 150bp
written by chenglei1865 •
-
About per tile sequence quality
written by Chris •
-
How to analyze mars-seq single end-read scRNAseq data?
written by Alex •
-
RNASeq data has 3 files R1, R2 and R3, which one is the barcode file?
written by leranwangcs •
-
Difference between trim galore report and Fastqc pre trimming
written by Luern •
-
Sequence Duplication Levels Failed FastQC
written by hpalk42 •
-
Sequence Duplication Levels
written by Elizaveta •
-
bcftools mpileup giving more wildtypes <*> than expected
written by gt •
This blog post by authors of FastQC would be of interest: https://sequencing.qcfail.com/articles/libraries-can-contain-technical-duplication/
Since this is RNAseq data some duplication is expected since there are likely to be more copies of same RNA.
You could try running
repair.shtool from BBMap suite. Guide here: https://jgi.doe.gov/data-and-tools/software-tools/bbtools/bb-tools-user-guide/repair-guide/Thank you! repair.sh worked great!