Closed YiweiNiu closed 3 years ago
Hi,
Thanks for reporting this issue. This is the first time I'm seeing that. So here, you are presenting two different things ;
*.unmap.fastq
files which have sequence and quality values which do not match.
This is of course unexpected and surprising as this file is generated by bowtie2
itself !
Could you check if this read is well formated in the original input fastq file ? if this is not the last read in the file for instance, to be sure that bowtie did not simply stop writting at some point ?*.unmap.fastq
is corrupted, the unmap_trimmed.fastq
will also be corrupted !If you manage to generate a small fastq files, I can try to reproduce your issue. Thanks Nicolas
Hi Nicolas,
Thank you for your reply.
Could you check if this read is well formated in the original input fastq file ? if this is not the last read in the file for instance, to be sure that bowtie did not simply stop writting at some point ?
The original input fastq files were complete, as validated by validatefastq.
I re-ran this sample without changing any parameters, and it worked now.
I guess there was something wrong when running bowtie2, which may be induced by unknown system error.
Thank you again for your time and effort.
Hi,
I am using HiC-Pro 3.0.0. And one of the samples encountered mapping error. I guess it was the due to corrupted Fastqs, which were generated by HiC-Pro, not the input Fastqs.
The following are the logs.
The config file looked like this:
I checked the input Fastqs and found no errors.
I do not know why the
*R2_mm10.bwt2glob.unmap.fastq
and*_unmap_trimmed.fastq
got corrupted.The issue was also reported before issue 381, but it was not solved.
Hope the log information above is useful. Any comments or suggestions would be highly appreciated.