You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for making defastq, it's super fast and easy to use. However, as I was comparing to a previous result with a different tool, I realised there is a bug when the option --allowed-mismatches set to 2.
I'm adding a minimal working example here of a set of fastq files that have 1 read in them and an index file with just one barcode in it. The reads contains the barcode with 1 mismatch. When I run defastq with --allowed-mismatches 1, it works as expected and the read is demultiplexed. However, when I run with --allowed-mismatches 2, the read ens up in undecoded.R2.fastq.gz.
Hi developers!
Thanks for making defastq, it's super fast and easy to use. However, as I was comparing to a previous result with a different tool, I realised there is a bug when the option
--allowed-mismatches
set to 2.I'm adding a minimal working example here of a set of fastq files that have 1 read in them and an index file with just one barcode in it. The reads contains the barcode with 1 mismatch. When I run defastq with
--allowed-mismatches 1
, it works as expected and the read is demultiplexed. However, when I run with--allowed-mismatches 2
, the read ens up inundecoded.R2.fastq.gz
.Code:
Could you look into what's going on here?
Thanks, Annique
test_barcodes.csv
test_reads.R1.fastq.gz
test_reads.R2.fastq.gz
The text was updated successfully, but these errors were encountered: