Paired end reads: line # does not match
Hello,
I have a GAII paired-end run (seven lanes, run1 and run2 for each lane are the forward and reverse ends of a pair).
For 3 of the lanes, very few of the reads mapped successfully (< 20%). I just realized that the line # is different in the run1 and run2 of these lanes. The last read in both files is a pair (same QNAME), but there appears to be extra reads in run2.
Has someone else experienced this problem, can it be caused by changes in the Illumina Pipeline settings? If the reads are out of order, does BWA and Bowtie check the read QNAME for mismatches?
If not, has someone else already written a high-speed tool for checking and removing the extra reads from huge FASTQ files?
Thanks
I have a GAII paired-end run (seven lanes, run1 and run2 for each lane are the forward and reverse ends of a pair).
For 3 of the lanes, very few of the reads mapped successfully (< 20%). I just realized that the line # is different in the run1 and run2 of these lanes. The last read in both files is a pair (same QNAME), but there appears to be extra reads in run2.
Has someone else experienced this problem, can it be caused by changes in the Illumina Pipeline settings? If the reads are out of order, does BWA and Bowtie check the read QNAME for mismatches?
If not, has someone else already written a high-speed tool for checking and removing the extra reads from huge FASTQ files?
Thanks