Closed MatthewPace98 closed 2 years ago
Under investigation. So far, unable to reproduce.
Closing for now, as neither I nor the user can reproduce this, and possibly fixed in newer version.
Update: this issue doesn't replicate, it happened on a specific machine, that concurrently displayed unexplained errors of other tools. Possibly faulty hardware. I will add another layer of validation in Genozip, to prevent this (very rare) environmental issue from affecting Genozip.
Update: this issue is now resolved in 13.0.21. See Release Notes.
We have recently noticed an issue with our paired-end genozipped DNA FASTQ files, where upon genounzipping, some reads were changed. We used genozip v12.0.37 to execute the following command:
genozip --reference Homo_sapiens_assembly38.ref.genozip --pair file_R1.fastq file_R2.fastq --threads 8
We also used
Process
from themultiprocessing
python library, running 8 instances of genozip simultaneously.The two files are identical in size, with only the line containing the nucleotide sequence sporadically being changed. Here’s an extract from one of the genounzipped files:
And the respective original file (notice the difference is solely in the nucleotides):
We could not reproduce this result, and we could find no errors in the log files. Do you have any suggestions for a potential cause/remedy, please?